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 experimental 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 (Phase 1)

MethodStatus
initializeProtocol v1, camelCase agent capabilities
session/newBinds sessionId → flock-memory acp_sessions
session/promptRuns FlockEngine + persist_episode_bundle
session/resumeRestores checkpoint metadata (no chat replay)
session/loadEmits episode metadata via session/update stubs
session/cancelAborts in-flight prompt task
session/closeCancels + marks session closed
promptDeprecated alias for session/prompt

Phase 2 adds async streaming, tool bridge, and permission UX. Phase 3 adds mux-default episodes and evolve hooks.

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 and .flock/episodes/<goal_id>.json exists.

Limitations

  • No full chat transcript replay on session/load — episode metadata only (MEMORY_ARCHITECTURE).
  • No built-in file/shell tools — use editor MCP servers or flock mcp.
  • Mux-backed episodes require Phase 3 (context.mux: true returns error in Phase 1).