{"version":"2.1.302","anchor":"stdin-or-tty-name-parser-replaced-by-json-object-parse","canonical_anchor":"stdin-or-tty-name-parser-replaced-by-json-object-parse","heading":"A macOS-only terminal name lookup is replaced by a JSON reader","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/stdin-or-tty-name-parser-replaced-by-json-object-parse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### A macOS-only terminal name lookup is replaced by a JSON reader\n\nA routine that asked macOS directly for the terminal's name is replaced by one that reads JSON text and checks its shape\n\n**Unclear.** It is not clear what Claude Code now uses this JSON reader for, or whether it still looks up the terminal name some other way.\n\n**What**\n\nClaude Code had a routine that looked up the name of the terminal device on macOS by calling a macOS system library directly. That routine is replaced by one that takes a piece of text, trims it, and reads it as JSON if it starts with `{`. JSON is a common format for structured data. The routine checks the result against an expected shape and returns nothing if the text does not start with `{`.\n\n**Why**\n\nClaude Code no longer makes that direct call into the macOS system library in this place.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}