instibrain / works with / bitwarden

Bitwarden, opened one field at a time.

Q: Does instibrain hold my Bitwarden vault, master password or session?

No. bw runs on your computer, signed in by you. The page names collections and items.

The bw command signs in as you, once per computer. Its session key stays in your secret store.

What you can ask → Where the credential stays

the bw command · your own sign-in · the session key in your secret store

team/tools/bitwarden/bitwarden.mdreference only

asked · an exampleAdd the new warehouse scanner login to the Operations collection.

the AI, from the pageBuilt from the template into Operations, sent by stdin. The password matches your clipboard, unprinted.

where the value wentClipboard to item over stdin. The page names the collection and the item only.

who uses it, and why

Who asks Bitwarden, and what for.

Three people, each with a login to move, read or account for.

the admin

Who sees a login, answered from the source.

whyAn auditor asks who can open the bank login.

asksWhich collections hold the bank logins, and who sees each?

a team lead

A login out of one person's vault.

whyThe only copy of the supplier login is in your own vault.

asksMove my supplier portal login into the organisation.

a developer

A release script that never holds a password.

whyThe release script needs the registry password.

asksPush the image with the registry login from the Engineering collection.

what you can ask

Your AI reads Bitwarden one field at a time, passwords kept off screen.

bw prints every field, so the AI parses each answer down to what it shows.

Read one field where it is used

A password, username, URI or TOTP code, inside the command that needs it.

See what the organisation shares

Collections, who sees each, members, and items as ids and names.

Find an item by title

Answered as ids and names. Your folders stay yours.

Create or edit an item

Sent by stdin, read back, and compared to its source.

Move an item into the organisation

So the people who need it see it.

Trash, never purge

Deleted items sit in the trash for 30 days. Purge is never used.

where the credential stays

Your sign-in opens the vault.

We store nothing of Bitwarden's, and add nothing to your organisation.

in Bitwarden, and in your secret store

You sign in once. The session key waits in your secret store, then goes. Each bw call gets the session key inline. Without it, the vault stays locked.

in your brain

A page names the organisation, its collections, and the item names.

what instibrain never touches

Your AI never prints a password or changes a shared item unasked.

Our server stores the page naming the collection and the item, nothing more.

A password on screen or in a page.
Listings are parsed to ids, names and usernames first.
Your master password, session or API key.
You type the password. The session key is deleted after.
A shared-collection write without your go.
The exact list comes first, then your yes.