Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Feature: Cross-product model awareness (Chat → Code prompt compatibility) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46877•Fetched 2026-04-12 13:30:42
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
ridingyoridingyo
Participants
ridingyoridingyo
Timeline (top)
labeled ×2

Root Cause

  • Users are already managing token budgets carefully (using lower models in Code to save costs)
  • The current workaround requires users to manually "dumb down" prompts — defeating the purpose of using a smarter model for prompt authoring
  • This friction increases token waste (failed attempts, re-prompting) rather than reducing it

Fix Action

Fix / Workaround

  • Users are already managing token budgets carefully (using lower models in Code to save costs)
  • The current workaround requires users to manually "dumb down" prompts — defeating the purpose of using a smarter model for prompt authoring
  • This friction increases token waste (failed attempts, re-prompting) rather than reducing it
RAW_BUFFERClick to expand / collapse

Problem

When users write prompts in Claude Chat (e.g., Opus) intended for execution in Claude Code (e.g., Sonnet or Haiku), the chat model generates prompts calibrated to its own capability level. Lower-tier models in Code then fail to follow these prompts correctly, wasting tokens and producing poor results.

This is a system-level gap, not something users should manually compensate for.

Proposed Solutions

Option A — Explicit query: Chat asks the user which model they're using in Claude Code, then adjusts prompt complexity/specificity accordingly.

Option B — Internal sharing: Anthropic internally shares the user's Claude Code model setting with Chat, so it can automatically calibrate prompts for the target model's capabilities.

Why This Matters

  • Users are already managing token budgets carefully (using lower models in Code to save costs)
  • The current workaround requires users to manually "dumb down" prompts — defeating the purpose of using a smarter model for prompt authoring
  • This friction increases token waste (failed attempts, re-prompting) rather than reducing it

Additional Context

  • Also, the /usage stats comparison (e.g., "21x more tokens than Les Misérables") would be more useful if it showed the reference book's actual size (pages/tokens) for context. Without that, the comparison is meaningless to most users.

extent analysis

TL;DR

Implementing an internal sharing mechanism to calibrate prompts based on the target model's capabilities in Claude Code is likely the most effective fix.

Guidance

  • Identify the specific models in Claude Code that are being used and their respective capability levels to inform the calibration of prompts in Claude Chat.
  • Consider implementing Option B — Internal sharing to automatically adjust prompt complexity based on the target model, reducing the need for user intervention.
  • Evaluate the feasibility of Option A — Explicit query as a potential workaround, weighing the benefits of user input against the added complexity.
  • Assess the impact of token waste and failed attempts on the overall user experience and token budget management.

Example

No specific code example is provided due to the lack of technical implementation details in the issue.

Notes

The proposed solutions aim to address a system-level gap, and the chosen approach should prioritize minimizing user friction and token waste. The effectiveness of the solution may depend on the specific requirements and constraints of the Claude Chat and Claude Code systems.

Recommendation

Apply workaround Option B — Internal sharing, as it seems to be the most straightforward and effective way to calibrate prompts for the target model's capabilities without requiring user intervention.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#GPU compatibility#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING