UX/Naming: "Code" is both a desktop-app mode and the product name "Claude Code" — overloaded terminology confuses users (esp. non-developers)

Area: UX / naming / terminology

The Claude clients/surfaces that exist today

• Claude desktop app (Mac/Windows): one app with three modes/tabs — Chat, Cowork, Code.
• Claude web (claude.ai) and the mobile apps: chat.
• Claude Code: a separate agentic product available across many surfaces — CLI (terminal), desktop app, IDE extensions (VS Code, JetBrains), web (claude.ai/code), mobile, even Slack.

Problem: the word "Code" is overloaded
In the desktop app, "Code" is just a mode/tab (next to Chat and Cowork). But "Claude Code" is also the name of a whole product that runs in the terminal / IDE / web. The same word means a mode in one place and a product/client in another, and the app you are using shows no distinct, user-visible name to tell them apart.

Real-world breakdown:

Someone asks me: "Do you use Claude Code?" I say "Yes" — because I use the Code mode in the desktop app. But they mean the Claude Code CLI. Neither of us realizes we are talking about different things.

This is worst for non-developers, who use the desktop app's Cowork/Code modes to process files (not to write code) and have no vocabulary to say which client/mode they mean.

Suggestion

• Disambiguate the overloaded "Code": give the desktop-app mode and the standalone product clearly distinct, user-visible names.
• Show the active client/mode name in the UI (window title, header, icon) so users can reliably say what they are in.
• Keep naming consistent across docs, support, and UI.

Related: #54140 (surfacing the active environment in the model's context) — related but model-facing; this issue is about user-facing naming.

Impact
Eliminates a real and growing source of miscommunication across the Claude client family, especially for non-developers.