Skip to content

docs(rfd): record the implementation status of four v2 RFDs - #2867

Open
benbrandt wants to merge 1 commit into
mainfrom
docs/v2-rfd-plan-status
Open

benbrandt wants to merge 1 commit into
mainfrom
docs/v2-rfd-plan-status

Conversation

@benbrandt

@benbrandt benbrandt commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Records which steps of four v2 RFD implementation plans are done.

The RFD process describes the Preview stage as fully implemented, but the plans of these RFDs did not say where they stand. Background Work recorded only phase 1 of 3. Replay Complete recorded steps 1 and 2 of 4. The Prompt plan still ended on a choice between a v1 opt-in and a preview flow for v2. The Idempotency Keys plan had no status at all.

RFD text only. Each RFD gets a "Status on 2026-11-18" note under its plan and a revision-history entry.

What the notes say

RFD Done Open
Background Work Phase 1. Phase 2 in claude-agent-acp and in Zed Phase 2 in codex-acp. Phase 3 is ongoing
Replay Complete All four steps, for the TypeScript and Rust SDKs and both adapters The Kotlin SDK has no v2 types yet
Prompt Schema, tests, and docs (steps 1 to 3 and 5 to 7). Both adapters implement the lifecycle Step 4 belongs to adapters and conformance suites
Idempotency Keys Steps 1 to 3: schema, tests, and docs Steps 4 to 6: SDKs and both adapters

The Prompt RFD's open choice is replaced by what happened: v2 is developed as its own protocol version behind unstable_protocol_v2, so no v1 opt-in was needed.

For reviewers to confirm

The implementation claims were checked against the main branch of each public repository on 2026-11-17 and 2026-11-18. Please correct any that are out of date:

  • claude-agent-acp reports the background list and paused, handles tool_call/cancel and terminal/cancel, and sends replay_complete. It does not use idempotencyKey.
  • codex-acp sends replay_complete. It does not report the background list, handle the two cancel requests, or use idempotencyKey.
  • Zed reads the background list and sends both cancel requests for items that advertise cancel.
  • TypeScript and Rust SDKs expose replay_complete, and their example Agents send it. Neither sends or records idempotencyKey.
  • Kotlin SDK delivers a resuming session's updates before the response (feat: deliver session/update to the operations during session/load and session/resume (IJAI-3502) kotlin-sdk#146) and has no v2 types.

Checks

Prettier and typos pass, and all internal links in the four RFDs resolve.

The plans of the Background Work, Replay Complete, Prompt, and Idempotency
Keys RFDs did not say which steps are done. Background Work recorded only
phase 1, Replay Complete recorded two of four steps, and the Prompt plan
still ended on a choice between a v1 opt-in and a preview flow for v2.

- Add a dated status note to each plan, with what is done in this
  repository, in the SDKs, in claude-agent-acp and codex-acp, and in Zed.
- Replace the Prompt RFD's open choice with what happened: v2 is developed
  as its own version, so no v1 opt-in was needed.
- Add a revision-history entry to each RFD.
@benbrandt
benbrandt requested a review from a team as a code owner November 18, 2026 10:10

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant