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

1.8 KiB

Raw Blame History

Example manifest: openclaude

Metadata

Field	Value
Institute	Molodetz Institute — Research & Retrieval Division
Subject	cap-protocol
Document type	Source Dossier
Tier	1
Source title	CAP agent manifest for openclaude
Source URL	https://github.com/rsclaw-ai/cap-protocol/blob/main/examples/openclaude.toml
Source type	example config
Source date (published)	Unknown, not stated (repo living file)
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 (50 lines)
Confidence	High
Status	Active

Summary

The gRPC-first manifest: grpc = true with stream-json/ACP/A2A false, PTY fallback fully specified (◉ tool patterns again), metered cost.

Key findings

grpc = true is a bare boolean, not an address: the address presumably comes from out-of-band config (the quickstart's grpc:<addr> driver URI), a gap between manifest schema and CLI.
Third use of (?P<>) named groups in shipped examples, confirming the ERE-subset rule is aspirational; tai's parser should accept Python-compatible named groups and only reject backrefs/lookaround.
Otherwise structurally identical to claude-code, confirming one parser handles all five.

Pros / strengths

Documents the grpc-true shape tai must parse even though tai will not implement the gRPC binding (stdlib has no HTTP/2 or protobuf).

Cons / limitations / caveats

No address in the manifest makes the grpc flag alone undrivable; resolution rules are unspecified.

Relevance to tai

Sets the binding-selection test case (grpc preferred but unavailable in tai means fall through to PTY) and settles the regex-flavor decision.

Changelog

Date	Change
2026-10-18	Initial dossier created.

1.8 KiB Raw Blame History