Use Error Tracking in PostHog Desktop
Contents
PostHog Desktop is in beta. This page is a work in progress.
PostHog Desktop is where you review and merge the Self-driving work that error tracking generates. When recurring exceptions are grouped into a report and a code fix is possible, Self-driving opens a draft pull request. You review it in PostHog Desktop, next to the agents improving your product, and nothing ships until you merge.
Before you start
- Set up Error Tracking – install exception capture in your app so exceptions reach PostHog.
- Install PostHog Desktop – download the app and connect it to your project.
Start at the inbox
Reports don't come looking for you – they queue up in the Self-driving inbox, so checking it is the habit that makes this surface worth anything. The inbox holds everything Self-driving has found across every source, error tracking included, with the highest-priority reports first. Open one to see the issue behind it, the evidence, and any pull request it opened.
What you can do here
- Review Self-driving reports built from recurring issues, with the related stack traces, session replays, and events attached.
- Inspect and edit the draft pull request that fixes an issue before merging.
- Hand issues off to an agent to investigate or draft a fix.
Related
- Debug over PostHog MCP – pull issues and stack traces into any MCP client or AI agent.
- How Self-driving works – the full report-to-merge loop.