Pineapple on pizza

No data available

Members

Goals

Q2 2026

For reference (internal-only): Q2 planning doc

Going as far as it takes to make users feel Inbox is not just "cool" - but awesome.

Principles:

  • We eat our own dog food - PostHog Inc. has to be a set of happy Inbox users, and we have a path to that
  • Reliabiltity is non-optional - explicitly allocating time to reliability, including devex

Ownership will be assigned as we prioritize throughout the quarter. Michael makes sure this happens as team lead.

Objective 1: One PR merged a day

Self-driving has to deliver concrete code to review and merge:

  • Auto-create PRs
  • Allow users to configure the level of confidence for PR creation
  • Make PostHog Code Inbox UX spark joy
  • Run user interviews
    • Annika will be running interviews with active PH Code users, we should take part

Objective 2: Prioritization

Serving "One PR merged a day": Prioritization in the inbox has to always surface slam dunks above noise:

  • Making the agent run queries to determine if the problem is in a hot path
  • "Analyze part of session visually" tool for research
  • Seamless PostHog org member→GH user mapping (for owner assignment)
  • Ability to reingest all signals in prod
    • Plus ability fo filter by pipeline version

Objective 3: Sources

Specific sources have to result in salient inbox items:

  • PostHog Error Tracking
  • Linear
  • GitHub Issues
  • Zendesk
  • PostHog Support
  • Later in the quarter: Session Replay (much higher-effort w/ Replay team collab)
    • Michael to write a spec for the person who'll help us ship here

Other teams integrating: on pause until we have confidence in these core sources.

Objective 4: Experiments

We're in delivery mode with PostHog Code launch, but when we have solid footing there, we should get back into some experimentation. We think we have some ideas that may take the product to the next level, but they need to be actually tested:

  • AI PM: Agent as the "product owner" on a product/feature level: On a cron, the agent checks the feature status (metrics, errors etc.) & recommends actions
  • Memory
  • Allow agent to schedule follow-up (esp. for LLMA + replay)

Non-objective: Pricing

Pricing is not a priority before we feel that the Inbox is indeed awesome. We should just keep track of costs to keep an eye:

  • Set up Inbox usage/success/costs dashboard

Handbook

We're building the product to proactively analyze your data in PostHog.

Data (Session Replay, Product Analytics, Error Tracking, AI Observability etc.) → signals → signal groups → tasks.

Questions about this page? or post a community question.