debugging

This article discusses a method for debugging AI agents by identifying which specific layer in the agent's architecture produced an incorrect answer, rather than immediately tweaking the prompt.

A tool to detect discrepancies between an AI agent's claimed actions and its actual behavior.

A new open-source skill forces AI coding assistants to debug production bugs by isolating the exact historical commit using git worktree, leaving the local workspace untouched.

The author investigates why segmentation faults are not displayed when using entr to run a C program, discovering that bash's exec optimization suppresses the error message unless the command is run in a subshell or script.

The article argues against over-integrating AI agents with many tools prematurely, advocating instead for narrow, deeply integrated connections (e.g., inbox and calendar) that use live context and are auditable, as broad integrations often fail in production.

Phoenix has a built-in Pixie assistant that helps users quickly filter out silent failure traces where agent spans have errors but model responses are normal, greatly improving trace reading efficiency.

A detailed blog post from the Guix HPC team describing how they identified and debugged a performance regression in the MPI stack on Slingshot interconnects, showcasing Guix's transparency and control.

A developer discovers that swapping two equivalent macros caused unexpected integer changes in unrelated functions, and the blog post investigates the mystery, questioning an LLM's explanation about control flow guard.

BugShot is a tool that helps developers discover, fix, capture, and report bugs in a single step.

The article explains how the readonly property `scrollHeight` can cause performance issues by triggering synchronous layout updates in Chromium, and suggests using a large number instead of recalculating scrollHeight frequently.

LangChain released a plugin that logs all Claude Code sessions into LangSmith for debugging, with a quick three-command setup.

Explains why a #pragma detect_mismatch error persists after fixing the mismatch and rebuilding the project—because the mismatched object file is in an external library that needs to be recompiled as well.

A deep dive into Go's profiling mechanism, explaining how the runtime collects CPU, heap, block, mutex, and goroutine profiles, and how they are represented in the pprof format.

This article describes a debugging journey where a Rust service's memory remained high under load despite no leaks, due to glibc's ptmalloc allocator not releasing freed memory back to the OS. It explains the allocator behavior and provides insights for Rust developers.

The article discusses common causes of cost spikes in AI workflows, such as retries, repeated tool calls, long-running workflows, and growing context, and asks how teams investigate such issues.

This article explains how to implement logging to the console in Game Boy Advance development using mGBA's custom memory-mapped registers, allowing printf-style debugging via the emulator's log window or terminal.

A practical account of the key failures encountered when building an autonomous agent that actually operates in production, along with solutions for each.

chrome-devtools-mcp is an MCP server that enables coding agents to directly connect to Chrome DevTools for page inspection, log capture, and network request analysis, reducing back-and-forth communication for manual review by developers.

Mcpsnoop is an open-source transparent proxy with a live terminal UI that sits between AI clients and MCP servers, showing real-time JSON-RPC traffic for debugging tool calls, capabilities, and performance without setup.

TraceSage is a new MIT-licensed, local-first observability tool for LangChain and LangGraph that runs entirely on your machine, providing live topology graphs, step-by-step replay, token tracking, and OpenTelemetry export without sending data to the cloud.