Repository navigation
AGENTS.md: require wire-compatible proto changes - #189
Merged
Merged
Conversation
Tunnel servers and agents deploy independently and run mixed versions, so a proto change must never make existing functionality depend on which side is upgraded first. New features may need both sides before they light up, but an older peer must degrade gracefully, not fail. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ashiramin
approved these changes
Nov 10, 2026
akwirick
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Protocol compatibility section to
AGENTS.md. Tunnel servers and agents deploy independently and run mixed versions, so changes underproto/must be wire compatible in both directions. Existing functionality must never depend on which side is upgraded first.oneofmembers. Never renumber, reuse, or change the type or meaning of an existing field. A retired field's number and name arereserved.oneofmembers instead of treating them as a protocol error.#186 follows these rules: its
CallCancelfields 3–7 and its agent-report grace period are the examples.Test plan
🤖 Generated with Claude Code