Skip to main content
A template often needs credentials: an Anthropic key, a database URL, an OAuth token. Secrets let a template declare what it needs without ever containing the value. The launching user supplies it from their vault, and Orgo injects it into the computer at create time. The value never lives in the template, the registry, or the golden snapshot.

Existing computers

In Settings → Secrets, save the value, then choose Apply. Only running Linux computers get secrets. A workspace secret goes to that workspace’s computers, and an account secret to every workspace you own. Updating the vault alone does not change an existing computer. A client account’s workspace is not in the workspace picker there. Save its secrets with Save a secret, naming its workspace_id.

Pick the computers

The Apply dialog lists the computers by workspace: the workspace you are on first, marked This workspace, then your other workspaces by name, then workspaces someone else owns. Every computer Orgo would change has a tick. When the dialog lists more than one workspace, or one someone else owns, each workspace with a computer to change has a tick on its heading too, for all of its computers. Only ticked computers get the secret. When you apply an account secret, a workspace someone else owns starts unticked, because its other members, and the agents they talk to, can read what you send there. Tick it to include it. It starts ticked for a secret saved for that workspace, and for a removal. Computers that are stopped, asleep, or not Linux are listed under their workspace as not changed, with why, and have no tick.

See what changes before you apply

Every info mark in the dialog opens a note. Hover over it, focus it with the keyboard, or tap it.
  • The mark after How secrets reach your computers lists where Orgo writes: its own file, then each agent’s file, with what happens after.
  • Each computer with a tick has a mark of its own. Orgo asks each ticked computer what the apply would change there, without changing anything, and the note says which agent files would get the secret, what would be left out and why, and whether an agent needs a restart. A computer you have not ticked is asked once you tick it. After you apply, the note says what was written.
The check never wakes a computer, and the computer is sent the names only, never a value.

Where each agent gets it

An agent gets a file only when it is installed on the computer. Some names stay out of an agent’s file, such as the chat app names Hermes keeps for each computer, and a value with a single quote, a backslash, ${, or a line break reaches /root/.env only. Every file Orgo writes, and which names each agent leaves out, is listed in Where the values are written, and on the How secrets reach your computers page linked in the dialog. Workspace values override account values with the same name. Programs already running keep the environment they started with, except Hermes, which reads its file again before each message. Hermes still keeps a value taken out of its file until it restarts.

Remove from computers

Deleting a vault entry does not remove copies already applied. Choose Remove from computers in the secret’s menu first. It takes the secret off the running Linux computers in its scope, with the same dialog, ticks, and marks. A line changed on a computer stays, and its note says where. Restart Hermes and OpenClaw afterward: supervisorctl restart hermes-gateway and supervisorctl restart openclaw-gateway. They keep a removed value until they restart. Each computer’s note says which to restart.

From the API

Apply secrets to many computers does what the dialog does in one call: send names alone and it picks the computers by where each name is saved, leaving out workspaces someone else owns unless you name them, or name a workspace or a list of computers. Apply secrets to a computer does one computer per call. Both take dry_run: true to preview and remove: true to take secrets off.

The model

1

Declare

The template lists the secrets it needs under secrets. Names only, no values.
2

Supply

The launching user stores the value in their vault (once, per account).
3

Inject

At create, Orgo writes the user’s matching secrets into the computer at /root/.env (mode 0600). They are never baked into the shared snapshot.

Declare

Reference

At launch, Orgo writes each declared secret you have set to /root/.env under its UPPER_SNAKE_CASE name, so anthropic_api_key becomes ANTHROPIC_API_KEY. New interactive shells source /root/.env, so terminals see the variable. You can also name a declared secret in env with {secret: <name>}:
When Orgo launches a built template, it does not apply env secret references or secret:// files. The value arrives only under the secret’s own UPPER_SNAKE_CASE name, so an env key receives it only when the key is that name, as above. A file with from: secret://<name> passes validation but is never written.
Only declared secrets you have set are injected. A launch never fails over a missing secret, whether or not it is optional: the variable is simply absent. A launch with a restricted API key injects your secrets only when the key has Secrets write, the level that writes vault values onto a computer. Without it, the computer launches as if you had set none, since a key that controls the computer could read /root/.env. Permissions are described in API key permissions.

Secrets and golden snapshots

A template computer starts from the golden snapshot, which was built before any particular user launched it. The user’s secret is injected per computer at create, after the snapshot was baked. So a launch that injects secrets does not restore the snapshot’s memory. It cold-boots from the snapshot’s disk with /root/.env already written, and /root/.env is sourced before app services, terminal sessions, and the on_every_boot hook start, so all of them see the secret. A launch with no secrets to inject restores the snapshot’s memory when its host can, with every process as the build left it. On a launch that injects secrets, /root/.env holds only the secrets: literal env values the template wrote there are not set. Put a value a service needs in that service’s own env. To start a program with the launcher’s key, give a terminal session a run command, or run the program as an app service:
This is the pattern the curated system/coding template uses: its claude-code and codex sessions run claude and codex. Do not rely on the on_resume hook for this, because launched computers do not run it.

Managing your vault

Add and update secret values in Settings → Secrets, at orgo.ai/settings/secrets. A secret is either account-wide or scoped to one workspace. Store an account-wide key once and every template you launch can request it by name. A workspace value takes precedence over an account value with the same name. From the CLI, orgo secrets set ANTHROPIC_API_KEY stores a value (it prompts for the value when you omit it) and orgo secrets list shows the names you have set.

Security

  • Values are encrypted at rest and never returned to a client in plaintext.
  • A secret is never part of the template document, its digest, or the golden snapshot.
  • Build logs never print secret values.
  • Only secrets a template explicitly declares are injected, and only if you have them set.

Next steps

Schema reference

env, files, and secrets in full.

Examples

See a launch-time secret in a real template.