What
Remote Control lets you drive a Claude Code session on your machine from elsewhere. The bridge is the part of Claude Code that keeps it registered with the service, using an environment secret, a private credential. Registration now records environment_secret_expires_in, which says when that secret expires.
- Re-registration can now be triggered proactively, before anything has failed. Before, it ran only after a failure and always re-queued sessions. A proactive re-registration returns a new secret with its expiry, does not re-queue sessions, and reports
re-registered in place; secret renewed. - When a re-registration is rejected, the error now includes the HTTP status and message.
- The polling loop keeps track of when the secret expires and runs a separate, non-exclusive heartbeat interval.
- When a session is stopped, the stop output is now written only after the child process has been killed and has finished, in a new
[stopped ...]format.
Proactive re-registration sits behind the tengu_bridge_env_reregister gate, a switch Anthropic controls remotely. Nothing has been read about that gate.
Why
Tracking the expiry and renewing in place should let a Remote Control connection get a fresh secret without dropping and re-queuing your sessions. Rejections now carry the server's status and message, which makes failures easier to diagnose.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What starts an early re-registration, and what sets the separate check-in interval, is not established.