Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

ACP (Agent Client Protocol)

Flock ships an ACP v1 stdio agent via flock acp. Editors such as Zed can spawn Flock as an external coordination agent — scheduler-primary runs that produce episodes, not chat transcripts.

MCP remains the primary Cursor integration path. See Cursor setup.

Capabilities

MethodStatus
initializeProtocol v1, camelCase agent capabilities
session/newBinds sessionIdflock-memory acp_sessions
session/promptRuns FlockEngine + persist_episode_bundle; emits session/update stream
session/resumeRestores checkpoint metadata (no chat replay)
session/loadReplays episode metadata via session/update notifications
session/cancelAborts in-flight prompt task
session/closeCancels + marks session closed
permissions/requestGovernance pipeline; set FLOCK_ACP_AUTO_DENY=1 in CI
promptDeprecated alias for session/prompt

Phase 2 ships async streaming notifications, tool bridge (flock_* registry), and permission UX. Phase 3 enables in-process mux episodes (context.mux: true or FLOCK_MUX_AUTO=1).

Diagnostics

flock acp doctor

Prints protocol version, agent capabilities, memory backend, and env flags (FLOCK_MUX_AUTO, FLOCK_ACP_AUTO_DENY).

Zed smoke (5 steps)

  1. Build Flock: cargo build --release -p flock-cli
  2. Copy examples/zed-acp.json into your Zed settings agents list (adjust command path).
  3. Open a workspace with a .flock/ directory (or let Flock create one on first prompt).
  4. Start the Flock agent in Zed and send: reach target with context plugin gridworld.
  5. Confirm the agent returns stopReason: completed, ≥3 session/update notifications, and .flock/episodes/<goal_id>.json exists.

Mux episodes

Set "mux": true in prompt context or export FLOCK_MUX_AUTO=1 when a multiplexer socket is healthy. ACP attaches pane_tree to persisted episodes for evolve flywheel compatibility.

Limitations

  • No full chat transcript replay on session/load — episode metadata only (MEMORY_ARCHITECTURE).
  • External editor MCP servers are bridged for flock_* tools only in Phase 2; shell/file tools remain editor-side.
  • crates.io publish for library crates is dry-run only until the API stabilizes.