Skip to content

fix(agents): an agent's clock sync sends its control token - #808

Merged
earakely-scale merged 1 commit into
mainfrom
edgararakelyan/clock-sync-control-token
Nov 19, 2026
Merged

earakely-scale merged 1 commit into
mainfrom
edgararakelyan/clock-sync-control-token

Conversation

@earakely-scale

@earakely-scale earakely-scale commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

a2a_agent/clock.py follow() posted clock/v1 sync_time with 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 at sync_env_clock or 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.py came 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() sends agent.control_headers with the sandbox headers.
  • agent_clock_test.py: the agent now has a control token, and the follower test asserts the sync_time request 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 /a2a or the card, which stay open. The always-on verifier reads the agent card's schema and makes no request.

Testing

  • CI.

🤖 Generated with Claude Code

RetriggerView in GreptileConfidence 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.

  • Agent clock sync sends the control token with its request.

No actionable issues found. Tests were not run.

Reviews (1) · Last reviewed commit: "fix(agents): an agent's clock sync sends..." · Reviewed by Greptile

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>
@earakely-scale
earakely-scale merged commit dc380fa into main Nov 19, 2026
26 of 33 checks passed
@earakely-scale
earakely-scale deleted the edgararakelyan/clock-sync-control-token branch November 19, 2026 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants