[BUG] Regression: Cost/status dialog data no longer visible to Claude in conversation context

Resolved 💬 2 comments Opened Apr 23, 2026 by JerryHanelPak Closed May 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] 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_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗