{"version":"2.1.277","anchor":"terminal-image-support-capability-detection-reworked-into-a","canonical_anchor":"terminal-image-support-capability-detection-reworked-into-a","heading":"Terminal image-support capability detection reworked into a settle\/cache class","tier":"internal","area":"Terminal Rendering","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/terminal-image-support-capability-detection-reworked-into-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Terminal image-support capability detection reworked into a settle\/cache class\n\nTerminal image-support detection was rebuilt around a proper pending\/settled state machine\n\n**What**\n\nClaude Code detects whether the terminal it's running in can display images inline. That detection logic has been rewritten to use a small internal state machine with clear stages: not yet asked, currently asking, and settled (answer known), with a way for other parts of the app to be notified once the answer settles. This sits inside a new container class that groups terminal capability checks together. The `CLAUDE_CODE_FORCE_TERMINAL_IMAGES` environment variable still works the same way, immediately forcing the detection to a settled, true state.\n\n**Why**\n\nThis is an internal restructuring of how image-support detection is tracked; it should make the detection state more reliable to reason about, without changing the forced-on behavior of `CLAUDE_CODE_FORCE_TERMINAL_IMAGES`.\n\n- Area: Terminal Rendering\n- Names: `CLAUDE_CODE_FORCE_TERMINAL_IMAGES`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}