[BUG] /bug command does not work

What is the output you are showing and what version of Claude Code?

1.0.24 (Claude Code) doesn't look like that; /bug prints a "modal" which submits (as described in the last point in your submission).

/bug
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ Submit Bug Report                                                                                                            │
│                                                                                                                              │
│ Describe the issue below:                                                                                                    │
│                                                                                                                              │
│                                                                                                                              │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
 Enter to continue · Esc to cancel

> /version

⏺ Let me check the Claude Code version for you.

⏺ Bash(claude --version)
  ⎿  1.0.24 (Claude Code)

⏺ Claude Code version 1.0.24

> /bug

⏺ I'll help you find and fix bugs in the codebase. What specific bug are you encountering?

@mulka can you clarify - are you talking about finding bugs in your code or filing a bug that exists in Claude Code? I have to assume the former, because AFAIK /bug already does the latter. Maybe update the title for clarity(?)

I'm talking about filing bugs in Claude Code itself. If it is a feature, it isn't working for me. See the responses I'm getting in the comments above.

It's working on Ubuntu for me. Can you add back in the environment information to the issue template? That might help the anthropic team triage your issue faster.

Environment

• Platform (select one):
• [ ] Anthropic API
• [X] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: 1.0.24
• Operating System: macOS 13.7.5
• Terminal: iTerm2

Bug Description

/bug isn't working

Steps to Reproduce

1. Open Claude Code
2. Type "/bug" and press enter

Expected Behavior

Expected to be able to file a bug with Claude Code itself

Actual Behavior

Different things happen each time I try. See other comments

Additional Context

@mulka

I just learned even built-in Claude Code /-commands are dynamic. For example, /terminal-setup is not in Alacritty. Maybe something is preventing /bug? Does it appear in the output of /help?

1.0.25 was just released, and the CHANGELOG mentions improved detection for /-commands.

thanks so much for the help from our friendly users here. we'll investigate—/bug should be available everywhere

Just retested with 1.0.27. /bug does not appear in the list of commands when I run /help.

╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code!                         │
│                                                   │
│   /help for help, /status for your current setup  │
│                                                   │
│   cwd: /Users/mulka/Documents/Code/claude-code    │
╰───────────────────────────────────────────────────╯


 What's new:
  • Slash commands: moved "project" and "user" prefixes to descriptions
  • Slash commands: improved reliability for command discovery
  • Improved support for Ghostty
  • Improved web search reliability
  • Improved /mcp output

> /bug

⏺ I'll help debug this issue. Can you please provide more information about
   the bug you're experiencing?

 Claude Code v1.0.27

 Always review Claude's responses, especially when running code. Claude has read
 access to files in the current directory and can run commands and edit files with
  your permission.

 Usage Modes:
 • REPL: claude (interactive session)
 • Non-interactive: claude -p "question"

 Run claude -h for all command line options

 Common Tasks:
 • Ask questions about your codebase > How does foo.py work?
 • Edit files > Update bar.ts to...
 • Fix errors > cargo build
 • Run commands > /help
 • Run bash commands > !ls

 Interactive Mode Commands:
  /add-dir - Add a new working directory
  /clear - Clear conversation history and free up context
  /compac - Clear conversation history but keep a summary in context. Optional:
         /compact [instructions for summarization]
  /config - Open config panel
  /cost - Show the total cost and duration of the current session
  /doctor - Checks the health of your Claude Code installation
  /exit - Exit the REPL
  /help - Show help and available commands
  /ide - Manage IDE integrations and show status
  /init - Initialize a new CLAUDE.md file with codebase documentation
  /mcp - Manage MCP servers
  /memory - Edit Claude memory files
  /migrate-installer - Migrate from global npm installation to local installation
  /model - Set the AI model for Claude Code
  /permissions - Manage allow & deny tool permission rules
  /pr-comments - Get comments from a GitHub pull request
  /release-notes - View release notes
  /resume - Resume a conversation
  /review - Review a pull request
  /statu - Show Claude Code status including version, model, account, API
        connectivity, and tool statuses
  /terminal-setup - Install Shift+Enter key binding for newlines
  /vim - Toggle between Vim and Normal editing modes

 Learn more at: https://docs.anthropic.com/s/claude-code


 Press Enter to continue…

Ooo... I found some Claude Code documentation that mentioned the /bug command:
https://docs.anthropic.com/en/docs/claude-code/troubleshooting#getting-more-help

I guess the /bug command is listed in the README for this repo too, so it must exist, right?

My Claude Code agrees with me that /bug is not implemented. Haha

> The /bug command doesn't seem to be implemented

⏺ Fetch(https://docs.anthropic.com/en/docs/claude-code/cli-usage)
  ⎿  Received 1.9MB (200 OK)

⏺ Fetch(https://docs.anthropic.com/en/docs/claude-code/cli-usage)
  ⎿  Received 1.9MB (200 OK)

⏺ You're right, the /bug command doesn't appear to be implemented in Claude
   Code. The documentation mentions slash commands exist, but I couldn't
  find details about a specific /bug command in the available
  documentation.

Claude is beyond reproach and doesn't like the implication of the existence of the /bug command. 😂

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

hi - this should be fixed in the latest version. if you are using bedrock / vertex / azure api keys in claude code, then you are not able to use the /bug command. thanks!

@catherinewu would be great if trying to use the /bug command told us that it doesn't work with bedrock / vertex / azure

The problem with > Unknown slash command: bug is not fixed in the latest Claude Code v2.0.55, because in certain circumstances it's a feature, not a bug. The availablility of the /bug command is controlled by environment variables like CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC and CLAUDE_CODE_DISABLE_BUG_COMMAND (see https://code.claude.com/docs/en/settings), and the /bug command is disabled on various providers, including Bedrock (see https://code.claude.com/docs/en/data-usage#default-behaviors-by-api-provider).

@catherinewu - when closing bugs, please try to provide more descriptive comments, including links to the official Claude Code documentation, because they may be hard to find.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.