- Agent side: --cap-manifest plus --cap-speak stream-json binding with transcript-diff frames, diff/transcript artifacts, session config - Orchestrator: PTY driver (settle heuristics on PtyProc/TuiVtScreen), stream-json, ACP-stdio (permission/elicit/fs/terminal serving) and A2A drivers (dual draft/current spelling, SSE mapping) - Sessions, fleets: worktrees, master plans, mediated routing, budget refusal, audit log, research auto-answerer, --cap CLI - cap.md contract with drift tests; research/cap-protocol archive - Suites 1119 + 16 green
1.5 KiB
1.5 KiB
ACP session setup (session/new)
Metadata
| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | cap-protocol |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | ACP Session Setup |
| Source URL | https://agentclientprotocol.com/protocol/v1/session-setup.md |
| Source type | specification |
| Source date (published) | Unknown, not stated (living docs) |
| Date researched | 2026-10-18 |
| Researched by | tai (agent), model: Muse Spark, on behalf of retoor |
| Research method | direct page fetch, targeted read (session/new request/response; load-session section skimmed) |
| Confidence | High |
| Status | Active |
Summary
Session creation: session/new with {cwd, mcpServers: []} returns {sessionId}; agents advertising loadSession also accept session/load for resume. Tai needs only the create path.
Key findings
session/newparams are exactly{cwd, mcpServers}(servers carry name/command/args/env); tai sends an empty server list.- Result carries only
sessionId, the correlation key for every later call. - Resume via
session/loadexists but tai sessions are single-connection; not implemented.
Pros / strengths
- Trivial handshake; no negotiation beyond initialize.
Cons / limitations / caveats
- Targeted read; auth and load-session details not synthesized.
Relevance to tai
Exact session/new shapes for the ACP driver handshake.
Changelog
| Date | Change |
|---|---|
| 2026-10-18 | Initial dossier created. |