Skip to content

The vault

Some tools need a key. A page speed report needs a Google API key, for example. The mission vault is where you give Cora such a key without ever typing it in the chat. Cora sees the name, never the value.

The examples on this page follow an invented bike shop, Kestrel Cycles, and its mission “Website refresh”.

A secret is a value with a name, kept in one mission. Each one has:

  • a name in capital letters, digits and underscores, such as PAGESPEED_KEY. Names are unique in the mission.
  • the value: the key itself, one line of 8 to 4,096 characters. It is stored in an encrypted store, not in the mission’s records. Nobody can read a value back, not even the person who added it. You can only replace it or remove it.
  • a short note on what it is for.
  • its allowed hosts: the sites the key may be sent to (see below).
  • its access: Ask first, Allowed or Off (see below).
  • who added it and when, and who last replaced it and when.

At most 20 secrets in a mission. A secret belongs to one mission only: another mission, even in the same organisation, cannot use it.

  • Every member of the mission sees the list: the names, notes, hosts and access, and who added each one. Members never see a value.
  • Mission admins, and org admins who are in the mission, add secrets, replace a value, change the access, the note or the hosts, and remove a secret.

Secrets are managed in mission details, on the Tools tab, under Vault keys (see the console reference). The form for a new key opens when you press Add a key. The value field is never filled in for you and is cleared once you save.

Access What happens when Cora wants to use the secret
Ask first The request waits on an approval card in the mission. A mission admin sees the secret’s name, the address and where the key goes, never the value, and approves or rejects it.
Allowed The request runs at once.
Off Cora cannot use the secret. It stays in the vault until someone switches it on or removes it.

Ask first is the default for a new secret. Choose Allowed only for a key you are happy for Cora to use whenever the mission needs it, such as a key that can only read public reports.

Only the mission’s leads (its mission admins, and org admins who are in it) can approve an Ask first request. If the mission has no lead, the request is not sent and no card is made: Cora is told to ask an org admin to make someone a lead of the mission.

Each secret names the hosts it may be sent to, as exact host names such as www.googleapis.com: no https://, no path and no wildcards. Up to five. A key is only ever sent over HTTPS, and only to those hosts. The platform checks the host three times: before the request, when it hands over the key, and at the egress gateway every request from Cora’s worker goes through. If the site answers with a redirect to somewhere else, the redirect is not followed.

Name only the hosts the key is made for. Do not name a general-purpose site such as a paste site or a file-sharing service: anything sent there could be kept.

Cora chooses the address on an allowed host and where the key goes in the request. So she could, by mistake or because a page told her to, put the key into content on that host: a post, a comment or a document it publishes. The host list and Ask first are what limit this. Allowed hosts should be API hosts, such as www.googleapis.com, not hosts where content is published, such as your website, a blog or a social network. If a key must go to a host that also publishes content, keep the secret on Ask first and read each request on the card before you approve it.

Cora has two tools for the vault:

  • request_secret asks for a key she needs. She posts a card in the mission with the name she wants, the host it is for and why. For a mission admin the card has an Add it in the Vault button, which opens the Tools tab with the Add a key form ready. The card never holds a value.
  • call_with_secret makes one web request with a secret. Cora gives the secret’s name, the address and where the key goes (a header, a field in the address, or a field in a JSON body). The platform makes the request for her. The key never enters her sandbox, her context, a message, a document or a log.

Cora gets the answer back with the key blanked out wherever it appears as the platform sent it: as it is, or encoded the way it was put into the address or a JSON body, including the usual ways a service writes those encodings back (small letters in percent codes, stricter percent encoding, and \/ for a slash in JSON) (BG-01M7JS50). That covers a service that echoes the request back. A service that changes the key in some other way, for example by cutting it up, could still show it, so use narrow keys (see below). A large answer, such as a page speed report, can be saved to a file in the team sandbox instead, for a script to summarise; the saved file is blanked out in the same way. Anything Cora posts in the same piece of work is checked for the key, in the same forms, as well.

Only Cora herself uses these tools; her helpers never do. When this mission is a hero and another mission calls it in, the hero uses this mission’s secrets as in its own work: one set to Allowed is used, and one set to Ask first waits for this mission’s admins. The calling mission never sees a secret or the approval card. A called hero saves a long answer only in its private folder for the call (save_to under /task/), never in the team folder (D0805).

Never paste a key or a password in the chat. If one is pasted, Cora will not use it. She will ask you to add it in the Vault instead and to replace the key at its source (make a new one and delete the old), because the old one is now in the conversation. A key pasted in your private chat with Cora is not stored, but Cora has seen it, so replace it too.

The mission’s secrets are kept but cannot be used. Mission admins can still see the list and remove secrets. When a mission is deleted, its secrets are deleted with it.

Adding, replacing, changing and removing a secret are recorded in the organisation’s audit log, with who did it, the secret’s name and its hosts. Every use is recorded with the name, the host and the piece of work that used it. An approval is recorded like every other approval. The value is never recorded anywhere.

  • It is not a password manager for people: no website logins, payment cards or personal details.
  • It is not for connections. Services you connect with a sign-in or a connection key keep their own store and rules; see Connecting an MCP server.
  • It does not let Cora run a command-line tool with a key. That may come later.

Use narrow, low-value keys made for this purpose: a key limited to one service, never a personal password or an account-wide key. For an example, see PageSpeed Insights with a Google key.

Cora’s worker sends every request through the platform’s egress gateway, which also refuses private and internal addresses.