{"version":"2.1.275","anchor":"repl-mode-entrypoint-now-classified-into-terminalhostevals","canonical_anchor":"repl-mode-entrypoint-now-classified-into-terminalhostevals","heading":"REPL-mode entrypoint now classified into terminal\/host\/evals for telemetry","tier":"internal","area":"REPL","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/repl-mode-entrypoint-now-classified-into-terminalhostevals","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### REPL-mode entrypoint now classified into terminal\/host\/evals for telemetry\n\nREPL-mode startup is now classified as terminal, host, or evals for telemetry purposes\n\n**What**\n\nA new function determines whether the current run counts as a 'terminal', 'host', or 'evals' entrypoint for the async REPL (the interactive prompt loop), based on the entrypoint type, whether input is streamed, the `sdkUrl`, and `asyncReplRequested`. This classification feeds a couple of new telemetry emitters.\n\n**Why**\n\nThis lets Claude Code distinguish and report which kind of environment is starting an async REPL session, which can help with understanding usage across terminal, host, and evaluation contexts.\n\n- Area: REPL\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}