Chat-Only Mode (reads codebase, no edits, no commands)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Every mode in Claude Code is biased toward doing. But for complex projects, the highest-leverage work happens before coding: choosing the approach with the lowest implementation cost.

Right now, users who need design discussions are forced into a broken workflow:

• Claude Desktop can discuss but can't see the codebase — you end up explaining your own code structure verbally.
• Claude Code can see everything but won't stop trying to edit — even Plan Mode generates documents.

I've been building two complex projects for 3 months. Both had moments where a 10-minute design conversation changed the entire implementation path:

• Translator: A design chat replaced an entire error-recovery chain with 2 parameters at the source. Weeks of debugging avoided.
• Trading terminal: A design discussion turned a 5-state machine with timers and concurrency locks into 2 variables, zero timers, zero concurrency risk.

Both conversations happened in Claude Desktop, then I copy-pasted conclusions into Claude Code — every single day for 3 months.

Proposed Solution

A fourth interaction mode: same codebase access, same context loading, tool calls (Edit, Write, Bash) disabled. Pure discussion with full project awareness.

Users open two panels side by side — one for design discussion, one for execution. No copy-paste, no context loss, no window switching.

Alternative Solutions

Current workaround: use Claude Desktop (web) for design discussions, then manually copy-paste conclusions into Claude Code. This loses codebase context and requires explaining code structure verbally every time.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

1. I'm building a real-time translator with complex audio pipeline
2. Before implementing a new feature, I open Chat-Only mode in one panel
3. Claude sees my full codebase and discusses the optimal approach — without touching any files
4. Once we agree on the design, I switch to the execution panel and Claude implements it
5. This eliminates daily copy-paste between Claude Desktop and Claude Code

Additional Context

_No response_