/inbox-exploration

name: inbox-exploration
description: >
  Explore PostHog's Inbox and act on what it surfaces — the place where signal reports cluster into
  actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?",
  "which reports are actionable?", "what's PostHog flagged recently?", asks about a specific report by
  ID or title, wants to act on / fix / implement a report (turn it into a PR), wants to resolve,
  dismiss, or snooze a report, or wants to see which signal sources are configured. Also use before you
  investigate an error, bug, metric change, or support ticket in code, to find research the Inbox already did.
  Covers listing, filtering, drilling into, and acting on reports, plus pointers to the deeper `signals` skill when raw signals
  or semantic search are needed. For a personal, ranked top N of reports, use `prioritizing-my-inbox`,
  which starts from the stored personal ranking (`view=for_you`, `sort=personal`).

Exploring the Inbox

The **Inbox** is where PostHog surfaces signal reports — clusters of related observations (signals) that have been aggregated into a single issue or trend (e.g. "Error rate spiked 3× on /checkout"). Reports come from multiple source products: error tracking, session replay, web analytics, experiments, and integrations like Linear, GitHub, and Zendesk.

Inbox is part of [PostHog Desktop](https://posthog.com/desktop), PostHog's agentic surface for engineering teams.

Don't assume the user's project has reports, or that any signal sources are configured — plenty of projects don't have Inbox set up. Always run the setup-check workflow below before answering the user's actual question.

Choose a workflow

Read only the reference for the task. Read it before you use its write tools.

| User request | Read before you proceed | | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | Check what needs attention | Use the setup check and triage workflow below. | | Investigate an error, bug, metric change, or support ticket | Use the research search below. Skip the setup check for this search. | | Read a report by ID or URL | Use the report detail workflow below. | | Fix a report or open a pull request | [Implementation and claims](references/implementation.md). Read before you claim or change code. | | Run Get it merged, Make it green, a suggested prompt, or Ask; file a report | [Report actions and filing](references/report-actions.md). Read before you start a run or file a report. | | Resolve, dismiss, snooze, or restore a report | [Report state](references/report-state.md). Read before any state change. | | Rank reports or use prediction filters | [Ranking](references/ranking.md). Read before you use model predictions. | | Review or change configured sources | [Sources](references/sources.md). Read before you change source settings. |

**"My inbox" means `view=for_you`.** Without a `view`, `inbox-reports-list` returns reports from the whole project, not only the user's. When the user says "my inbox", "my reports", or "what needs me", pass `view: "for_you"`. Use project scope only when the user asks for the whole project or the team's inbox.

When the user wants a personal shortlist ("let's look at my inbox", "my top 10 inbox reports", "what should I look at today?"), use the **`prioritizing-my-inbox`** skill. Its first call is `{"view": "for_you", "sort": "personal", "limit": 10}`, which returns the user's stored personal ranking in one read. Check that the response's `ranker` is `personal` before you call the list personal, and do not pass `ordering` with it, because `ordering` replaces `sort`.

For deeper investigation, hand off to other skills and tools:

• **`signals` skill** — query `document_embeddings` via HogQL for raw signal text, semantic

search across signals, or to inspect every signal that contributed to a report.

• **PostHog's product-specific MCP tools** — when a report points at a specific error, log line,

session, person, or time range, reach for the matching domain tool to pull richer context:

• Error tracking: `query-error-tracking-issues-list`, `query-error-tracking-issue`,

`query-error-tracking-issue-events` for error-tracking-sourced reports

• Logs: `query-logs`, `logs-count-ranges` to find log activity around the issue
• Session replays: `query-session-recordings-list`, `session-recording-get` to find

recordings of affected users

• Persons / activity: `persons-retrieve`, `advanced-activity-logs-list` to inspect a specific user's

behavior

• Trends / SQL: `query-trends`, `execute-sql` for ad-hoc verification queries

A signal report tells you _what_ PostHog clustered. The product-specific tools tell you the _underlying detail_ — pair them when the user wants to dig in.

Available tools

| Tool | Purpose | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | `inbox-reports-list` | Paginated list of reports with filters (statu