Use /bug to Report Issues with Claude Code Directly from Your Session
Found a bug in Claude Code? Don't just move on — report it so it gets fixed for everyone. The /bug command makes reporting frictionless.
/bug
Claude Code captures the relevant session context — what you were doing, what went wrong, and diagnostic information — and packages it into a report. You add a description of what happened, and it's sent.
This is worth using when:
# Claude made an edit that corrupted a file
/bug
# A tool call failed with a cryptic error
/bug
# Claude claimed to edit a file but nothing changed
/bug
# The response was cut off or garbled
/bug
# An MCP tool stopped working after an update
/bug
Good bug reports include:
- What you asked — the prompt that triggered the issue
- What happened — the unexpected behavior you saw
- What you expected — what should have happened instead
# After hitting an issue, type:
/bug
# Then describe: "Asked Claude to edit config/app.php but it edited
# config/auth.php instead. The file path in my prompt was explicit."
The automatic context capture is the key advantage over filing issues manually — /bug includes session metadata, tool call history, and configuration details that would be tedious to gather yourself.
You can also report issues on GitHub if you prefer:
# The GitHub issues page for Claude Code
# https://github.com/anthropics/claude-code/issues
Every bug you report makes Claude Code better for the next developer — /bug makes reporting it take 10 seconds instead of 10 minutes.
via Claude Code
Log in to leave a comment.
When typing feels slow — describing a complex bug, explaining architecture, or thinking through a problem out loud — press Option+V to switch to voice input. Speak naturally and Claude Code transcribes your words into a prompt, so you can describe what you need at the speed of thought.
When Claude is heading down the wrong path — editing the wrong file, writing code you don't want, or giving a long explanation you don't need — press Escape to stop it immediately. You keep everything it did up to that point and can redirect with a new prompt.
Closed a session and realized you weren't done? Pass --continue (or -c) when launching Claude Code to pick up exactly where you left off — same context, same files, same conversation history — without re-explaining what you were working on.