Group of 3 Under the hood
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.
Names in the bundleidleExitAfterMs