claude-code - 💡(How to fix) Fix Claude Code lacks independent reasoning — defaults to docs/assumptions instead of running available tools first [2 comments, 2 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#49066Fetched 2026-04-17 08:51:50
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×3commented ×2

Claude Code recommended a config fix (changing dots to dashes in model IDs) based on documentation, without first running the obvious verification command (gsd --list-models github-copilot) that would have shown the actual available models. The docs were correct for some providers but not for GitHub Copilot, which uses dot notation. The "fix" broke the working config.

Claude should run available CLI/verification tools before making assumptions based on documentation, especially when the answer is one command away.

Root Cause

Claude Code recommended a config fix (changing dots to dashes in model IDs) based on documentation, without first running the obvious verification command (gsd --list-models github-copilot) that would have shown the actual available models. The docs were correct for some providers but not for GitHub Copilot, which uses dot notation. The "fix" broke the working config.

Claude should run available CLI/verification tools before making assumptions based on documentation, especially when the answer is one command away.

RAW_BUFFERClick to expand / collapse

Summary

Claude Code recommended a config fix (changing dots to dashes in model IDs) based on documentation, without first running the obvious verification command (gsd --list-models github-copilot) that would have shown the actual available models. The docs were correct for some providers but not for GitHub Copilot, which uses dot notation. The "fix" broke the working config.

Claude should run available CLI/verification tools before making assumptions based on documentation, especially when the answer is one command away.

Steps to reproduce

  1. Ask Claude Code to fix a config referencing model IDs for GitHub Copilot
  2. Claude consults docs, finds dashes are correct for Anthropic provider
  3. Claude applies the fix without verifying against the actual provider's model list
  4. Config is now broken for the actual provider (Copilot uses dots, not dashes)

Expected behavior

Claude should run gsd --list-models <provider> (or equivalent verification command) before recommending or applying config changes based on documentation.

Actual behavior

Claude applied a doc-based fix that broke a working config, only running the verification command several messages later when explicitly prompted by the user.

extent analysis

TL;DR

Run the verification command gsd --list-models <provider> before applying config changes based on documentation to ensure accuracy for the specific provider.

Guidance

  • Verify the available models for the actual provider (in this case, GitHub Copilot) using the gsd --list-models command to avoid making incorrect assumptions based on documentation.
  • Check the documentation for the specific provider being used, as the correct notation may vary (e.g., dots for GitHub Copilot, dashes for Anthropic).
  • Before applying any config fixes, confirm that the proposed change aligns with the output of the verification command.
  • Consider establishing a practice of running verification commands as a preliminary step when troubleshooting or making config changes.

Example

No code snippet is necessary for this issue, as the focus is on the process of verification rather than code implementation.

Notes

The approach should be tailored to the specific provider and model in use, as different providers may have different notation conventions. This guidance assumes that a verification command like gsd --list-models <provider> is available and applicable.

Recommendation

Apply workaround: Run the verification command before making config changes. This ensures that any fixes are based on the actual models available for the provider in question, rather than potentially outdated or incorrect documentation.

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…

FAQ

Expected behavior

Claude should run gsd --list-models <provider> (or equivalent verification command) before recommending or applying config changes based on documentation.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING