Remote Control lets you drive a Claude Code session from somewhere else. It keeps a saved pointer to the environment it last used, so it can pick that environment up again. Three things have changed:
- Reuse check: on startup, Claude Code reads the pointer together with the machine and account it was written for. If the pointer is for another folder or another machine, Claude Code sets up a fresh environment instead.
- Keep-alive: when the connection fails, Claude Code keeps retrying while a tool is still running instead of giving up after the usual timeout.
- Shutdown: writing the pointer during shutdown now has a time limit.
Before, the pointer was reused unless the process that wrote it was still running.
Remote Control no longer reuses an out-of-date environment from another folder or machine, and no longer drops the connection while a tool is still working.
tengu_bridge_requires_action_details On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.323: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.323. It isn't a statement about your account. What a flag value here can and cannot tell you