bandicot
Bandicot Docs
Chapter IIIWork · Available now

Secrets and passwords

Paste a key without it reaching a model, save sign-ins in Passwords, and learn what an agent can use or read, what a teammate gets and how to remove a secret.

Available now. A current user-facing path exists within the stated scope.

Paste a secret safely

Choose Share a secret in the prompt bar's attach menu, or paste a key as usual and Bandicot marks it private before it is sent.

The attach + menu has Share a secret, with the hint private. It opens a masked field, Type or paste it here, and an optional Name (optional). Choose Save securely, or Back to cancel.

If you paste a secret straight into a message, Bandicot spots it first. It recognises the usual key prefixes, such as those of Stripe, GitHub, OpenAI, Anthropic, AWS, Google, Slack, Hugging Face, npm, Tailscale and Resend, private key blocks, and a value written after a word like password, secret, token or api key, in English and Spanish.

A match shows a chip, such as Stripe key · private, and the text turns to dots. If it was not a secret, choose Not a secret on the chip; that skips the check for this one message only.

  1. Open the attach menu in the prompt bar and choose Share a secret.
  2. Type or paste the value, and give it a Name (optional).
  3. Choose Save securely.
  4. Send your message. The agent gets a note that the secret exists, never the value.

What the agent gets

The agent gets a private file and a note naming it, never the value, so the value does not reach the model, the logs or the events you see.

The note reads like this: the secret is saved privately at a path, to be read inside a command and never printed. A command can read the file. Anything the command prints that holds the value is masked as the secret's name.

The file is deleted after twenty-four hours, or sooner when you delete the agent. For a work agent, the card says it is kept out of chat, in a private file this agent's commands can read for twenty-four hours.

When the agent asks for a secret

When an agent needs a key it does not have, a card headed Asking for a secret appears with a field, Save securely and Decline.

The card shows what the agent needs and why. Links on it open in Bandicot's own browser, so you can fetch the key from the site without leaving the window. Paste it into Type or paste it here and choose Save securely.

Afterwards a receipt says what happened: Saved with the name and when it stops being readable, You declined to share the secret, or that no answer was given.

For an automaton the footer reads that the key is kept out of chat and sealed in Passwords until you forget it, and that a private file holds it only while a run reads it.

The Passwords vault

Settings › Passwords holds your sign-ins, Mac accounts, profiles and FileVault recovery keys, sealed on this Mac, for you and your agents to use.

The pane says an agent can ask for one to be typed where you allow, and never sees the value. Add a password makes a new entry; an empty list reads Nothing saved yet.

Each entry has a kind: Sign-in, Two-factor code, Mac account, FileVault recovery key, Profile, Secure note, or Kept secret, which an agent's ask makes. A Kept secret has only Forget.

Showing a value needs your Touch ID or Mac password. Show reveals a field for fifteen seconds, Hide it now closes it sooner, and Copy puts it on the clipboard for thirty seconds, then clears it. A recovery key asks Show this recovery key? first, stays on screen for fifteen seconds and the use is written down.

The form has Name and Kind, then the fields that kind needs: Website, User name, Password with Show and Generate, Mac, Recovery key or Note. The chips Who can use it and Where it can be typed set where an agent may use it; a place you did not list asks the first time. Macs this key is for limits which of your Macs may have it. A blank sealed field keeps what is saved.

Recent use counts Typed for agents and Refused. No password is ever written in this list.

If it goes wrong

The pane says the passwords were sealed with another key.
They stay closed and nothing was changed. Quit and reopen Bandicot; if it repeats, see Troubleshooting.
The pane says the key that seals the passwords is not available on this Mac.
Quit and reopen Bandicot, then open the pane again. Nothing was changed.

One-time codes

A Two-factor code entry holds a setup link or key and shows the current code with a countdown, so an agent can have it typed without seeing the key.

Choose Add a password, pick Two-factor code and paste the setup link or key into Setup link or key. The live code and a countdown appear on the entry.

An agent that needs the code asks for it to be typed in the page. The code changes on a timer, and the key behind it is never shown to the agent.

What an agent can use and what it can read

An agent can have a password typed where you allow, and it can read a kept secret only inside a command, but it never sees either value.

Passwords in the vault are typed into a page or field for the agent. The agent learns only whether a value went in. A recovery key cannot be allowed on first use with the one-button allow.

A Kept secret is different: it is a file the agent's own commands read, for twenty-four hours, so a script can use an API key. The value is masked in everything the agent prints.

Bandicot's own window refuses password fields when an agent drives it. Passwords go into no starter kit and into no exported profile.

Use versus read
KindTyped for an agentRead by a commandSeen by the model
Sign-in, Mac accountTyped for an agentWhere you allowRead by a commandNoSeen by the modelNever
Two-factor codeTyped for an agentWhere you allowRead by a commandNoSeen by the modelNever
FileVault recovery keyTyped for an agentNeeds your yesRead by a commandNoSeen by the modelNever
Kept secretTyped for an agentNoRead by a commandFor twenty-four hoursSeen by the modelNever

A secret and your teammates

A message that holds a secret is never sent to someone else's Mac, so a pasted key stays with you and the Macs it is for.

If you write a secret in a message that would go to a teammate or to one of their agents, Bandicot does not send it. It says that the message holds a secret and would go to someone else's Mac, so it was not sent. Take it out and send it again.

If the secret could not be saved privately at all, the message says so and is not sent either. In Passwords, Macs this key is for sets which of your own Macs may use a key.

If it goes wrong

That message holds a secret and would go to someone else's Mac, so it was not sent.
Remove the secret from the message and send it again. Share it another way, such as a team password manager.
That message holds a secret that could not be saved privately, so it was not sent.
Try again. If it repeats, save it with Share a secret first and then send your message.

Secrets in an automaton's brief

A key inside a brief for an automaton is sealed in Passwords for that automaton, and its runs read it from a private file only while they need it.

The key is kept out of the conversation. The automaton uses it; it does not show it. See Automations for how an automaton works.

Remove a secret

Choose Forget on a Kept secret, or Delete and then Delete for good on a Passwords entry, and it is gone.

A private file also goes by itself after twenty-four hours, and when you delete the agent. Choose Keep instead of Delete for good to back out.

A key you pasted into a service may still work there. Revoke it on the service's own site if you think it leaked.

Questions

Does the model see my API key?

No. The agent gets a private file and a note naming it, and the value is masked in anything it prints.

Can an agent read my passwords?

No. It can ask for one to be typed where you allow, and it learns only whether a value went in.

Where are passwords stored?

Sealed on this Mac, in Settings › Passwords. They are not part of a starter kit or an exported profile.

What if Bandicot thinks something is a secret and it is not?

Choose Not a secret on the chip. That skips the check for that one message.