{"version":"2.1.288","anchor":"bridge-environment-re-registration-can-run-proactively-rene","canonical_anchor":"bridge-environment-re-registration-can-run-proactively-rene","heading":"Remote Control bridge tracks environment secret expiry and can renew it ahead of time","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/bridge-environment-re-registration-can-run-proactively-rene","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote Control bridge tracks environment secret expiry and can renew it ahead of time\n\nThe Remote Control bridge now records when its environment secret expires and can re-register early to renew it; stop messages are reworked\n\n**Unclear.** What starts an early re-registration, and what sets the separate check-in interval, is not established.\n\n**What**\n\nRemote 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.\n\n- 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`.\n\n- When a re-registration is rejected, the error now includes the HTTP status and message.\n\n- The polling loop keeps track of when the secret expires and runs a separate, non-exclusive heartbeat interval.\n\n- 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.\n\nProactive re-registration sits behind the `tengu_bridge_env_reregister` gate, a switch Anthropic controls remotely. Nothing has been read about that gate.\n\n**Why**\n\nTracking 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.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}