Bug: Claude cannot execute custom slash commands from within conversations

Resolved 💬 5 comments Opened May 20, 2025 by benpchandler Closed Jan 7, 2026

Bug Report: Claude cannot execute custom slash commands from within conversations

Description

When using Claude Code with custom slash commands (in .claude/commands/), Claude is unable to execute these commands from within the conversation, even though they appear to work when a user runs them directly.

Steps to Reproduce

  1. Set up a project with custom Claude commands in .claude/commands/ directory
  2. Start a conversation with Claude
  3. Ask Claude to execute one of these custom commands (e.g., project:pr-reviewb)
  4. Observe that nothing happens when Claude tries to run the command

Expected Behavior

Claude should be able to execute custom slash commands from within the conversation, just as a user can.

Actual Behavior

When Claude attempts to run a custom command (either with or without the slash prefix), nothing happens. The command isn't recognized or executed.

Context

I was having a conversation with Claude about PR review commands in my project. I could run commands like project:pr-reviewc and project:pr-reviewb directly from my terminal, and Claude could see the outputs. However, when I asked Claude to execute the same commands, Claude was unable to do so.

This creates a confusing experience where Claude can analyze the commands and see their output when I run them, but cannot execute them itself when asked to.

Environment

  • Claude Model: claude-3-7-sonnet
  • Using Claude Code CLI
  • Custom commands defined in .claude/commands/ directory

Additional Information

This limitation significantly reduces Claude's ability to be proactive in helping with project-specific tasks. If Claude could execute custom commands, it could perform more complex project-specific tasks without requiring the user to manually type each command.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗