Shift your product into self-driving mode

You have a new pull request ready for review. (Yep, really.)

While you slept, PostHog dug through your product data, found what was worth fixing, and had agents do the work. All you need to do is hit merge.

Learn about InboxNew to PostHog? Sign up

Unlimited reports. Priced by pull request. 3 free each month.

How a product improves itself

…then it loops

Every change ships with the instrumentation to measure it – the agent adds the events, feature flags, and experiments as it goes. After it merges, PostHog checks whether the metric actually moved. If it didn't, that's a new signal (and the change can be rolled back).

SignalResearchReportPRShipMeasureThe self-improving loop
A hedgehog transforming into a self-driving machine

PostHog agents run on their own, but don't run wild

Self-driving is autonomy from instruction, not from you. Agents work in the background without you prompting them to make progress, but nothing ships on autopilot.

  • It's stuck in a sandbox. Work happens in the cloud, nowhere near your repo. Agents follow your branch protections, CI, and review rules.
  • The work can't merge itself. Nothing reaches production until a human clicks merge. Robots don't touch the big green button.
  • PRs > Issues. Raw signals are deduped and clustered into reports. Actionable ones become PRs. You only pay for real work completed.
  • Your secrets are safe. Literally, and so is your code. Private repos stay private, and so does your data. (We're training AI models, but not on your code.)

Merged into PostHog by self-driving

See them all →
fixexports

retry transient browserless render drops in-process

merged#709892949w ago
fixexports

stop re-raising user-config export errors

merged#709882949w ago
fixsignals

attach inbox infinite-scroll observer via callback ref

merged#664782949w ago
fixoauth

degrade gracefully when loading teams fails on /authorize

merged#665202949w ago
fixweb-analytics

swallow transient fetch failures in presets loader

merged#665402949w ago
fixmigrations

retry clickhouse migration step on startup races

merged#665682949w ago
fixhogql

guard resolver against unbounded recursion

merged#709822949w ago
fixinsights

warn when dashboard filters are dropped on SQL insights

merged#688682949w ago
fixtoolbar

drop self-inflicted posthog-js telemetry timeout errors

merged#689892949w ago
featsurveys

surface $current_url in survey notification editor

merged#691622949w ago
fixactivity-log

guard side panel loader against 403 for denied users

merged#642022949w ago
fixintegrations

handle no-org 404 in organization integrations loader

merged#650602949w ago
fixexports

retry transient browserless render drops in-process

merged#709892949w ago
fixexports

stop re-raising user-config export errors

merged#709882949w ago
fixsignals

attach inbox infinite-scroll observer via callback ref

merged#664782949w ago
fixoauth

degrade gracefully when loading teams fails on /authorize

merged#665202949w ago
fixweb-analytics

swallow transient fetch failures in presets loader

merged#665402949w ago
fixmigrations

retry clickhouse migration step on startup races

merged#665682949w ago
fixhogql

guard resolver against unbounded recursion

merged#709822949w ago
fixinsights

warn when dashboard filters are dropped on SQL insights

merged#688682949w ago
fixtoolbar

drop self-inflicted posthog-js telemetry timeout errors

merged#689892949w ago
featsurveys

surface $current_url in survey notification editor

merged#691622949w ago
fixactivity-log

guard side panel loader against 403 for denied users

merged#642022949w ago
fixintegrations

handle no-org 404 in organization integrations loader

merged#650602949w ago
fixtoolbar

stop finder unique() throwing on 0-match candidates

merged#641662949w ago
fixerror-tracking

keep breakdown filters logic mounted for issue scene

merged#665352949w ago
fixerror-tracking

keep breakdownFiltersLogic mounted at scene root

merged#665472949w ago
fixweb_analytics

allow query strings in saved heatmap URLs

merged#687622949w ago
fixquery

keep events feed stable when ClickHouse errors break a reload

merged#687532949w ago
fixsession-replay

swallow team-scoped 404/403 in playlist popover

merged#687712949w ago
fixreplay

stop playlist reload and scroll reset on recording select

merged#687882949w ago
featsettings

guide users to the right internal-user filter property

merged#685172949w ago
fixdata-warehouse

soften DAG-managed sync frequency rejection

merged#691272949w ago
fixpersons

degrade person preview gracefully on list API error

merged#687932949w ago
fixfrontend

self-heal on stale-bundle ESM binding mismatch after deploy

merged#685032949w ago
fixreplay-vision

guard selector reads after unmount in vision logics

merged#687432949w ago
fixtoolbar

stop finder unique() throwing on 0-match candidates

merged#641662949w ago
fixerror-tracking

keep breakdown filters logic mounted for issue scene

merged#665352949w ago
fixerror-tracking

keep breakdownFiltersLogic mounted at scene root

merged#665472949w ago
fixweb_analytics

allow query strings in saved heatmap URLs

merged#687622949w ago
fixquery

keep events feed stable when ClickHouse errors break a reload

merged#687532949w ago
fixsession-replay

swallow team-scoped 404/403 in playlist popover

merged#687712949w ago
fixreplay

stop playlist reload and scroll reset on recording select

merged#687882949w ago
featsettings

guide users to the right internal-user filter property

merged#685172949w ago
fixdata-warehouse

soften DAG-managed sync frequency rejection

merged#691272949w ago
fixpersons

degrade person preview gracefully on list API error

merged#687932949w ago
fixfrontend

self-heal on stale-bundle ESM binding mismatch after deploy

merged#685032949w ago
fixreplay-vision

guard selector reads after unmount in vision logics

merged#687432949w ago

It runs on the data you already have

Your product is a context goldmine. Self-driving puts that data to work. The more sources PostHog can see, the sharper the fixes get.

Signals
In-app activity
Logs
Errors
Payments
Session recordings
Traces
Funnel dropoff
Feature flags
Experiment results
Internal threads
Support tickets
Backlog
Transcriptions

Works in your workflow

The same Inbox and agents show up across five surfaces (everywhere you go, there's PostHog).

PostHog web app

The full product in your browser. Explore your data, review proposed work, and dig into the evidence.

Sign up free

PostHog Slack app

@PostHog brings PostHog into Slack channels. Route reports to the ones each team already watches (hedgehog mode not included).

Add to Slack

PostHog MCP

Look ma, no hands! Pull self-driving context into other tools, and pull context from your other tools into self-driving.

Hook it up

PostHog CLI

Self-driving from your terminal. Query your data and drive agents right where you already work, and wire it into your scripts and CI.

Read the docs

PostHog CodeBeta

A desktop app for driving parallel agents to edit your product. The same Inbox and reports live here.

Get the app

Steering a self-driving report from a Slack thread

Build in public (with the whole team)

Self-driving isn't only autonomous. Some fixes are better hashed out by three people in a thread.

Solve it together

Work through a report or PR with collaborators in Slack. Add context, steer the agent, and decide what ships.

Sorted by priority

Each report arrives tagged P0–P4 by impact, so the channel sees what needs attention now and what can wait.

A P0 self-driving report delivered to a Slack channel
A P1 · Replay self-driving report delivered to a Slack channel
A P1 · Zendesk self-driving report delivered to a Slack channel
A P2 self-driving report delivered to a Slack channel
A P3 self-driving report delivered to a Slack channel
A P4 self-driving report delivered to a Slack channel
A P0 self-driving report delivered to a Slack channel
A P1 · Replay self-driving report delivered to a Slack channel
A P1 · Zendesk self-driving report delivered to a Slack channel
A P2 self-driving report delivered to a Slack channel
A P3 self-driving report delivered to a Slack channel
A P4 self-driving report delivered to a Slack channel
A P0 self-driving report delivered to a Slack channel
A P1 · Replay self-driving report delivered to a Slack channel
A P1 · Zendesk self-driving report delivered to a Slack channel
A P2 self-driving report delivered to a Slack channel
A P3 self-driving report delivered to a Slack channel
A P4 self-driving report delivered to a Slack channel

Suspiciously chill for how much it's doing

building with AIbuilding with AI
Prompted

It builds what you spec

This is what you're used to (you set the spec and the agents do the work). Prompt a task from PostHog AI, PostHog Code, or the Slack app, and agents build it.

Full product context Understands your users, not just the diff it's editing.

Reactive

It acts on your data

This is what the Inbox is for. It watches the data you already have in PostHog and turns anything worth acting on into a researched report, often with a fix attached.

Always on Reads logs and tickets for fun. Sick, honestly.

Proactive

It looks for work

This is where it gets good. Scouts dig through your data and flag problems you haven't thought about (yet). Your product improves everywhere, every day.

Remembers everything Including that. Especially, that.

So, what's left for you?

Work lands while you sleep. You wake up to diffs and reports waiting for review. Then what?

You're (still) the driver

Like a Waymo, a self-driving product doesn't decide where you're going (it just makes getting there easier). You choose where the product goes next.

A hedgehog gesturing toward the work

Skip to the good part

Somebody's gotta clean up around here. Turns out it doesn't have to be you. Bug fixes and maintenance work land in your inbox. Hit merge and move on with your day.

A hedgehog eating popcorn

Outship everyone

Product capability used to scale with headcount. Now it's handled (without adding any). A small team with self-driving can outship companies 10x the size.

A hedgehog working at a laptop

Set up your InboxBeta

Install PostHog, then run the wizard – it turns on your signal sources, connects GitHub, and sets up your scouts. Your first reports start landing in ~20–30 minutes.

Learn more

New to all this? Read the self-driving docs.

FAQ

Community questions

Questions about this page? or post a community question.