The remote-control bridge now re-registers sessions it was running when it restarted.
tengu_daemon_upgrade_defer_busy Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: off
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When the headless remote-control bridge shuts down it now records which sessions were active, and on restart it re-registers and re-queues them instead of losing them.
- The saved list and its timestamp are read back from the bridge's pointer file, and only reused if the timestamp is inside a fixed freshness window.
- Startup logs
re-queuing N session(s) interrupted by the previous shutdown, and each resume reports success orenv_reuse_declined. - Persisting the list on shutdown is controlled by
tengu_daemon_upgrade_defer_busy, which falls back to on, so absent remote config the daemon does persist. - Pointer-file writes moved from a bare hourly timer onto a write queue.
bridge_shutdown_requeue
Strings lifted out of the shipped bundle, so the claim above can be checked against them.