Synopsis
Description
Runs<agent> with every agent plugin installed in the active environment, then gets out of the way.
The agent replaces the flox agent process, so its exit status and terminal are yours.
<agent> is one of:
The agent is found on
PATH, so the environment’s harness wins over one installed elsewhere.
When the agent comes from outside the Nix store, such as a copy installed with npm or Homebrew, launch warns and runs it anyway.
Each launch stages the plugins in its own folder under .flox/cache/agent-stacks/launch/ and hands that to the agent.
Staged files are links into the installed packages, so nothing is copied.
Your own agent configuration, such as ~/.claude and your login, is not changed.
Launch prints a note: line for each hook a plugin runs and each setting it applies, and a warning for anything it leaves out.
Options
Options forlaunch go between launch and <agent>.
Arguments for the agent
Everything after<agent> goes to the agent unchanged.
A single leading -- is removed:
Global options
Global options go beforelaunch: flox agent --config-dir ./cfg launch claude.
Sandboxes
With--sandbox, launch builds the agent’s command and environment exactly as it does without one, then runs:
See Launch an agent in a sandbox for what each sandbox allows.
Examples
Requirements
Claude Code 2.1.280 or later. Theagent-stacks/claude-code package meets this.
Codex must be the agent-stacks/codex build, which accepts skills from Flox; another build launches without them, and flox agent doctor reports it as degraded.