Vault

Store API keys, passwords and other credentials in your personal Vault instead of pasting them into chat. Chetty keeps values encrypted, never shows them again, and gives the agent only item names and descriptions. The agent writes {{vault:NAME}}; the value is inserted only when the tool executes and exact values in tool output are hidden as «vault:NAME».

The Vault protects against accidental disclosure, not a deliberately exfiltrating agent. It is personal, not shared with a Project or team. The native Vault tool lists names and descriptions only.

Add an item

1. Open Account → Vault, between Security and API tokens.
2. In Your items, choose Add item.
3. Enter a name such as API_KEY. Use uppercase A–Z, digits and underscores, start with a letter, and use at most 64 characters. Lowercase letters turn uppercase as you type.
4. Add a description of 1–500 characters explaining what the agent may use the item for. Do not put the secret in the name or description.
5. Enter the value in the password field. Switch to multiline input for keys that span several lines. The value must contain at least four characters and at most 64 KiB of UTF-8 text; it is stored exactly as entered.
6. Save the item. Your items shows it folded: its name with when a tool call last used it and when it last changed, and its description below, never its value.

You can also ask the assistant to save, change or delete an item if it has permission to use the API. If you send it a value to save, that value passes through the conversation before it reaches the Vault; saving it does not remove it from the earlier conversation. To keep a value out of chat, enter it in the Account → Vault form. Chatbot accounts do not have a vault.

Ask the agent to use an item

For example, ask: “Use API_KEY from my Vault to authenticate the request to the example service.”

The agent calls the Vault tool to list NAME: description entries, then writes {{vault:API_KEY}} in the tool argument. It does not need to see or remember the value. Its account must have the Vault tool grant as well as permission to use the receiving tool.

An unknown name stops the call before anything runs. Without the grant, Chetty refuses the placeholder rather than sending it as a credential. Permission prompts and saved permission patterns contain the placeholder only. Text saved for a later run keeps placeholders: memories, delegated-task instructions, scheduled job and one-time wake-up prompts, tasks, skills and voice-call instructions. The later run resolves them only when it uses a tool.

Bash quoting

Put placeholders inside double quotes, never single quotes. For example:

curl -H "Authorization: Bearer {{vault:API_KEY}}" https://api.example.com/status

Terminal passes the value to that one process as an environment variable, not in the launch command arguments. A standalone placeholder also expands, but double quotes keep spaces and line breaks together. Inside single quotes it remains unexpanded. This rule also applies when Bash runs PowerShell on a paired Windows computer.

If a paired computer reports LOCAL_CLIENT_OUTDATED, update the Chetty CLI to the release matching the server.

Replace or delete an item

Each item has Edit (its description), Replace (its value) and Delete beside its name. Replacement uses a password field with the same multiline option; the old value is never revealed. A replaced or deleted value applies to the very next tool call.

Unfold an item to see how many tool calls used it on each day of the chosen period, with the total below the chart. The period is shared by all items. A call counts once for each item it uses, even if the tool then fails. Deleting an item also deletes its usage.

Whose vault is used

In a shared conversation, the agent uses the vault of the person whose message it is answering. In your own chat, scheduled tasks and delegated sub-agents, it uses the owner's vault (a sub-agent keeps the delegating account). A sender on another chat platform needs a linked human account. Memory consolidation does not have vault access.

Limits

Protects against accidents, not against an agent that deliberately encodes, splits or sends a value elsewhere. Images are not scrubbed. Files on disk keep what was written into them; reading them back is scrubbed. The same holds for text the agent saves through a general writing tool or by calling the Chetty API directly: the placeholder is replaced with the real value before saving. A scheduled job whose prompt is sent straight to the scheduler's API therefore carries the value into every later run. Ask the agent to create schedules with its normal scheduling tool, which keeps the placeholder. What a tool sends or stores with a value (HTTP request, e-mail, a plugin record such as a card comment) leaves the vault; that is the use itself. In Bash the placeholder must sit inside double quotes or stand alone; inside single quotes it does not expand. The live tail of a running command is scrubbed per update. A value the command did not receive through the vault (for example cat .env) can show as a fragment at the cut edge of that rolling window; the final result and everything the model sees are whole and scrubbed. Values handed through the vault are already removed from the stream by Sandbox's output redaction.