claude-code - 💡(How to fix) Fix claude agents: workflow slash-commands missing from dispatch-input completion (regression-adjacent to #61424)

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…

Inside an active Claude Code session, typing a slash-prefix surfaces autocomplete suggestions for workflows (user-defined /<name> workflow constructs) — but the same prefix in the claude agents dispatch input does not.

This appears adjacent to #61424 (fixed), but the workflow case still doesn't surface.

Root Cause

Inside an active Claude Code session, typing a slash-prefix surfaces autocomplete suggestions for workflows (user-defined /<name> workflow constructs) — but the same prefix in the claude agents dispatch input does not.

This appears adjacent to #61424 (fixed), but the workflow case still doesn't surface.

Fix Action

Fix / Workaround

Inside an active Claude Code session, typing a slash-prefix surfaces autocomplete suggestions for workflows (user-defined /<name> workflow constructs) — but the same prefix in the claude agents dispatch input does not.

  1. In a repo that has a registered workflow (e.g. /g9-sdlc), start an active Claude Code session.
  2. Type /sdl at the prompt. The completion popup correctly surfaces /g9-sdlc with its description.
  3. From a shell, run claude agents (from a parent directory or any directory; the target repo is reachable via @<repo>).
  4. In the dispatch input, type @<repo> /sd (where <repo> is the same repo that has /g9-sdlc registered).
  5. Expected: the dispatch input suggests /g9-sdlc the same way the in-session prompt does.
  6. Actual: only enter to create · esc to clear is shown — no slash-command suggestion.

claude agents dispatch input (broken) — typing @<repo> /sd

RAW_BUFFERClick to expand / collapse

Summary

Inside an active Claude Code session, typing a slash-prefix surfaces autocomplete suggestions for workflows (user-defined /<name> workflow constructs) — but the same prefix in the claude agents dispatch input does not.

This appears adjacent to #61424 (fixed), but the workflow case still doesn't surface.

Environment

  • Claude Code: 2.1.153
  • OS: macOS (Darwin 25.5.0)
  • Workflow under test: a workflow registered as /g9-sdlc in the target directory (described in agent view as [dynamic workflow] g9 feature SDLC: clarify → plan → gate → dev → review…)

Repro

  1. In a repo that has a registered workflow (e.g. /g9-sdlc), start an active Claude Code session.
  2. Type /sdl at the prompt. The completion popup correctly surfaces /g9-sdlc with its description.
  3. From a shell, run claude agents (from a parent directory or any directory; the target repo is reachable via @<repo>).
  4. In the dispatch input, type @<repo> /sd (where <repo> is the same repo that has /g9-sdlc registered).
  5. Expected: the dispatch input suggests /g9-sdlc the same way the in-session prompt does.
  6. Actual: only enter to create · esc to clear is shown — no slash-command suggestion.

Screenshots

In-session completion (works) — typing /sdl inside an active session

in-session completion working

claude agents dispatch input (broken) — typing @<repo> /sd

agents-view dispatch input missing completion

Expected behavior

Per the agent view docs:

/<command> — Suggest skills and commands to dispatch as the prompt

Workflows are user-defined slash-commands and should be suggested the same way skills and built-in commands are.

Hypotheses (not asserted, just to narrow the search)

  • The dispatch-input completion source may enumerate skills and commands but not workflow constructs.
  • Or it may enumerate them from the parent CWD only and not from the @<repo>-resolved target directory.

Related

  • #61424 — fixed an adjacent completion issue in the agents-view dispatch input, but did not cover workflows.

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…

FAQ

Expected behavior

Per the agent view docs:

/<command> — Suggest skills and commands to dispatch as the prompt

Workflows are user-defined slash-commands and should be suggested the same way skills and built-in commands are.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING