{"version":"2.1.273","anchor":"bridge-session-spawn-session-tag-prefetch-broadened-to-more","canonical_anchor":"bridge-session-spawn-session-tag-prefetch-broadened-to-more","heading":"Bridge session spawn: session-tag prefetch broadened to more triggers","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/bridge-session-spawn-session-tag-prefetch-broadened-to-more","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bridge session spawn: session-tag prefetch broadened to more triggers\n\nMore conditions now trigger a session-tag prefetch before spawning a Remote Control bridge worker\n\n**What**\n\nBefore spawning a bridge worker for a Remote Control session, Claude Code decides whether to first fetch the session's tags. This decision now checks a wider set of conditions than before: whether spawning is enabled, whether a positive idle-exit timeout is configured (via `tengu_bridge_rc_child_idle_exit_ms`, and only when not in single-session spawn mode), whether restart-resume is enabled (via `tengu_bridge_rc_child_restart_resume`), or whether an auto-mode environment is configured. Previously this used a narrower, inline check.\n\n**Why**\n\nBroadening the check means the session-tag prefetch happens whenever any of these bridge features that depend on it are active, rather than only in the one case the old inline check covered.\n\n- Flag `tengu_bridge_rc_child_restart_resume`: Not enough to say (read for one account on one subscription tier against v2.1.273; this account: no value returned, anonymous baseline: no value returned, compiled default: 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.\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}