# Getting started with PostHog Code Inbox - Docs

## Connect your signal sources

Inbox identifies work by monitoring *product signals* from various sources, both internal to PostHog and external ones. To get started, you need to connect the sources:

![The PostHog Code Inbox with researched and actionable reports](https://res.cloudinary.com/dmukukwp6/image/upload/c_crop,x_112,y_75,w_iw_sub_224,h_ih_sub_222/Screenshot_2026_05_04_at_4_48_19_PM_9652a9fb7c.png)

-   **Internal:** PostHog [Error Tracking](/docs/error-tracking.md) issues, [Support](/docs/support.md) tickets, and [Session Replay](/docs/session-replay.md) recordings.
-   **External:** GitHub issues, Linear issues, or Zendesk tickets.

In PostHog Code, open **Inbox** and use the **Configure sources** button above the search box.

[Learn about signal sources](/docs/posthog-code/inbox/sources.md)

## Wait for signals to be researched

Once sources are connected, Inbox researches new information as it arrives. The agent uses the MCP servers in your workspace, starting with the PostHog MCP, to figure out what's happening and how big the impact is.

The agents have access to your product's code for grounding. The result of research is a ready report, rated with:

-   **Actionability:** Marked as "Actionable" if the problem can be solved with code.
-   **Priority (P0-P4):** Determined by the impact on user flow, number of users, and code importance.

You can audit the research agent's logs to see exactly how it navigated your repo and reached its conclusions.

### Waiting for reports to appear?

Background research can take up to fifteen minutes due to its depth. If you've just connected a source, there are two scenarios:

1.  The source already has data to ingest, for example if you connect Error Tracking and you already have error issues in PostHog. It might take a minute or two for these records to appear queued for research in Inbox.
2.  The source is empty, for example you connect Error Tracking in a blank project. Just stay tuned for bugs to be tracked then! We'll let you know in the Inbox when there are user issues to resolve.

[Learn about research tasks](/docs/posthog-code/inbox/research.md)

## Merge your first PR

When research is complete and the issue can be simply actioned with code, the agent executes an **implementation agent**: cloning your repo, implementing the fix, creating a branch, and opening a GitHub PR.

Each PR includes an AI-generated description of the problem and the change. Your job is simply to review the code in GitHub and click **Merge**. Any comments on the result? You can chat with the implementation agent directly in PostHog Code, and it'll make tweaks you ask for.

[Learn about implementation tasks](/docs/posthog-code/inbox/implementation.md#implementation-tasks)

1/3

[**Connect your signal sources** ***Required***](#quest-item-connect-your-signal-sources)[**Wait for signals to be researched** ***Required***](#quest-item-wait-for-signals-to-be-researched)[**Merge your first PR** ***The Goal***](#quest-item-merge-your-first-pr)

**Connect your signal sources**

***Required***

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better