Group of 3 Nothing to try yet
No documentation found
Bridge-spawned sessions can now be set to exit after an idle period, reporting status as idle rather than completed
What
- The idle-exit helper (triggered by
CLAUDE_CODE_EXIT_AFTER_STOP_DELAY) now accepts a callback that runs right before the process actually exits, with errors from it swallowed. - Bridge-spawned sessions can now be given an
idleExitAfterMsvalue; when greater than 0, the child session getsCLAUDE_CODE_EXIT_AFTER_STOP_DELAYset, and on clean exit its reported status is "idle" instead of "completed". - New scaffolding computes whether a spawned bridge session should be tagged
rc-child, gated behind thetengu_bridge_child_auto_modeflag, and passes it to session spawn along with newprojectThreadChildandidleExitAfterMsparameters — though the other two triggering conditions are currently hardcoded to always false.
Why This lays groundwork for bridge sessions to shut themselves down after a period of inactivity rather than running indefinitely or being reported as fully completed, though some of the related triggering logic isn't fully wired up yet.
Feature flag
tengu_bridge_child_auto_mode 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.269: off
Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this build
New in this build: tengu_bridge_child_auto_mode