Feature Request: Claude should know its runtime environment (Desktop App vs CLI vs Web)

Summary

Claude Code does not know which interface it is running in. When asked, it cannot distinguish between the Desktop App, the CLI/Terminal, or the Web interface. This leads to incorrect assumptions and confusing guidance for users.

Problem

As a non-technical user working in the Claude Code Desktop App, Claude repeatedly assumed I was using the Terminal/CLI and gave instructions referencing "the terminal" — even though I have never used it. When corrected, Claude acknowledged it simply does not receive this information.

This is a fundamental context gap. Claude receives system information like the OS (Darwin), shell (zsh), and git branch at session start — but not which Claude Code interface it is running in.

Expected Behavior

Claude should be aware of its runtime environment from the start of every session. For example, the system context could include a field like:

Runtime: Claude Code Desktop App (v2.0.76)

or

Runtime: Claude Code CLI (v2.0.76)

This would allow Claude to:

• Use correct terminology ("here in the app" vs "in the terminal")
• Know which features are available (e.g., App Preview only in Desktop App)
• Provide appropriate guidance based on the actual interface
• Avoid confusing non-technical users with wrong assumptions

Why This Matters

For non-technical users, being told they are "in the terminal" when they are clearly in a desktop application is disorienting. It undermines trust and makes the interaction feel like Claude lacks basic situational awareness — similar to talking to someone who doesn't know whether they're indoors or outdoors.

Suggested Implementation

Add the runtime environment identifier to the system context that Claude receives at session start, alongside existing fields like platform, shell, and OS version.

---

Filed on behalf of a user via Claude Code Desktop App.