// 30 tips tagged "debugging"
Hand Claude your heap snapshots or server code and ask it to trace memory leaks — it spots missing event listener cleanup, unbounded caches, and stream lifecycle bugs that are easy to miss in code review.
Ask Claude to audit your UI components for WCAG accessibility issues — it catches semantic problems, missing ARIA attributes, and keyboard navigation gaps that automated tools miss.
Claude Code checks credentials in a specific order. A stale ANTHROPIC_API_KEY in your shell can shadow your subscription login without any obvious error.
Every event emitted while processing a single prompt shares a prompt.id UUID, letting you trace the complete chain of API calls and tool executions.
Claude Code accepts images from any clipboard source — screenshots, Slack messages, browser windows, and design mockups all paste directly into your prompt.
The --debug flag enables verbose logging for Claude Code, and an optional category filter like "api,mcp" lets you narrow output to exactly the subsystem you need to investigate.
In iTerm2, paste clipboard images into Claude Code with Cmd+V — first capture a screenshot to your clipboard with Ctrl+Shift+Cmd+4 instead of the default Cmd+Shift+4.
Distributed tracing turns mysterious slowdowns into pinpointed bottlenecks. Ask Claude to wire up OpenTelemetry across your application without digging through the docs.
When an MCP server misbehaves, /mcp gives you a live view of every connected server, its status, and the tools it's exposing — right inside your session.
Printf debugging doesn't belong in production. Claude can wire up structured JSON logging with request context, log levels, and external service routing in minutes.
Share your server config or middleware code and ask Claude to identify missing or misconfigured security headers and provide drop-in fixes.
Paste your Rust compiler errors into Claude and get a clear explanation of the ownership issue plus a corrected version of your code.