48 lines
1.5 KiB
Markdown
48 lines
1.5 KiB
Markdown
|
# 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/new` params 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/load` exists 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. |
|