Expand description
The AgentService boundary — every ACP wire type stays behind this (ADR-0007).
Synchronous and object-safe, following the template ADR-0005 §3 set for
FileSystemService: the methods block, but they are only ever called from the agent
worker thread, so the non-blocking guarantee comes from where they run. That is what
lets a scripted agent be a plain struct with a queue — no executor, no runtime — and
it is why tokio is still not in the tree.
Structs§
- Client
Capabilities - What the client offers to do on the agent’s behalf (ADR-0007 §3).
- Null
Agent - The default when no agent is configured: Tier 0, and honest about it.
Enums§
- Agent
Event - What comes back from the agent.
- Agent
Integration - How the agent is wired into the workspace (ADR-0003).
- Agent
Request - Work sent to the agent.
- Permission
Decision - The protocol’s four permission responses.
- Proposal
Decision - The human’s verdict while reviewing a proposal. Per hunk and per proposal, as ARCHITECTURE.md §9.3 requires.
- Stop
Reason - Why a turn ended.
Traits§
- Agent
Service - The ACP client surface.
Functions§
- permission_
for_ review - What to tell the agent after a review, given how much of it the human took.