Signal sources
Contents
Self-driving is in open beta. It's improving quickly – expect rough edges, and expect them to disappear fast.
Signal sources are what fill your inbox. A signal can be a production error, a support conversation, a Session Replay pattern, a log alert changing state, a Replay Vision scanner finding, or an issue from an external tracker. Each source watches one of these streams and turns what it finds into work worth investigating.
Configure sources
From the inbox, open settings and configure your sources. Toggle the ones you want to enable, then follow the authentication prompts for any external services. The inbox is available across surfaces – the web app, PostHog Desktop, and Slack – and your sources stay the same wherever you open it.
You don't need to configure MCP servers for inbox sources manually. Once your repository is connected, 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. Connect any of these via the data warehouse and the inbox surfaces actionable items for research.
Issue trackers
New issues from connected project management and issue tracking tools. The inbox starts a research task to find related code and decide whether a fix is possible.
- GitHub Issues
- Jira
- Linear
- GitLab
- Gitea
- Shortcut
- pganalyze
Support / helpdesk
Customer support tickets and conversations. The inbox turns actionable bug reports and feature requests into researched implementation work.
- Zendesk
- Freshdesk
- Freshservice
- Front
- Gorgias
- Kustomer
- Dixa
- Plain
Error tracking
Errors and exceptions from external error monitoring services. The inbox surfaces new errors and error patterns for investigation.
- Sentry
- Rollbar
- Bugsnag
- Honeybadger
- Raygun
Security scanners
Security vulnerabilities and findings from code scanning tools. The inbox prioritizes actionable security issues.
- Snyk
- SonarQube
- Semgrep
- Rapid7 InsightVM
Product feedback
Feature requests, ideas, and product feedback from feedback management platforms.
- Featurebase
- Frill
- Aha
- UserVoice
- Productboard
- Canny
- AskNicely
- Retently
Reviews
App store and product reviews. The inbox identifies actionable feedback from user reviews.
- Appfigures
- AppFollow
- Judge.me
What happens next
Related signals don't each become their own task. As signals arrive, the inbox deduplicates them and groups related ones, so a signal from a support conversation, a matching error-tracking issue, and a session-replay pattern collapse into a single report rather than three. That way you deal with one customer-facing problem, not scattered noise.
Once a report exists, research starts if the source is enabled. The research agent connects it to your codebase, checks user impact, and marks the report as Actionable when a code fix is possible.
From there, you can review the report, ask for more research, let an implementation agent open a pull request, or audit the agent log to see exactly what it read and why.
Next step
See how the inbox researches each report.