You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
DesktopArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
Unclear The finding does not name which applications count as desktop hosts.
What
Several error messages now have a second wording used when Claude Code is running inside a desktop-type host app. This applies when the session is non-interactive, the host is one of the recognised desktop-type entrypoints and is not a child session (a session started by another session), and the host is not claudecode. In that case:
The error about using effort without thinking says "you can lower effort to High" instead of telling you to use --effort high or the effortLevel setting.
The error about using Opus on a Pro plan says "sign out and sign in again" instead of "run /logout and /login for the plan to take effect".
When an organisation has turned off API key sign-in, the managed-key case says "Sign in again with your claude.ai account" instead of "Run /login to sign in".
In the terminal the messages are unchanged.
Why
People using Claude Code through a desktop host cannot type slash commands or command-line flags, so the old messages told them to do something they had no way to do. The new wording describes the same fix in terms of the app itself.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not name which applications count as desktop hosts.
Anthropic's release notes agreeAdded telemetry.resource_attributes to the Claude apps gateway config, to put fixed labels on the telemetry of Claude Desktop and /login…
