Agent integrations
The structured CLI surface an AI agent drives without a TTY: create with new, place configured agents or explicit argv with launch / spawn, reshape exact...
Full source summary
The structured CLI surface an AI agent drives without a TTY: create with new, place configured agents or explicit argv with launch / spawn, reshape exact existing panes with insert-pane / move-pane / swap-pane, act through run, send-keys, or paste, observe through bounded wait / watch, and raise advisory human attention with ask. Plugin, workspace, and satellite verbs provide the surrounding configuration and inventory surfaces. This file is the agent contract. Per ADR-0030, the structured agent state — cells, command results, semantic events — is a local projection over the shared engine, and the CLI plus its versioned JSON schemas are what an agent depends on, not a structured wire tier. It documents each verb, its JSON shape, the read-act-wait loop, and the exit codes each verb mirrors.
6. Relationship to the other agent surfaces
The CLI verbs here are the stable contract. The
OpenCode integration selects a host-specific six-tool subset;
the Pi integration exposes nineteen bounded tools, including spatial
placement and topology edits. The MCP adapter exposes 32 strict
tools, including paste, launch/spawn, bounded watch, ask, spatial edits, agent
state, and workspace parity, over JSON-RPC stdio. Adapter guides link here instead of
redefining CLI syntax.
sdk.md documents phux-client, the library crate those surfaces
are built from. These adapters are unprivileged consumers
(ADR-0017); the wire
underneath stays additive and versioned under ../spec/
(ADR-0022).
Agent JSON contracts
The structured CLI surface an AI agent drives without a TTY: create with new, place configured agents or explicit argv with launch / spawn, reshape exact...
OpenCode integration
@phux/opencode adds six bounded terminal tools and cache-preserving fleet awareness while an external local phux server owns the terminals.