Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Workflow dispatch by scriptPath drops args; user-global ~/.claude/workflows/ not resolvable by name

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…

Fix Action

Fix / Workaround

Bug Description ---Title: Dynamic Workflow: scriptPath dispatch drops args; user-global ~/.claude/workflows/ not resolvable by name

  1. Workflow({ scriptPath, args }) runs the script but the args global is empty/undefined. Workflow({ name, args }) passes args fine. Expected: args passed regardless of dispatch mode.
  2. Workflow({ name: 'x' }) returns "not found" for a workflow at ~/.claude/workflows/x.mjs (user-global), while a plugin-shipped workflow (deep-research) resolves by name. Docs imply ~/.claude/workflows/ resolves with project-precedence — possibly symlinks aren't scanned, or a raw .mjs needs registering via /workflows save.

Use case: dispatching one workflow as an autonomous engine across many host repos, with per-run config. Currently neither mode gives global-findable and args.

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description ---Title: Dynamic Workflow: scriptPath dispatch drops args; user-global ~/.claude/workflows/ not resolvable by name

Body: Two issues building a reusable dynamic workflow (research preview, v2.1.154+):

  1. Workflow({ scriptPath, args }) runs the script but the args global is empty/undefined. Workflow({ name, args }) passes args fine. Expected: args passed regardless of dispatch mode.
  2. Workflow({ name: 'x' }) returns "not found" for a workflow at ~/.claude/workflows/x.mjs (user-global), while a plugin-shipped workflow (deep-research) resolves by name. Docs imply ~/.claude/workflows/ resolves with project-precedence — possibly symlinks aren't scanned, or a raw .mjs needs registering via /workflows save.

Use case: dispatching one workflow as an autonomous engine across many host repos, with per-run config. Currently neither mode gives global-findable and args.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.158
  • Feedback ID: f7e46a99-691e-4304-b7b3-eedbc818c084

Errors

[]

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] Workflow dispatch by scriptPath drops args; user-global ~/.claude/workflows/ not resolvable by name