PostHog Code Inbox signal sources
Contents
Inbox uses signal sources to find work worth investigating. A signal can be a production error, a support conversation, a session replay pattern, or an issue from an external tracker.
Configure sources
- Open Inbox in PostHog Code.
- Click the Settings icon or open the Signal Sources tab.
- Toggle the sources you want to enable.
- Follow the authentication prompts for external services.
MCP is handled for you
You don't need to configure MCP servers for Inbox sources manually. Once your repository is connected in PostHog Code, research tasks can run automatically.
PostHog sources
These sources are available when the matching PostHog product has data in your project.
External sources
External sources pull issue context into the same Inbox queue as your product signals.
| Source | What Inbox reads | What Inbox does |
|---|---|---|
| GitHub Issues | New issues in connected repositories | Starts a research task to find related code and decide whether a fix is possible |
| Linear | Issue title, description, labels, and linked context | Searches the codebase and keeps the report tied to the original issue |
| Zendesk | Customer support ticket context | Turns actionable bug reports into researched implementation work |
What happens next
When a signal arrives, Inbox creates a report and starts research if the source is enabled. The research agent connects the signal to the codebase, checks user impact, and marks the report as Actionable when a code fix is possible.
From there, you can:
- Review the report in Inbox
- Ask for more research
- Let an implementation agent open a PR
- Audit the agent log to see exactly what it read and why
Learn more about research tasks and implementation tasks.