> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Self-driving – Error Tracking pocket guide

Canonical URL: https://posthog.com/learn/error-tracking/pocket-guide/self-driving

Chapter 07

# Self-driving – Error Tracking pocket guide

Now that Twig's engineers see reliable, high-quality exceptions flow into Error Tracking, they're ready to take the next step to let PostHog self-drive fixes.

Twig's engineers turn on a troop of [scouts](https://posthog.com/docs/self-driving/scouts.md). Scouts are agents that run on a schedule to look for specific issues. They stay silent unless they find something to act on.

They will automatically look for issues, assess their impact, create a [report](https://posthog.com/docs/self-driving/reports.md) with the impact and the fix, and even open pull requests to help the engineers resolve them.

This chapter covers these examples of how Twig self-drives with Error Tracking:

-   [Catch error spikes and stuck loops](https://posthog.com/learn/error-tracking/pocket-guide/spikes-and-stuck-loops.md) ranks spikes by how many guests they affect.
-   [Find the errors Twig's paying hosts hit](https://posthog.com/learn/error-tracking/pocket-guide/errors-in-paying-hosts.md) reports issues concentrated in hosts who pay.
-   [Connect a deploy to an error burst](https://posthog.com/learn/error-tracking/pocket-guide/deploy-regressions.md) ties a new issue to the pull request that likely caused it.
-   [Check whether the fix held](https://posthog.com/learn/error-tracking/pocket-guide/verify-the-fix.md) reports fixes that didn't stop the error.

[Start reading →](https://posthog.com/learn/error-tracking/pocket-guide/spikes-and-stuck-loops.md)