{"version":"2.1.242","anchor":"turn-handling-moved-out-of-the-repl-into-the-turn-controller","canonical_anchor":"turn-handling-moved-out-of-the-repl-into-the-turn-controller","heading":"Turn handling moved out of the REPL into the turn controller","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/turn-handling-moved-out-of-the-repl-into-the-turn-controller","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Turn handling moved out of the REPL into the turn controller\n\nTurn handling moved out of the prompt loop into the turn controller with nothing changing on screen.\n\n**What**\n\nWork that lived in the interactive prompt loop now belongs to the turn object, with no change to what happens on screen.\n\n**Details**\n\n- Moved: loading-state reset, spinner tip selection, session signal tracking (bash tools, hosts, tools used), rate-limit auto-continue arm\/cancel\/prefill\/retract, initial message submission with the resume partial-output hint, and queued input execution.\n- Many separate references, including file-read state, session env vars, tool state, memory selection, isolation latch, content replacement, tool and MCP computation, dialog requests and sandbox verdicts, were collapsed into one `scope` object on the host.\n- The telemetry involved already existed in the previous build.\n\n**Evidence**\n\n`prefillRateLimitAutoQueueContinue`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}