Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix "Allow once" on the Workflow usage warning persists skipWorkflowUsageWarning, silently disabling it

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…

Clicking Allow once on the Workflow tool's usage/cost warning prompt writes skipWorkflowUsageWarning: true into user settings.json, permanently disabling the warning. "Allow once" should authorize only the current run, not persist a global preference. A user who wants to keep the cost warning has to manually delete the key after every workflow they approve.

Root Cause

Clicking Allow once on the Workflow tool's usage/cost warning prompt writes skipWorkflowUsageWarning: true into user settings.json, permanently disabling the warning. "Allow once" should authorize only the current run, not persist a global preference. A user who wants to keep the cost warning has to manually delete the key after every workflow they approve.

Code Example

"agentPushNotifEnabled": true,
+  "skipWorkflowUsageWarning": true
RAW_BUFFERClick to expand / collapse

Summary

Clicking Allow once on the Workflow tool's usage/cost warning prompt writes skipWorkflowUsageWarning: true into user settings.json, permanently disabling the warning. "Allow once" should authorize only the current run, not persist a global preference. A user who wants to keep the cost warning has to manually delete the key after every workflow they approve.

Environment

  • Claude Code 2.1.146
  • Windows 11

Repro (deterministic)

  1. Ensure user settings.json has no skipWorkflowUsageWarning key (warning enabled).
  2. Run any Workflow (e.g. a trivial one-agent script).
  3. When the usage/cost warning prompt appears, click Allow once.
  4. Inspect settings.json:
   "agentPushNotifEnabled": true,
+  "skipWorkflowUsageWarning": true

Reverting the key and re-running reproduces it every time.

Expected

"Allow once" authorizes the current run only; the warning reappears on the next run. Persisting suppression should require an explicit "don't show again" / "always allow" affordance.

Actual

The flag is persisted on the first approval, so the warning never appears again until the key is manually removed.

Notes

  • skipWorkflowUsageWarning is currently undocumented in the settings reference.

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