Skip to content

docs(rfd): clarify usage accounting placeholders - #2061

Open
kocaemre wants to merge 1 commit into
agentclientprotocol:mainfrom
kocaemre:docs/usage-accounting-semantics
Open

docs(rfd): clarify usage accounting placeholders#2061
kocaemre wants to merge 1 commit into
agentclientprotocol:mainfrom
kocaemre:docs/usage-accounting-semantics

Conversation

@kocaemre

Copy link
Copy Markdown

Summary

  • Removes the provisional "across session / across all turns" wording from unstable end-turn Usage fields.
  • Aligns v1/v2 generated draft schema docs with the End-Turn Token Usage RFD language while leaving the per-turn vs cumulative decision open.

Verification

  • cargo +nightly run -p schema-generator --features unstable
  • cargo +nightly run -p schema-generator --features unstable,unstable_protocol_v2
  • npm run spellcheck
  • cargo +nightly check -p agent-client-protocol-schema --features unstable,unstable_protocol_v2
  • cargo +nightly fmt --all -- --check
  • npx prettier --check docs/rfds/end-turn-token-usage.mdx docs/protocol/v1/draft/schema.mdx docs/protocol/v2/draft/schema.mdx schema/v1/schema.unstable.json schema/v2/schema.unstable.json
  • git diff --check

Closes #1860

Signed-off-by: Emre K <110906681+kocaemre@users.noreply.github.com>
@kocaemre
kocaemre requested a review from a team as a code owner August 29, 2026 10:01
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.

PromptResponse.usage semantics are self-contradictory: "for this turn" vs. fields documented "across session" — implementations already diverge

1 participant