claude-code - 💡(How to fix) Fix [BUG] Regression: Cost/status dialog data no longer visible to Claude in conversation context [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#52552Fetched 2026-04-24 06:04:07
View on GitHub
Comments
0
Participants
1
Timeline
7
Reactions
0
Participants
Timeline (top)
labeled ×6subscribed ×1

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

The only workaround is manual copy/paste, which is tedious and breaks automation.

Code Example

The only workaround is manual copy/paste, which is tedious and breaks automation.

  Environment

  - OS: Windows 11 Enterprise 10.0.26200
  - Claude Code version: 2.1.118
  - Shell: bash
  - Model: Claude Sonnet 4.5
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The /status and /cost commands now show a dialog to the user but do not pass the cost/usage data into the conversation context where Claude can see it. This is a significant regression that breaks cost tracking and budget management workflows.

Timeline of the regression

  1. ~5 days ago: Cost data was automatically visible to Claude in the conversation. User could say "track costs" and Claude could monitor and report on usage automatically. ✅
  2. ~2-3 days ago: User had to manually run /cost or /status, but the output was visible to Claude in the conversation. One extra step, but workable. 😐
  3. Today (April 23, 2025): Running /status or /cost shows a dialog to the user with graphs and cost information, but Claude only sees "Status dialog dismissed" in the conversation. Claude cannot see any of the actual cost data. ❌

Impact

This regression makes it impossible to programmatically track or analyze costs during a conversation. Users who need to:

  • Monitor costs against budgets
  • Track spending per work item/task
  • Analyze cost trends
  • Get cost summaries in reports

...must now:

  1. Pause their workflow
  2. Run /status
  3. Manually copy the numbers from the dialog
  4. Paste them into a message to Claude
  5. Resume work

This is a major UX regression for cost-conscious users.

What Should Happen?

The new status dialog with graphs and detailed information is excellent - the visual presentation is great. The issue is just that the data needs to be accessible to Claude when the user wants it to be (via an "OK" or "Share with Claude" button).

This would make the feature both visually appealing for users AND programmatically useful for Claude to help with cost management.

Error Messages/Logs

The only workaround is manual copy/paste, which is tedious and breaks automation.

  Environment

  - OS: Windows 11 Enterprise 10.0.26200
  - Claude Code version: 2.1.118
  - Shell: bash
  - Model: Claude Sonnet 4.5

Steps to Reproduce

  1. Start an interactive Claude Code session
  2. Have a conversation with some back-and-forth (generate some cost)
  3. Run /status or /cost
  4. Observe: Dialog appears with cost information
  5. Bug: Claude only sees "Status dialog dismissed" - no actual cost data
  6. Expected: Claude should be able to see and work with the cost data

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.118 (Claude Code)

Platform

AWS Bedrock

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The issue can be fixed by modifying the /status and /cost commands to pass the cost/usage data into the conversation context where Claude can see it, potentially by adding an "OK" or "Share with Claude" button to the dialog.

Guidance

  • Review the code changes made to the /status and /cost commands in the last few days to identify what broke the functionality of passing cost data to Claude.
  • Investigate the possibility of adding a button to the dialog that allows users to share the cost data with Claude, as suggested in the "What Should Happen?" section.
  • Check the documentation for the Claude Code version 2.1.118 to see if there are any known issues or workarounds related to this problem.
  • Test the /status and /cost commands with different inputs and scenarios to see if the issue is consistent or if there are any specific conditions that trigger the bug.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue seems to be a regression, and the last working version is not specified. It is essential to review the code changes made recently to identify the root cause of the problem.

Recommendation

Apply workaround: Modify the /status and /cost commands to pass the cost/usage data into the conversation context, potentially by adding a button to the dialog, as this is a significant regression that breaks cost tracking and budget management workflows.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Regression: Cost/status dialog data no longer visible to Claude in conversation context [1 participants]