Repository navigation
fix(agents): an agent's clock sync sends its control token - #808
Merged
Merged
Conversation
follow() posted clock/v1 sync_time with the sandbox's headers only, so an agent whose extension routes take its control token (protocol 0.1.582 and later) refused it with a 401, and every task that arms the env's clock failed at sync_env_clock or at the deploy of an agent while the clock runs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sarah-chitty-1
approved these changes
Nov 19, 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
a2a_agent/clock.pyfollow()posted clock/v1sync_timewith only the sandbox's request headers, without the agent's control token. Since #780, an agent built on protocol 0.1.582 or later refuses an extension call without that token. So with agent-env 0.9.1567 or later, every task that arms the env's clock fails, either atsync_env_clockor at the deploy of an agent while the clock runs, with "this route takes the agent's control token in the AgentEnv-Control-Token header". 0.9.1566 works.clock.pycame in after #743 made the existing callers send the token, so it was never updated, and no test covered a clock sync against a guarded agent.follow()sendsagent.control_headerswith the sandbox headers.agent_clock_test.py: the agent now has a control token, and the follower test asserts thesync_timerequest carries it.I checked every other module that resolves an agent extension endpoint. The trajectory follower, the episode proxy and agent-state capture take their headers from callers that already send the token. The validator steps without headers call only
/a2aor the card, which stay open. The always-on verifier reads the agent card's schema and makes no request.Testing
🤖 Generated with Claude Code


Confidence Score: 5/5
The change appears safe to merge; no actionable issues were found.Summary
Clock sync now sends the agent’s control token alongside sandbox headers, so guarded agents can follow the environment’s clock.
No actionable issues found. Tests were not run.
Reviews (1) · Last reviewed commit: "fix(agents): an agent's clock sync sends..." · Reviewed by Greptile