Environment variables
Read by Swarmed
Section titled “Read by Swarmed”| Variable | Effect |
|---|---|
SWARMED_DATA_DIR, SWARMED_WORKTREES_DIR |
move the data directory and the worktrees |
SWARMED_CLAUDE_BIN |
the claude program sessions run, instead of the one on the PATH |
SWARMED_CLAUDE_CONFIG, SWARMED_CODEX_CONFIG, SWARMED_OPENCODE_CONFIG_DIR |
where Claude Code’s, Codex’s and OpenCode’s configuration is read from |
SWARMED_FAKE_AGENT |
any value: a scripted agent instead of real ones, which spends no tokens |
SWARMED_NOTIFY_TRACE |
a file the app notes what became of each notification in |
Set for hooks
Section titled “Set for hooks”A task’s hooks run with SWARMED_PROJECT, SWARMED_TASK, SWARMED_USER, SWARMED_BRANCH,
SWARMED_SLOT, SWARMED_WORKTREE, SWARMED_REPO and SWARMED_PORT_<NAME>, beside the project’s
and the environment’s own env. Hooks, stacks and ports has what
each holds.
Given to agents
Section titled “Given to agents”A task’s agents get the project’s and the environment’s env, but not the SWARMED_* variables
above. Agents other than Claude Code also get the stored API keys.
Claude Code gets none of those keys, and no variable whose name starts with ANTHROPIC_ or
CLAUDE.