Keeper, passwords masked by default.

Keeper Commander signs in as you once, for 30 days. Listings mask passwords; a value is fetched only at use.

What you can ask → Where the credential stays

keeper commander · a persistent login, 30 days · batch mode on every call

team/tools/keeper/keeper.mdreference only

asked · an exampleWhich record holds the payroll portal login, and who else can see it?

the AI, from the pagePayroll portal, in the shared folder Finance, seen by the finance team. A new share waits for your go.

where the value wentNowhere. The listing masks it, and the page names the record by UID.

who uses it, and why

Who turns to Keeper, and why.

Three jobs, from a leaver's last day to the quarterly review.

the IT admin

A leaver's records, kept for the team.

whySomeone leaves, and their records hold shared logins.

asksTransfer the leaver's records to me, and list what moved.

the finance lead

One login, shared for one hour.

whyAn outside accountant needs the tax portal, once.

asksSend the accountant a one-time link to the tax portal record.

the security lead

The security report, run from one ask.

whyThe quarterly review needs the numbers.

asksRun the security report for this quarter's review.

what you can ask

Your AI reads, adds and shares Keeper records with passwords masked.

Every call runs as you in batch mode, so no prompt can hang it.

Read a record where it is used

Fetched by UID inside the command that needs it.

See the folders you reach

The tree, shared folders marked, records as UID and title.

Find a record by title

Then its UID, used from there on.

Add or update a record

A new login with a generated password, or a field changed.

Share a record or a folder

To a teammate, or by a one-time link for an hour.

The admin's commands

Seats, teams, leavers' records transferred, audit and security reports.

where the credential stays

Your login stays on your computer.

We store nothing of Keeper's, and add nothing to your enterprise.

in Keeper Commander

Sign in once, approve the device, and stay logged in for 30 days. Every call syncs the vault first, so all calls run in batch mode.

in your brain

A page names who holds a seat, the shared folders, and records by UID.

what instibrain never touches

Nothing leaves Keeper unmasked or unasked.

Our server stores the page naming folders and records, in a space you chose.

A password in visible output.
--unmask is never added to anything shown.
Your master password and your device token.
You type the password once. The token stays on your computer.
A record or user change without your go.
The exact list goes to the folder's manager or the admin first.

the limits

Your AI works within Keeper's own rules on removal, restore and sign-in.

Three rules of Keeper's own.

Limit	What it means
A removed record can survive elsewhere	Removed from a shared folder, it stays in its owner's vault.
Only the owner restores from the trash	A member who removed it cannot bring it back.
Persistent login is the admin's call	Without it, every session asks for the master password.