ACP client: umbrella for protocol features Kit does not yet use when driving child harnesses
I maintainer di solito rispondono entro 1 giorno
@danielkov ci sta già lavorando.
Dal 13/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Tracking issue for Agent Client Protocol features that Kit does not use or handle when it acts as an ACP client, driving child harnesses through subagent, prompt, and fork (src/acp_child.rs, src/tools/subagent.rs). Audited against agent-client-protocol-schema 1.7.0 (fork rev 6e7e044) at Kit v0.1.134 (e75629c). Kit as ACP agent is tracked in #146.
Each item is intended to become its own issue or PR. Check off as they land.
1. Handshake
- Send
clientInfoand negotiate v2.InitializeRequest::new(ProtocolVersion::V1)is sent with defaultClientCapabilitiesand noclientInfo. Read the child's advertised version and use v2 when offered. v2 unlocks group 5.
2. Permissions
- Flip the permission handler to always allow.
permission_outcomeanswers everysession/request_permissionwithreject_always,reject_once, orcancelled, so a child that gates edits and shell behind permission is effectively read-only. Kit's base posture is unattended execution, so selectallow_alwayswhen offered, elseallow_once. Updatedocs/user/subagents-and-acp-harnesses.mdanddocs/user/security-limits-and-troubleshooting.md, which currently document the fail-closed policy. Supersedes the framing in #13.
3. Session setup
- Send
additionalDirectories. Never set onsession/neworsession/fork. Needed once the parent supports multi-root (#146). - Config options beyond
model. Only themodelselect is read and set (session/set_config_optionwith idmodel). Passthought_leveland anymodeor boolean options from the subagent profile. Consumeconfig_option_updateso the handle tracks the child's current state.
4. Prompt content
- Non-text prompt blocks. Every prompt is a single text block. Support
resource_linkand embeddedresourcefor file references, andimagewhere the child advertisespromptCapabilities.image, so the parent stops pasting file contents as text.
5. v2-only capabilities
- Steer running children. With v2 negotiated, use
session/injectinsteermode to redirect a child mid-turn instead of cancel plus re-prompt. - v2 stop reasons and replay. Read
state_updateidle stop reasons (v2session/promptreturns{}), and usesession/resumewithreplayFrom: startto rebuild child output after reconnect.
6. Updates consumed
- Surface dropped session updates.
ChildOutput::recordkeeps message chunks, tool calls, and plan. Dropped:usage_update(no child token or cost accounting),agent_thought_chunk,session_info_update(child titles),available_commands_update,notice,compaction_update,compaction_summary_chunk. Decide which belong inSubagentValue.updatesand which feed runlet progress so the TUI shows child activity. - Render
diffandterminaltool content. Passed through raw today;tool_call_update.contentis dropped when it restatesrawOutput. Map diff content onto the parent's own diff projection once #146 group 3 lands.
7. Lifecycle
- Reattach child sessions across Kit restarts. No
session/list,session/load, orsession/resumecalls. Child handles are parent-process-lived even when the child persists sessions. Record child session ids in the transcript and resume them on session load. Overlaps with #12. -
session/deletecleanup. Explicit branch disposal deletes persistent history when advertised; shutdown preserves it. #186, merged in #197. -
$/cancel_requestbefore abandoning.session/fork(30s) andsession/close(5s) hit fixed deadlines then drop the handle. Send protocol cancellation for the in-flight request first.
8. Auth
- Child authentication.
authMethodsin the child'sinitializeresponse are never read andauthenticate/auth/loginis never called. At minimum surfaceauth_requirederrors with themethodIdso the user can log in out of band. Optionally runterminalauth methods on the user's behalf.
9. Elicitation
- Handle
elicitation/createfrom children. No handler is registered, so the SDK answers method-not-found and the child's turn fails. Answerdeclineorcancelat minimum, or route form requests to the parent model as a structured question.
Explicitly out of scope
- Forwarding
mcpServersto children: subagents are separate agents and need not share the parent's tools. - Setting the child's permission mode through config options: superseded by group 2.
- Advertising client
fsorterminalcapabilities to children: children own their filesystem and shell.
Related: #11, #12, #13, #14, #15 (fork and permission behavior for generic harnesses), #146 (Kit as ACP agent).
- Lingua principale
- Rust
- Stelle
- 43
- Fork
- 5
- Merge medio
- 5h 43m
- PR unite (30g)
- 81
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di speakeasy-api/kit
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
speakeasy-api/kit#175 ·
I maintainer di solito rispondono entro 1 giorno
-
Implement session/deleteApertaenhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
speakeasy-api/kit#165 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
speakeasy-api/kit#151 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
speakeasy-api/kit#149 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 84/100
speakeasy-api/kit#148 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di speakeasy-api/kit
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
eclipse-opensovd/classic-diagnostic-adapter#616 ·
I maintainer di solito rispondono entro 2 giorni
-
documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
I maintainer di solito rispondono entro 1 giorno
-
track: content
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
0xAndersen/witness-log#10 ·
-
follow-up main-defect wave-A
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
carrick-sh/carrick#249 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
lugassawan/swe-workbench#799 ·
I maintainer di solito rispondono entro 1 giorno