Agent Protocol Client sessions
Agent Protocol Client (ACP) sessions let Orca run supported coding agents as structured chats. Orca owns the provider process, adapts each provider's ACP dialect, restores or creates a provider conversation, and records the result in the shared agent-session journal. Workspaces and other clients then see one view of messages, tools, questions, child work, choices, and recovery state.
ACP transport
The ACP transport is a bounded JSON-RPC stream between Orca and a provider process. The process, stream, and cleanup form one owned unit so startup, sign-in, cancellation, stream loss, and exit have one lifecycle.
Process boundary
The client sends protocol calls through standard input and reads provider events from standard output. The transport supports calls in both directions and limits message size, pending work, incoming requests, write backlog, and request time. Invalid or oversized input becomes a diagnostic or a typed failure instead of unbounded work.
References: src/…/acp-json-rpc-peer.ts• L24-36 src/…/acp-json-rpc-peer.ts• L37-97 src/…/acp-json-rpc-peer.ts• L104-165 src/…/acp-json-rpc-peer.ts• L177-215
Sign-in boundary
Sign-in is a startup or turn outcome, not ordinary provider text. A recognized sign-in line can start the host sign-in flow and close the chat as signed out. An unreadable or oversized link closes the connection without claiming that sign-in succeeded, and the link does not enter diagnostics.
References: src/…/acp-agent-connection.ts• L30-39 src/…/acp-agent-connection.ts• L93-107 src/…/acp-agent-connection.ts• L188-215
Structured session acquisition
Acquisition turns a durable Orca session into a live provider chat. It uses the saved session identity and launch policy, publishes ownership before the handshake, and reports a ready session only after the provider conversation and its safety checks are complete.
Launch identity
The session record supplies the workspace folder, account home, provider handle, saved options, and resume choice. Launch resolution then selects the command, managed release, environment, permission mode, skills, standing instructions, and provider metadata for that identity. A caller's current folder or account does not silently replace the saved values.
Orca can use a host-installed program or a managed provider release. A release must match the host target, checksum, command layout, and minimum version before Orca offers it for a chat. The same launch identity is used for chat sessions and model discovery.
Providers do not share one way to receive skills or standing instructions. Orca loads skill roots when the provider release can preserve them, and it uses provider-specific session metadata, files, or launch flags for standing instructions. If a provider cannot receive required instructions, the chat does not start.
References: src/…/acp-launch-contract.ts• L22-110 src/…/acp-launch-command.ts• L29-70 src/…/acp-structured-launch-resolution.ts• L128-183 src/…/acp-structured-launch-resolution.ts• L203-303 src/…/acp-instructions.ts• L20-50 src/…/acp-instructions.ts• L214-247 src/…/acp-minimum-versions.ts• L1-9 src/…/acp-registry-catalog.ts• L32-57 src/…/acp-registry-managed-runtime.ts• L70-110
Connection ownership
The acquisition path creates the provider connection after its final cancellation check. It tracks that connection before spawn and handshake so cancellation can close a process that has started but is not ready. Frames that arrive before the journal lane exists wait in a bounded queue, then enter the lane in order.
Protocol loss and process exit are separate facts. Protocol loss can close journal input and stop history catch-up while the process still needs exit evidence. Exit evidence completes cleanup and supplies the final diagnostic state.
References: src/…/acp-structured-acquire.ts• L35-47 src/…/acp-structured-acquire.ts• L85-163 src/…/acp-structured-acquire.ts• L203-247 src/…/acp-agent-connection.ts• L58-70 src/…/acp-agent-connection.ts• L138-159 src/…/acp-agent-connection.ts• L196-225
Provider attachment
After initialization, Orca loads the saved provider conversation or starts a new one. The provider session id identifies the remote conversation, while the Orca session id and journal remain the stable host identity across provider replacements.
When a saved conversation cannot be reopened, Orca checks whether it was an unsaved first conversation. It can supersede that empty handle, or it records a restore warning before opening a new provider conversation. A moved conversation is reopened in the folder where the provider lists it when the dialect requires that rule.
The handshake also checks standing-instruction support, probes child-stop support, confirms the requested permission mode, and adopts the provider's live options. A loaded conversation keeps its own model. Only a new conversation applies a model carried by the launch. The resulting provider handle records whether the conversation was created or resumed.
References: src/…/acp-structured-handshake.ts• L63-114 src/…/acp-structured-handshake.ts• L115-205 src/…/acp-structured-handshake.ts• L209-317 src/…/acp-session-reopen-failure.ts• L27-73
Catalog discovery
Model and option catalogs come from the same provider command, account, environment, and release policy as a chat. A provider may expose its catalog during initialization, through a command, or through a disposable session. Discovery never performs interactive authentication.
Session-based discovery starts only when needed and cleans up after the provider process exits. It can publish a basic model inventory before slow model-specific effort data arrives, then retain valid late results. A failed launch model remains marked as attempted instead of becoming a false confirmed choice.
References: src/…/acp-model-catalog-probe.ts• L61-145 src/…/acp-model-catalog-probe.ts• L165-245 src/…/acp-model-catalog-probe.ts• L247-283 src/…/acp-listing-session-models.test.ts• L25-93 src/…/acp-listing-session-models.test.ts• L192-223 src/…/acp-registry-managed-runtime.ts• L119-154
Dialect and capability negotiation
ACP defines the wire contract, but providers differ in event names, option menus, questions, child work, commands, and failure text. A dialect is the provider-specific translation policy at that boundary. The session, journal, and client controls stay shared while the dialect maps provider facts into Orca concepts.
Protocol capabilities
Initialization validates the ACP version and records provider capabilities. Orca advertises only the client features that the live provider can support. It can advertise forms or URL elicitation when the chat can present and answer them, while file-system and terminal services remain outside ACP.
Capability checks also govern child work, commands, interaction modes, and model controls. A child Stop action appears only when Orca has a safe route and full child identity. Commands that affect shared account state can be withheld from the chat.
References: src/…/acp-dialect.ts• L140-196 src/…/acp-structured-acquire.ts• L104-128 src/…/acp-structured-handshake.ts• L72-82 src/…/acp-structured-child-stop.ts• L27-85
Provider variants
Supported providers share the structured session contract but use different rules. Antigravity, Cursor, and Kimi adapt questions and approvals. Copilot, Hermes, and OpenCode normalize provider tool results. OpenCode also maps interaction modes and child-session support, while provider dialects can classify authentication notices, retries, quota errors, compaction results, model selectors, and skills.
These differences belong in dialects instead of the shared session path. The common journal and turn rules therefore remain stable when a provider changes its wire details. A provider failure notice is treated as failure evidence rather than assistant text when the dialect can prove that meaning.
References: src/…/acp-dialect.ts• L140-243 src/…/acp-reply-notice-failure.ts• L12-25 src/…/antigravity-dialect.ts• L195-214 src/…/copilot-dialect.ts• L14-45 src/…/cursor-dialect.ts• L167-186 src/…/hermes-dialect.ts• L91-104 src/…/kimi-dialect.ts• L74-81 src/…/opencode-dialect.ts• L118-133
Request presentation
ACP requests become the existing Orca question or approval surface. The translator keeps provider field ids and maps choices, text, boolean values, multi-choice values, and URL actions back to the provider's reply shape. Orca bounds the number of fields shown to a person and returns an explicit not-shown value for supported fields outside that bound.
URL elicitation is person-only approval. Orca accepts only safe HTTP or HTTPS URLs, records whether the person opened or declined the page, and waits for the provider's completion notice before marking the request finished.
References: src/…/acp-form-elicitation.ts• L11-44 src/…/acp-form-elicitation.ts• L71-199 src/…/acp-url-elicitation.ts• L42-83 src/…/acp-url-elicitation.ts• L93-153 src/…/cursor-dialect.ts• L41-81 src/…/antigravity-dialect.ts• L22-69
Turns and permissions
Orca separates input admission, provider delivery, journal acceptance, and final turn outcome. This prevents a successful host hand-off from becoming false proof that the provider received a prompt.
Prompt turns
Each outgoing message has one logical prompt and one journal identity. The first provider event proves receipt. A refusal before the prompt opens rejects the message. A failure after the provider may have received it becomes a provider failure or an unknown send according to the evidence available.
Only one prompt runs at a time. A new message becomes a steer and cancels the active prompt once. Later steers keep their order. Stop withdraws held work and gives the active turn one grace window. A provider-specific busy retry can repeat only the same logical prompt after a typed temporary refusal.
The adapter applies option and permission changes before it admits the message. It records host admission before provider confirmation, which keeps queued, admitted, rejected, failed, and unknown sends distinct.
References: src/…/acp-structured-session-adapter.ts• L106-153 src/…/acp-structured-turns.ts• L79-141 src/…/acp-structured-turns.ts• L180-207 src/…/acp-structured-turns.ts• L219-279
Permission modes
Permission mode can belong to Orca or to the provider. Orca can answer an offered allow-once choice in full access only when the dialect does not claim the request as a question or as a provider-enforced permission flow. Provider-owned modes are written in order and are considered unknown when a write may still have reached the provider.
Changing a provider-owned mode can require a turn transition or a restart. The next prompt waits for the mode write to settle, so a prompt does not run under an older mode.
References: src/…/acp-launch-contract.ts• L63-72 src/…/acp-structured-options.ts• L220-252 src/…/acp-structured-options.ts• L305-323 src/…/acp-structured-session-adapter.ts• L137-152
Permission requests
A permission request is a provider request for a person's choice. Orca validates the session, request shape, and offered option ids. It commits the journal answer before it replies to the provider, so another client cannot answer the same request and the visible card stays aligned with the provider.
Permission handling fails closed. Requests during Stop, teardown, or an unready turn are cancelled without opening a new card. A claimed answer finishes its commit even if Stop arrives during the save.
References: src/…/acp-structured-prompts.ts• L39-89 src/…/acp-structured-prompts.ts• L91-146 src/…/acp-structured-acquire.ts• L110-127
Option selection
Model, effort, fast mode, interaction mode, and permission choices use provider-confirmed state. A live provider report outranks a catalog default, and a write is accepted only after the provider confirms it. A late response cannot replace a newer choice. New sessions may apply configured defaults, while loaded sessions keep the choices saved in the provider conversation.
Some providers expose model families or selectors that their ACP option cannot name. Orca uses the dialect's hidden provider command when allowed, absorbs its reply, and exposes only a confirmed choice or a clear refusal. Reported provider commands become slash commands or skills after dialect filtering and provider initialization identifies built-ins.
References: src/…/acp-select-choices.ts• L13-73 src/…/acp-session-slash-command.ts• L5-19 src/…/acp-structured-options.ts• L109-181 src/…/acp-structured-options.ts• L220-295 src/…/acp-dialect.ts• L210-243
Prompt content
Orca converts journal message blocks into ACP content only when the provider can represent them. Text remains text. Supported images are bounded before inline delivery, and unsupported or unsafe data uses a host-file reference when possible. Invalid or oversized content is rejected before delivery.
Host commands such as model, effort, compact, and clear remain separate from ordinary provider prompts. A provider command passes through only when the live provider reports it.
References: src/…/acp-prompt-content.ts• L1-120 src/…/acp-structured-session-adapter.ts• L106-146 src/…/acp-dialect.ts• L205-224
Timeline translation
The timeline translator turns provider events and requests into Orca's shared journal grammar. It keeps message, tool, request, turn, and child identities stable so a later provider update revises the right row instead of creating a second one. Translator state belongs to one provider child, and the lane drains its events in journal order.
Event grammar
| Provider evidence | Orca journal concept |
|---|---|
| Assistant and thought chunks | Assistant or reasoning messages |
| Tool calls and updates | Tool rows, output, and diffs |
| Plans and goals | Plan or goal status rows |
| Usage and model reports | Context and option state |
| Questions and permissions | Question or approval rows |
| Unknown updates | Bounded provider frames |
| Failed ends and hook blocks | Turn failure or hook-outcome rows |
The translator chooses the owning turn from provider identity and durable ownership. It starts a turn once, drops late chunks for settled turns, keeps host command turns separate from provider-keyed turns, and retains context-window facts during replay. Dialects normalize provider tool output before the shared tool row is built.
References: src/…/acp-timeline-translator.ts• L38-69 src/…/acp-timeline-translator.ts• L166-239 src/…/acp-session-update.ts• L12-45 src/…/acp-session-update.ts• L48-125 src/…/acp-tool-timeline.ts• L1-120 src/…/acp-turn-failures.ts• L24-55
Ownership and late evidence
Timeline ownership links provider message and tool ids to the turn that first accepted them. A later frame can use that durable ownership to stay with its original turn without reopening a completed turn. A settled compaction or host command can update context state, but it cannot reopen or retarget the completed prompt.
Failure evidence is merged by turn. A later provider detail can improve an earlier generic failure without creating a second failure row. Provider retry notices become one revised warning row for that retry run.
References: src/…/acp-timeline-translator.ts• L194-218 src/…/acp-timeline-translator.ts• L231-272 src/…/acp-turn-failures.ts• L24-55 src/…/acp-turn-failures.ts• L101-163 src/…/acp-reply-notice-failure.ts• L12-25
Child work
Background tasks and subagents are child work. They belong to the session but are not the lead agent's current answer. Orca keeps their identity and outcome across tool updates, independent completion notices, parent Stop, session loss, and journal paging.
Some providers report after a prompt ends because a long call became a background task. When the dialect supports reactive wakeups, Orca places that later report in a new agent turn and updates the original task instead of attaching the report to the old prompt. A quiet timer ends unprompted work, but it waits while a request is open or a call is still running.
Child work feeds two surfaces: a timeline row near its spawning tool or turn, and shared status evidence for workspace summaries. A child is stoppable only when the provider route and full identity are known. Unknown, failed, signalled, or unproven endings stay non-successful.
References: src/…/acp-agent-turns.ts• L11-74 src/…/acp-agent-turn-quiet.ts• L14-60 src/…/acp-background-task-child-work.ts• L1-120 src/…/acp-child-sessions.ts• L28-130 src/…/acp-dialect.ts• L151-176 src/…/antigravity-v1.5.12-reactive-wakeup.jsonl• L6-16
History replay
Provider traffic during attachment is history, not a new live turn. Orca marks the full load window as replay even when the provider omits a replay marker. The translator keeps context usage from that traffic, but it does not create duplicate message, tool, task, or child rows.
After the load window closes, new provider events enter the live lane. A provider-specific history identity can add turns made outside Orca once. History catch-up reads bounded pages, matches provider turns to native journal turns or prior imports, and writes only owned changes. Incomplete, conflicting, stale, or oversized catch-up is reported as incomplete instead of a complete transcript.
References: src/…/acp-structured-handshake.ts• L115-140 src/…/acp-structured-handshake.ts• L209-235 src/…/acp-history-catch-up.ts• L36-167 src/…/acp-history-journal-view.ts• L165-235 src/…/acp-history-turn-content.ts• L5-33 src/…/acp-history-turn-matching.ts• L37-119
Lifecycle recovery
Recovery distinguishes provider failure, protocol loss, requested close, sign-in, and provider-session loss. This prevents the journal from claiming success when Orca cannot prove what happened, and it prevents a new child from starting while an old one may still be alive.
Connection and process exit
A broken stream closes journal input and settles a running turn as unverifiable when the provider result is not known. Orca then closes the process and waits for exit evidence. A requested close is a host action, not a provider crash. An unexpected exit includes the exit status and a redacted diagnostic tail.
The process owner tracks root and process-tree evidence separately. If cleanup is unproven, the owner remains retained and replacement is blocked. Startup failures map to structured outcomes such as not signed in, missing runtime, provider refusal, or unproven exit.
References: src/…/acp-agent-connection.ts• L138-159 src/…/acp-agent-connection.ts• L196-225 src/…/acp-agent-connection.ts• L250-260 src/…/acp-agent-connection.ts• L319-328 src/…/acp-structured-session-adapter.ts• L70-95
Session replacement
When a provider reports that its saved conversation is gone or cannot be restored, Orca records a new provider handle in the session's handle chain. The old conversation remains represented by a warning when it had user-visible history. A missing conversation with no exchanged turn can be silently superseded.
The same rule applies after a session-lost error during a live prompt. Held messages do not enter the lost child. Before a new acquisition starts, the adapter stops the previous provider child. If it cannot prove that stop, it refuses acquisition instead of allowing two owners for one session.
References: src/…/acp-session-reopen-failure.ts• L25-50 src/…/acp-structured-handshake.ts• L151-205 src/…/acp-structured-session-adapter.ts• L70-95 src/…/acp-structured-turns.ts• L261-279
Auxiliary tasks
Model discovery, command discovery, conversation naming, copying, and text generation use short-lived provider work without taking over the user's live chat. They reuse the account and launch policy but use bounded input, output, time, and cleanup rules.
Disposable sessions are deleted when the provider supports deletion. Otherwise Orca isolates their storage and retains cleanup ownership until process exit is proven. Text tasks deny tools and user input because they are not interactive chat sessions.
References: src/…/acp-model-catalog-probe.ts• L165-245 src/…/acp-model-catalog-probe.ts• L247-283 src/…/acp-listing-session-models.test.ts• L25-93 src/…/acp-text-task-policy.ts• L16-23 src/…/acp-text-task-policy.ts• L54-97
Orca agent-session presentation
The ACP adapter exposes the provider through Orca's common structured agent-session surface. The host owns durable session records and journal writes, while local and paired clients use the same operations and receive the same session facts.
Session RPC surface
The shared surface supports session acquisition and attachment, message send, Stop, prompt answers, permission mode, model and effort selection, command reads, compaction, child-work Stop, history, and status updates. Fences and acquisition generations bind mutations to the current provider child. A stale client cannot safely change a newer acquisition.
References: src/…/acp-structured-session-adapter.ts• L65-105 src/…/acp-structured-session-adapter.ts• L106-153 src/…/acp-structured-session-adapter.ts• L156-227 src/…/acp-structured-session-adapter.ts• L279-303 src/…/acp-structured-session-contract.ts• L15-47
Conversation projection
The conversation view is journal-led. It combines durable rows with a short optimistic send state until the provider or journal proves the result. Accepted, queued, stopped, rejected, failed, and unknown sends remain distinct so a transport timeout does not become a false delivery claim.
The status view combines lead work, open questions, pending approvals, goals, and live child work. A lead turn can be done while child work keeps the session active. Provider retry, quota, sign-in, model, hook, and compaction outcomes become user-visible rows without exposing transport markers.
References: src/…/acp-timeline-translator.ts• L214-250 src/…/acp-turn-failures.ts• L57-99 src/…/acp-compaction-turn.ts• L72-142 src/…/acp-structured-session-adapter.ts• L106-153
Workspace integration
ACP sessions use the structured chat path inside an Orca workspace rather than a terminal-led view. The workspace session tab reads the common journal and status stream, while child-work evidence can also appear in workspace and mobile summaries.
For session tabs and workspace placement, see Agent workspaces. ACP uses the structured path rather than the legacy hook path in Agent integrations and hooks. Provider-session discovery outside an open chat is covered by AI Vault sessions. Native provider chat behavior is covered by Native agent conversations. Related execution and automation boundaries are covered by Workspace and worktree lifecycle and Automation services.
References: src/…/acp-structured-session-adapter.ts• L47-68 src/…/acp-child-sessions.ts• L133-180 src/…/acp-subagents.ts• L126-169
Change checklist
When these files or sections are changed, remember to consider these:
- Keep launch specs, account bindings, release checks, managed runtimes, skill roots, standing instructions, and provider handle rules aligned. A mismatch can select the wrong account or start without required chat context.
- Keep connection tracking, early-frame buffering, lane creation, history capture, and protocol-loss callbacks aligned. Startup cancellation and replay must not lose frames or leave an unowned process.
- Keep ACP capabilities, dialect capabilities, form and URL support, command filtering, child-stop probes, reactive wakeups, and client feature gates aligned with the provider release being launched.
- Keep model discovery policy, release checks, disposable storage, deletion or discard hooks, and attempted-model reporting aligned. A catalog must not describe an unconfirmed model or leave a temporary owner behind.
- Keep prompt admission, busy retry, option writes, hidden model commands, permission transitions, Stop, and queued steer rules aligned so one logical message cannot create two live prompts.
- Keep permission and form validation aligned with journal commit order and protocol cancellation. A claimed answer must not be withdrawn as if it was never saved.
- Keep provider event identity, journal ownership, replay boundaries, child-work evidence, reactive agent turns, thread goals, and lane ordering aligned. Late frames must revise the original row or be dropped.
- Keep root exit evidence, tree cleanup, auxiliary task ownership, provider handle chains, restore warnings, and replacement gates aligned. An unproven child must not be replaced or discarded.
Important failure modes
| Trigger | Consequence | Guard |
|---|---|---|
| The provider does not support a required ACP version, capability, or standing-instruction delivery | Orca can start a chat that cannot safely present its required behavior | Check release and advertised capabilities before session creation |
| Launch resolution uses current caller state instead of the durable session record | The provider can run in the wrong workspace or account | Build launch identity from the owning session record |
| A frame arrives before the journal lane exists and exceeds the early-frame bound | Startup can lose provider evidence or process unbounded input | Track the connection before handshake and keep a bounded early queue |
| A form or permission answer is invalid or arrives after Stop | The provider can receive an answer that the journal did not record | Validate offered values, commit first, and cancel unclaimed requests |
| A session-load frame is treated as live output | Reattach duplicates messages, tools, goals, or child work | Treat the complete attach window as history |
| A stream closes before process exit is proven | A running turn can be falsely settled and a replacement can start too soon | Mark the outcome unverifiable and wait for exit evidence |
| A previous provider child cannot be stopped before acquisition | Two provider owners can act on one Orca session | Refuse acquisition until exit is proven |
| A catalog probe uses a model-specific menu as a global default | A picker shows unsupported effort choices or a false default | Keep live and per-model provenance separate from catalog hints |
| A provider session is lost after a turn starts | A replacement can hide an unclear result or admit held work to the lost child | Preserve the handle chain and settle sends from available evidence |
| A child id has no confirmed provider Stop route | Stop can target the wrong child or claim cancellation without evidence | Expose targeted Stop only with a proven route and full identity |
| A late option response arrives after a newer write | An older model, effort, or mode can replace the current selection | Apply only the current write revision and require confirmation |
| A provider retry notice is treated as assistant text | The journal shows internal retry text as a user answer | Let the dialect map retry notices to one failure row |
| A provider reports a background task after its prompt ends without reactive-turn handling | The later result can attach to a settled prompt or remain absent from the session view | Give supported wakeups a separate quiet-bounded agent turn and retain task identity |
| A history match claims an unowned saved row | Catch-up can revise another session's journal item | Admit only owned rows and reject conflicting or stale history |
Key files
| File | Why to read it |
|---|---|
| src/…/acp-launch-contract.ts | Defines the provider launch, account, capability, catalog, instruction, and history contract. |
| src/…/acp-launch-registry.ts | Shows the supported provider launch policies and their high-level differences. |
| src/…/acp-structured-launch-resolution.ts | Shows how durable session identity becomes a checked provider launch. |
| src/…/acp-instructions.ts | Shows the shared goal of standing instructions across provider forms. |
| src/…/acp-registry-catalog.ts | Shows how official provider builds are selected for a host. |
| src/…/acp-registry-managed-runtime.ts | Shows how a verified registry build becomes an Orca-managed runtime. |
| src/…/acp-model-catalog-probe.ts | Shows catalog discovery using the same account and launch policy as chats. |
| src/…/acp-agent-connection.ts | Shows process ownership, sign-in output, exit evidence, and cleanup. |
| src/…/acp-structured-acquire.ts | Shows connection ownership, early frames, lane setup, and acquisition callbacks. |
| src/…/acp-structured-handshake.ts | Shows initialization, resume, replacement, replay, options, and provider handle creation. |
| src/…/acp-structured-session-adapter.ts | Connects the common session surface to sends, Stop, options, child work, and cleanup. |
| src/…/acp-dialect.ts | Defines the provider extension boundary. |
| src/…/acp-structured-options.ts | Shows live model, effort, mode, and command state. |
| src/…/acp-structured-prompts.ts | Shows journal-first request claiming and cancellation. |
| src/…/acp-structured-lane.ts | Shows ordered event admission, backpressure, and child-work publication. |
| src/…/acp-agent-turn-quiet.ts | Shows how unprompted provider work receives a bounded turn. |
| src/…/acp-timeline-translator.ts | Shows event ownership, turn state, event translation, and replay handling. |
| src/…/acp-agent-turns.ts | Shows reactive wakeups and background task turn boundaries. |
| src/…/acp-history-catch-up.ts | Shows bounded history import and journal-safe reconciliation. |
| src/…/acp-history-turn-matching.ts | Shows how replayed provider turns match existing Orca turns. |
| src/…/acp-session-update.ts | Shows how standard provider updates become messages, tools, plans, and usage rows. |
| src/…/acp-child-sessions.ts | Shows child-session placement and thread-scoped updates. |
| src/…/acp-structured-turns.ts | Shows prompt admission, steering, Stop, and send outcomes. |
| src/…/acp-structured-stop.ts | Shows grace periods and evidence-based turn stopping. |
| src/…/acp-session-slash-command.ts | Shows how provider commands and skills enter the shared session surface. |
| src/…/acp-live-permission-mode.ts | Shows provider-owned live permission mode changes. |