Skip to content
Open Bluedeer

How do I give Bluedeer a password or API key safely?

When the assistant needs a password, API key or token, it asks with a secure field in the chat. The value goes straight to Bluedeer, encrypted, and never into a message; the assistant gets only its name, and Bluedeer hands the value to the step that needs it. What a step returns is not hidden, so a command that prints the value shows it.

Never type a password, API key or token into a chat message. When the assistant needs one, it shows a Secure input field in the chat instead. This works on every plan.

Secure input keeps the secret out of the conversation. It is never typed into a message, and the assistant gets only its name and a reference to it. When a step needs the secret, Bluedeer hands the value to that step: a call to one of your custom connectors, or one command on Your computer, where the command receives it as its own variable.

How it works

  1. The assistant explains what it needs and why, and a Secure input card appears in its reply, with one field (or several, when it needs several details at once; see below).
  2. You type or paste the value. Use the eye button to check what you typed; it is hidden again when you save.
  3. Select Save. The value goes straight from the card to Bluedeer and is stored encrypted. Or select Not now, and nothing is saved.

On the phone the card works the same way. While the Bluedeer app is not in front, the field is covered, so the app switcher never shows it. If you leave the app before saving, what you typed is cleared, and you type it again when you come back. On Android, screenshots and screen recordings of the app are also blocked while the field holds something.

When the assistant needs several details at once

One card can ask for several values together, for example everything needed to connect to a database: the host, the port, the database name, the user name and the password.

  • Secret fields are masked, each with its own eye button, and marked Secret. They are handled exactly like a single secret: the assistant gets only their names.
  • Fields marked Not secret, such as a host name, a port or a user name, are ordinary fields. What you type in them goes to the AI as you typed it, so that it can use them directly. Never put a password or key in a field marked Not secret. If you do, for example by pasting a connection string that contains a password, Bluedeer keeps that value secret anyway, does not show it to the AI, and says so on the card.
  • Optional fields say "(optional)" after their label. You can leave them empty; the card then says which ones were not provided.
  • Some fields show an example as a placeholder, or a line under the field that says what the value looks like.

Press Enter to move to the next field; on the last field, Enter saves. The card is saved all at once: Bluedeer checks every field first, and if one needs a change, it says so under that field and nothing is saved until you try again. Not now declines the whole card. After saving, the card lists each field: the secrets by name with how long each is kept, and the values you typed in the fields marked Not secret.

In a shared chat, others see which details were requested, which were secret, and whether each was provided, but never a value. On a shared link, even the values typed in fields marked Not secret are left out.

The value is stored exactly as you entered it: spaces at the start or end are kept, and a value of several lines, such as a private key or a JSON credential, keeps its line breaks. A value can be up to 32,768 characters; a longer one is refused with a message on the card, and nothing is saved.

The assistant is told only the name it chose, for example STRIPE_KEY, and a reference to it, and it tells you whether the secret was saved, by that name. When a later step needs the secret, Bluedeer puts the value in at the moment that step runs, and only after you have approved the step if it asks first. The reply carries on by itself after you answer the card.

A step that was handed a saved secret shows a small used STRIPE_KEY mark: in the thinking section, and on the command's line in the What I did card for commands on Your computer. The mark names the secret only; select it (on the phone, tap it) to read what it means.

What Secure input does not promise

Secure input protects the way a secret reaches Bluedeer. It does not hide what a step returns.

  • Results are not hidden. If a command or a tool prints the value, or a file the assistant reads holds it, the assistant can see it like any other output, and so can you in that step's output.
  • The assistant is careful with it. The assistant is told to write commands that don't print a secret. If it reads one by mistake, it tells you, so that you can replace the secret where it was issued.
  • Your own scripts stay as they are. The assistant doesn't change a script of yours to protect a secret unless you ask, but it can warn you when a script would print or store one.
  • Programs you let it use. Bluedeer can't control what a program or a connector does with a secret it receives. It could send the secret somewhere or save it. Only use secrets with programs and connectors you trust.

A file you attach to a message yourself is given to the assistant as it is. Don't attach files that hold keys; give each key through a Secure input field instead. If you paste a key into a chat message anyway, it is sent to the AI with your message. Replace it where it was issued, then give the new one through a Secure input field.

Masking keys in tool results, in an Enterprise workspace

In a shared workspace on Bluedeer Enterprise, the owner or an admin may have the Compliance option Mask keys and passwords in tool results, where Bluedeer offers it. While it is on, key-shaped values in what tools and commands return, such as API keys, tokens and passwords, are hidden from the AI and from the chat before the AI reads them. The AI then can't use a hidden value either. See Choose what PII the AI sees in a workspace.

Who can see or use it

  • Only you can use it. A secret belongs to the person who saved it, in the chat where it was saved. No one else in the workspace can use it: not other members, not the workspace owner or an admin, and not Bluedeer support.
  • The card never shows it again. Once saved, the card never shows the value, to anyone, you included. If it was wrong, the assistant can ask for it again, and the new value replaces the old one.
  • In a shared chat, only the person the assistant asked sees the field. Others see what kind of secret was requested from that person (for example "Stripe secret key" and its name, STRIPE_KEY), why it was asked, and whether it was saved or declined. They never see a field or the value on the card.
  • On a shared link of the chat, the card's place shows a quiet record: what kind of secret was requested, its name, why, and what became of it (provided, not provided, or provided and since deleted). It never shows the field, the value, how long is left or who was asked. A snapshot link shows the outcome as it was when the link was made; a live link shows it as it is now.
  • Activity shows at most the secret's name.

When it is deleted

  • With the chat. Deleting the chat deletes its secrets at once.
  • A week after you saved it, by default. The card shows how long is left, for example "Will be deleted in 5 days", and later "Deleted".
  • While a scheduled task uses it. A scheduled task made in the same chat whose instructions name the secret keeps it for as long as the task can run (also while it is paused). The card then says "Kept while the task … can run". When the task is deleted, finishes, or no longer names the secret, it is deleted a week later.
  • If a task needs a secret that has been deleted, the task stops and tells you to enter it again. If the chat it was made in was deleted, the task is paused at once and a notice in your Inbox says so. To use it again, ask Bluedeer in a chat of the same workspace to set the task up with the secret again: it asks you to enter it securely, and the task then runs from that chat.

There is no separate list of secrets to manage: delete the chat to remove its secrets sooner.