Cost Control Confirmation Prompt for AI Queries

Status Closed — not planned
Maintainer reply ✓ Yes — bcherny
Activity 8 comments · opened Feb 24, 2025 · closed Feb 5, 2026
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Bug Description
I just spent $0.20 on a query and I didn't mean to. I wish there was a way to specify per-prompt thresholds above which the system would ask for confirmation of whether inference is actually run.

Environment Info

  • Platform: macos
  • Terminal: Apple_Terminal
  • Version: 0.2.8
  • Feedback ID: d33a6a51-8333-4914-8e42-b78bf3d8bf4b

View original on GitHub ↗

8 Comments

bcherny collaborator · 1 year ago

Unfortunately there's no way to know ahead of time how much a query will cost. Will leave this open for tracking. Will noodle on how we might do this.

maschwenk · 1 year ago

@bcherny if you could just set a cost limit for a session up front that’d be ideal. then even if the limit is only enforced after each command is run, you can still limit the impact. In CU currently applying execution timeouts as a proxy for this, but would rather just say “take as long as you want, just don’t spend more than $20 on a given session.” We use Claude Code almost exclusively in CI so this is important to us.

github-actions[bot] · 10 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

mark-bfd · 10 months ago

Root Cause Identified: Transient workflow execution failure.

Investigation Findings:

  • Execution 85639 failed at 15:03:51-15:06:23 (error status)
  • This execution corresponds to missing pubspoke_article_id 24613
  • Article 24612 logged at 15:02:04, article 24614 logged at 15:13:03
  • 24613 gap confirms the failed execution was for this article

Technical Explanation:
WF4S workflow structure: Run Puppeteer Automation → Upsert Publishing Record
The logging happens AFTER Puppeteer completes. When the workflow failed between these nodes:

  • ✅ Article was published to Pubspoke (24613 exists)
  • ❌ No log entry was created in wf4s_publishing_log

Statistics:

  • 1 out of 20 recent executions failed (5% failure rate)
  • 19/20 articles logged successfully (95% success rate)

Resolution: Closing as transient failure. The article was published successfully; only the audit log entry is missing. Current 95% logging success rate is acceptable.

skfarhat · 9 months ago

Implementation Complete

Created a Playwright-based UI verification workflow with the /verify-ui command.

Files Created:

  • .claude/commands/verify-ui.md - Slash command documentation
  • apps/shell/e2e/ui-verify.spec.ts - UI verification tests
  • apps/shell/e2e/screenshots/.gitkeep - Screenshots directory

Available Verifications:

  • datetime-picker - Date/time picker in task modal
  • task-modal - Full task modal with all fields
  • weekly-planner - Main planner view with day columns
  • task-card - Individual task cards with badges

Usage:

/verify-ui datetime-picker
# or directly:
cd apps/shell && npx playwright test ui-verify --headed --grep "datetime-picker"

Screenshots are saved to apps/shell/e2e/screenshots/.

🤖 Closed by Claude Code

github-actions[bot] · 8 months ago

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

marcindulak · 8 months ago

While some comments posted on this issue seem not relevant to the problem, this issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at https://github.com/anthropics/claude-code/issues/16497. Please upvote that issue, so maybe it gets noticed.

github-actions[bot] · 8 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.