Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Windows desktop app rejects dotted slash commands (e.g. /smithy.fix) — parses "." as a separator [1 participants]

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…
GitHub stats
anthropics/claude-code#49707•Fetched 2026-04-17 08:33:41
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
JMBattistaJMBattista
Participants
JMBattistaJMBattista
Timeline (top)
labeled ×5

Error Message

Note the error references "/smithy", not "/smithy.fix" — the client appears to be truncating the command name at the first "." and looking up only the prefix. The full command is correctly deployed at .claude/commands/smithy.fix.md and is listed in autocomplete.

Error Messages/Logs

Code Example

/smithy isn't a recognized command here. Some commands only work in the Claude Code terminal.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

In a Claude Code session hosted inside the Claude desktop app on Windows, slash commands whose names contain a dot (e.g. /smithy.fix, /smithy.strike) appear in the autocomplete picker but fail when submitted. The app returns:

"/smithy isn't a recognized command here. Some commands only work in the Claude Code terminal."

Note the error references "/smithy", not "/smithy.fix" — the client appears to be truncating the command name at the first "." and looking up only the prefix. The full command is correctly deployed at .claude/commands/smithy.fix.md and is listed in autocomplete.

The same command, same repo, same deployed file works in:

  • Claude Code TUI (CLI)
  • Claude iPad app (Code session)

It fails only in the Windows desktop app's Code session. It worked in the Windows desktop app yesterday, so this is a recent regression.

What Should Happen?

Submitting "/smithy.fix" should invoke the command backed by .claude/commands/smithy.fix.md, matching the behavior of the CLI and iPad app. Dots should be treated as part of the command name, not as a namespace/command separator.

Error Messages/Logs

/smithy isn't a recognized command here. Some commands only work in the Claude Code terminal.

Steps to Reproduce

  1. Clone a repo that deploys a dotted slash command. Minimal repro: git clone https://github.com/balexda/smithycli This copies the public repo with .claude/commands/smithy.fix.md (and other /smithy.* commands). While these are custom commands they exhibit the works in some places not others behavior being reported perfectly.
  2. Open the repo in a Claude Code session via the Claude desktop app on Windows.
  3. In the prompt box, type "/smithy." — autocomplete lists "smithy.fix" and other /smithy.* commands. Select "smithy.fix" (or type it out).
  4. Submit the prompt.
  5. Observe the response: "/smithy isn't a recognized command here. Some commands only work in the Claude Code terminal."
  6. For comparison, run the same command in Claude Code TUI (claude in a terminal) against the same repo — it executes correctly.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

I had last updated around 4/9 or 4/10. It used the old UI look and feel.

Claude Code Version

Claude for Windows | Claude 1.3109.0 (35cbf6) 2026-04-16T20:32:01.000Z

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Commands do appear in the auto-complete list, and auto-complete works, it just refuses to run the command.

extent analysis

TL;DR

The Windows desktop app's Code session is truncating slash command names at the first dot, causing commands with dots to fail, and a fix or workaround is needed to treat dots as part of the command name.

Guidance

  • Verify that the issue is specific to the Windows desktop app by testing the same command in other environments, such as the Claude Code TUI or iPad app, to confirm the behavior.
  • Check the autocomplete functionality to ensure it is correctly listing commands with dots, as it is in this case, to isolate the issue to command execution.
  • Investigate the difference in handling of command names between the Windows desktop app and other environments to identify the root cause of the truncation.
  • Consider testing commands with dots in other contexts within the Windows desktop app to see if the issue is limited to Code sessions or is a more general problem.

Notes

The issue appears to be a regression, as it was reported to have worked in a previous version, and the exact cause of the truncation is not specified in the provided information.

Recommendation

Apply a workaround, as the issue seems to be specific to the Windows desktop app and there is no clear indication of a fixed version that resolves this problem. The reason is that the issue is a recent regression and not a known fixed issue in a newer version.

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…
#api#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING