Inbox - Docs - PostHog

**Open beta** Self-driving is in open beta. It's improving quickly – expect rough edges, and expect them to disappear fast. The inbox is where self-driving hands work back to you. [Reports](https://posthog.com/docs/self-driving/reports) and the pull requests the loop opens both land here, ranked by priority, so the most important work rises to the top. It's the human side of the [self-improving loop](https://posthog.com/docs/self-driving/self-improving-loop): the loop watches, enriches, and proposes, and the inbox is where you review, steer, and decide. -   **Reports** – grouped [signals](https://posthog.com/docs/self-driving/signals) framed as one problem, with the evidence behind them.-   **Pull requests** – the changes an agent opens for actionable reports. Reports appear in one list that you filter by state and reviewer scope. Filter by `For you`, `Entire project`, or a teammate. Then choose the states to show, such as `Needs decision`, `Review and merge`, `Resolved`, or `Dismissed`. Reports are ordered by priority by default. To change the order, use the sort control and choose a different order, such as `Last updated first`, `Newest first`, or `Oldest first`. From the inbox you: -   **Review** a report and dig into the evidence.-   **[Ask AI](https://posthog.com/docs/self-driving/reports#ask-ai-about-a-report)** a question about a report, with its evidence already in context.-   **Steer** the work: approve it, snooze it, or decline what self-driving proposes.-   **Merge** the pull requests you're happy with, the same as any other PR. Nothing ships without you. The inbox is where you stay in control of what self-driving does. A resolved report stays resolved. If the same problem returns later, self-driving files a new report. It does not reopen the old one. Dismissed reports stay available in the `Dismissed` view, so you can review them or restore one. Triage is also how you teach the loop. When you dismiss or snooze a report and say why, that note is [forwarded to the scout that filed it](https://posthog.com/docs/self-driving/scouts#your-inbox-feedback-steers-scouts-too), so later runs read it before deciding what to surface. Explaining a bad report is the cheapest way to stop getting it. The inbox is available across surfaces – the [web app](https://posthog.com/docs/self-driving/web), [PostHog Desktop](https://posthog.com/docs/posthog-desktop/self-driving), and Slack – so you can review and act on work wherever you are. It's the same inbox everywhere; only the way you open it changes. When a report notification arrives in Slack, reply in that thread and mention `@PostHog` to continue the work on that report. PostHog links the task to the report, so the follow-up stays with the original finding instead of starting as unrelated work. See the [Slack app docs](https://posthog.com/docs/slack) for the other things you can do from a mention. Self-driving is one shared setup, not a separate one per surface. Your [signal sources](https://posthog.com/docs/self-driving/inbox/sources), [scouts](https://posthog.com/docs/self-driving/scouts), [reports](https://posthog.com/docs/self-driving/reports), and inbox state are the same whether you open PostHog Desktop or the web app – connect a source or tune a scout in one place and it takes effect everywhere. To start filling it, connect your [signal sources](https://posthog.com/docs/self-driving/inbox/sources). See what fills your inbox and how to connect it. [Signal sources](https://posthog.com/docs/self-driving/inbox/sources)