Files

T

retoor cc1c130b51 CAP protocol both directions: agent speak plus orchestrator drivers (1.39.0)

- 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

2026-10-18 13:17:35 +02:00

2.2 KiB

Raw Blame History

CAP quickstart (cap run/chat CLI)

Metadata

Field	Value
Institute	Molodetz Institute — Research & Retrieval Division
Subject	cap-protocol
Document type	Source Dossier
Tier	1
Source title	CAP Quickstart
Source URL	https://github.com/rsclaw-ai/cap-protocol/blob/main/docs/quickstart.md
Source type	documentation
Source date (published)	Unknown, not stated (repo living doc)
Date researched	2026-10-18
Researched by	tai (agent), model: Muse Spark, on behalf of retoor
Research method	direct raw-file fetch, read in full (142 lines)
Confidence	High
Status	Active

Summary

Operator view of the reference orchestrator: fleet.yaml sessions/routes, cap run with static/llm/hybrid routing, cap chat interactive multi-agent talk, cap manifest validate/resolve, cap list-drivers, and the driver matrix (claude, openclaude, codex, opencode, aider, a2a:<url>, acp:<cmd>, grpc:<addr>, pty:<cmd>).

Key findings

Fleet patterns: pipeline, fan-out+join, parallel+human-collect, by-subtask split via a ```cap-subtasks fence convention (convention, not spec).
Routing strategies: static (routes block verbatim), llm (model picks next session), hybrid.
cap manifest validate/resolve confirms manifest tooling is expected orchestrator surface, not just internal plumbing.
Worktree isolation path in practice: .cap/<session>/, cleaned up at fleet end (differs from the profile's .cap-worktrees suggestion).
--bypass auto-approves all permissions at the fleet level.

Pros / strengths

Shows what "orchestrator" means operationally beyond the spec's MUSTs; directly reusable as tai's cap CLI command sketch.
The driver: URI scheme (a2a:, acp:, grpc:, pty:) is a compact dispatch design tai can borrow.

Cons / limitations / caveats

Reference-implementation surface, not spec; fleet.yaml schema and fence conventions are rsclaw inventions.
NoFleet error semantics or exit codes documented here.

Relevance to tai

Shapes tai's orchestrator UX (manifest validate/resolve, driver URIs, chat/run split) and confirms worktree cleanup as expected behavior.

Changelog

Date	Change
2026-10-18	Initial dossier created.

2.2 KiB Raw Blame History