{"version":"2.1.281","anchor":"remote-control-bridge-declines-project-thread-sessions-when","canonical_anchor":"remote-control-bridge-declines-project-thread-sessions-when","heading":"Remote Control bridge declines project-thread sessions when at capacity","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-bridge-declines-project-thread-sessions-when","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control bridge declines project-thread sessions when at capacity\n\nRemote Control now declines recently created project-thread sessions when it is already at its session limit\n\n**Unclear.** The finding does not define a project-thread child session or say how recent counts as recently created.\n\n**What**\n\nRemote Control lets you run Claude Code sessions on a machine from somewhere else. Its connecting piece is called the bridge, and it can run up to a set number of sessions, `maxSessions`. When the bridge is full and a new session arrives, it now looks that session up. What happens next depends on what it finds:\n\n- Recently created project-thread child session: the bridge logs \"Declined session \u2026 already running N of M sessions.\", stops the incoming work, marks the session on the server as refused for lack of capacity, and archives it once the mark is saved.\n\n- Any other session: the bridge records the same `at_capacity` event as before.\n\n- A slot frees up during the lookup: the bridge starts the session anyway.\n\n**Why**\n\nWhen too many sessions are already running, new sessions of this kind are now explicitly turned away and tidied up, rather than waiting on a busy machine."}