"Allow once" on the Workflow usage warning persists skipWorkflowUsageWarning, silently disabling it

Resolved 💬 1 comment Opened Jun 5, 2026 by GitHubxSuperKai Closed Jul 11, 2026

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.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗