{"version":"2.1.281","anchor":"error-wording-for-sessions-hosted-by-the-desktop-app-no-sla","canonical_anchor":"error-wording-for-sessions-hosted-by-the-desktop-app-no-sla","heading":"Error messages in desktop-hosted sessions no longer tell you to type slash commands","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/error-wording-for-sessions-hosted-by-the-desktop-app-no-sla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Error messages in desktop-hosted sessions no longer tell you to type slash commands\n\nEffort, Opus-on-Pro and disabled-API-key errors now give desktop-hosted sessions advice they can follow instead of CLI commands like \/login\n\n**What**\n\nSeveral 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:\n\n- 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.\n\n- 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\".\n\n- 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\".\n\nIn the terminal the messages are unchanged.\n\n**Why**\n\nPeople 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."}