Skip to content

docs(rfd): Move message ID RFD to Preview #1353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benbrandt merged 1 commit into from
Jun 3, 2026
+11 −2
Merged

docs(rfd): Move message ID RFD to Preview #1353

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,7 +192,6 @@
"rfds/custom-llm-endpoint",
"rfds/model-config-category",
"rfds/plan-operations",
"rfds/message-id",
{
"group": "v2 Draft",
"expanded": true,
Expand All @@ -212,7 +211,8 @@
"pages": [
"rfds/rust-sdk-v1",
"rfds/session-delete",
"rfds/session-usage"
"rfds/session-usage",
"rfds/message-id"
]
},
{
Expand Down
1 change: 1 addition & 0 deletions docs/rfds/message-id.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,6 +282,7 @@ Future RFDs may propose extending `messageId` to other update types if use cases

## Revision history

- **2026-06-03**: Moved the v1 portion of the RFD to Preview while v2-specific behavior remains part of the v2 draft work
- **2026-06-03**: Moved the RFD out of the v2 Draft group while keeping v2-specific behavior; added a dedicated `MessageId` type, and made v2 require message IDs on streamed message chunks while v1 keeps optional message IDs for compatibility
- **2026-06-02**: Updated the proposal so message IDs are Agent-generated only, removed client-provided prompt IDs and prompt response acknowledgments, and removed the UUID requirement in favor of opaque strings
- **2026-02-17**: Added "Message ID Acknowledgment" section to clarify that presence/absence of `userMessageId` in response indicates whether the Agent recorded the ID; clarified that UUID format is MUST (not SHOULD) since both sides generate IDs; renamed response field to `userMessageId` for clarity (request keeps `messageId`)
Expand Down
8 changes: 8 additions & 0 deletions docs/rfds/updates.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,14 @@ rss: true

This page tracks lifecycle changes for ACP Requests for Dialog. For broader ACP announcements, see [Updates](/updates).

<Update label="June 3, 2026" tags={["Preview"]}>

## Message ID RFD moves to Preview stage for v1

The v1 portion of the RFD for adding message IDs to streamed message chunks has been moved to Preview stage. Please review the [RFD](/rfds/message-id) for more information on the current proposal and provide feedback before the v1 behavior is stabilized.

</Update>

<Update label="June 3, 2026" tags={["Preview"]}>
## Session Usage RFD moves to Preview stage

Expand Down