Blog
Practical notes on production debugging, SDKs, product analytics, and the decisions behind DebugBundle.
Check release mismatches, environment assumptions and regression coverage before accepting an AI coding agent's fix for a production failure.
By Owen Far
Create a public status page from DebugBundle health checks. Share website and API uptime, combine projects, and keep sensitive diagnostics private.
By Owen Far
Analyze signup drop-off and cross-domain user flows with Codex, Claude Code, Cursor, or Gemini CLI using DebugBundle's acquisition and activation reports.
By Owen Far
Connect Gemini CLI to DebugBundle's MCP server and Agent Skill to investigate incidents, inspect debug bundles, and turn production errors into tested fixes.
By Owen Far
See how DebugBundle redacts secrets before transport, protects stored evidence at retrieval, and gives AI agents bounded incident access instead of raw logs.
By Owen Far
Use Codex to investigate production errors with captured requests, logs, and release context. A practical DebugBundle workflow from incident to tested fix.
By Owen Far
See how AI agents use product analytics, funnels, journeys, opportunities, and incident impact to turn usage evidence into focused product work.
By Owen Far
Learn how aggregate metrics, consent controls, redacted journeys, and friction signals reveal product problems without video session replay.
By Owen Far
How to design health check endpoints, readiness checks, and hosted availability checks that catch downtime without creating noisy incidents.
By Owen Far
How capture policy, diagnostic probes, redaction, and volume controls keep production debugging bundles useful without becoming unsafe telemetry dumps.
By Owen Far
