Settings

External agents

Detect Codex, Claude Code, and OpenCode on your PATH and start their ACP runtimes from the same project thread list.

What this panel does

External Agents lets AgentsOS talk to local agents through the Agent Client Protocol. Detected presets can be launched as project sessions, so you can keep native AgentsOS threads and external-agent threads beside each other.

Supported presets

The native app currently checks these presets:

  • Codex: requires codex and npx, launched through npx -y @zed-industries/codex-acp.
  • Claude Code: requires claude and npx, launched through npx -y @agentclientprotocol/claude-agent-acp.
  • OpenCode: requires opencode, launched with opencode acp.

Each row shows whether the preset is detected, the launch command, the primary binary path, and requirement paths.

Verify

Use Verify to probe an available preset. A successful probe shows the agent title or name, ACP protocol version, optional agent version, and whether session/load is supported.

Creating external-agent threads

After a preset is detected, the Projects sidebar's new-thread menu includes entries such as New Codex Thread, New Claude Code Thread, and New OpenCode Thread. External sessions show a runtime badge in the chat editor and expose that runtime's supported model, thinking, or mode controls when the agent reports them.

If a previously-created external thread becomes unavailable because the binary is missing from PATH, the chat input is blocked with instructions to reinstall it or verify it from this settings panel.