Skip to content

Sprint - September 21 to October 2 #101363

New issue
New issue
Closed
Closed
Sprint - September 21 to October 2#101363
Labels
sprintSprint planning

Description

@turnipdabeets
turnipdabeets
opened on Sep 16, 2026

Sprint Planning

List of incidents + any action items that haven't been scheduled yet

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

# Team ___

**Support hero:** ___
**Off during the sprint:** ___

## Quarter goals

1. Quarter goals, status (red/yellow/green) and action points if yellow/red

## Retro

### Tasks

<!-- Grab the high and low priority items from last time and add whether that item was completed or not -->

## Plan

### High priority

-

### Low priority / side quests

-

### Are any other teams impacted by this plan? If so, tag them here

-

Activity

  1. turnipdabeets
    added
    sprintSprint planning
    on Sep 16, 2026

  2. turnipdabeets commented on Sep 16, 2026

    @turnipdabeets
    turnipdabeets
    on Sep 16, 2026
    ContributorAuthor

    Team Client Libraries

    Support hero: @turnipdabeets then @dustinbyrne
    Next sprint planning @ioannisj
    OOO: Manoel 1 day (TBC) Ioannis 1 day (Oct 1st)

    Quarter goals

    Q3 2026 objectives

    • 🟡 Goal 1: SDK harness and specs (@dustinbyrne)
      • 🟢 Expand the SDK harness coverage across SDKs
      • 🟢 Define clear specs for shared SDK behavior (incl. SDK parity table)
      • 🟡 Use the harness in CI so SDK changes stay on contract
      • 🟡 Make it easier for contributors and employees to validate changes before release
      • 🔴 Publish shared SDK skills customers can install, using the SDK specs as source of truth
        • worst results
      • 🟢 Explore spec-driven "software factory" workflow for agent-assisted updates across SDKs
      • 🟢 Experiment with a GitHub Action that triages issues and opens PRs for straightforward fixes
    • 🟢 Goal 2: Mobile push notifications (@ioannisj)
      • 🟢 Android and iOS support
      • 🟢 Flutter and React Native support by reusing the native SDK implementations
    • 🟡 Goal 3: SDK coverage and modernization (@marandaneto)
      • 🟢 KMP SDK
      • ⚪ Flutter desktop SDK
        • a customer wanted to contribute/donate here
      • 🔴 Session replay for macOS
        • technically not feasible with screenshots
      • 🟢 React Native Expo Router touch events
      • 🟢 Flutter SDK init bootstrapping for feature flags
      • ⚪ Framework-level SDK experiences and docs native to customers' frameworks
      • 🟢 CocoaPods sunset migration plan
      • ⚪ iOS SDK next major version
      • 🟢 Async version of the Python SDK
      • 🟡 JS SDK v2, including the versioned script loader
      • 🟡 Port the new ingestion endpoint across SDKs using the Rust SDK as an example
        • 🟡 Rust SDK v1 GA
      • 🟢 Triage and fix real and stale issues across SDKs during Support Hero rotation
    • 🟡 Goal 4: Tracing support (@turnipdabeets)
      • 🟢 Define the SDK tracing approach for first-class JS Python support
      • 🟡 Add tracing support to the JS and Python SDKs
      • 🟢 Align tracing behavior with PostHog ingestion and analysis workflows
      • 🟡 Document how customers should configure and use tracing from PostHog SDKs
    • 🟡 Goal 5: SDK observability research (@ioannisj)
      • 🟡 Whether we can safely instrument SDK behavior affecting reliability and customer experience
      • ⚪ Visibility into SDK errors, delivery failures, and performance issues
      • 🟡 How SDK observability could improve support and debugging workflows
      • 🟡 How feasible learnings feed back into SDK quality, release, and support processes

    Retro

    Details

    High priority

    • 🟢 expand SDK harness implementations to missing SDKs @dustinbyrne
      • expanded support for ruby/php/.NET/elixir, a few drafts/accepted PRs held off on to focus on the harness v2 work below
    • 🟢 experiment with expanding SDK harness to include sdk-specs acceptance tests @dustinbyrne
      • clear path forward for migrating the existing harness to gherkin: test every behavior, make more use of the OpenSpec scenarios in sdk-specs, rework test annotation/selection (today mobile targets server tests because there's no easy way to select just the transport format). Targeting node for a first release
    • 🟡 SDK observability @marandaneto @ioannisj
      • review/approve and merge RFC
      • get a draft SDK PR with PoC
      • check with ingestion/billing about those events
    • 🟡 Add tracing support to the JS SDKs @turnipdabeets
      • 🟢 posthog-node manual tracing
      • 🟡 posthog-python manual tracing
    • 🔴 iOS SDK next major version @ioannisj
    • 🟡 Adding $recording_status to all sdks that have session replay @ioannisj

    Low priority / side quests

    • 🟢 @posthog/browser core bundle byte size elimination @dustinbyrne
    • 🔴 @posthog/browser runs shared extensions @dustinbyrne
      • good progress on core/analytics refactoring on the side; extension loading in progress (flags/logs/surveys/autocapture to follow)
    • 🟢 modernize JS monorepo stack @marandaneto
      • CI is slow, lots of jobs, we need faster tooling and improve CI time
    • 🟢 $push_notification_opened Flutter sent on code and warm starts @turnipdabeets
      • iOS (missing cold)
      • Android (missing cold and warm)
      • React Native: Android warm start, iOS cold launch, Android killed process
    • 🟢 Godot experimental SDK @marandaneto
    • 🟢 rrweb perf improvements @marandaneto
    • 🟢 disable touch recording for all mobile SDKs @marandaneto
    • 🟢 PostHogUnmaskWidget flutter support @marandaneto
    • 🟢 Custom paint masking flutter support @marandaneto
    • 🟢 identify traffic from in-app browsers web $webview_ props @marandaneto
    • 🟢 React native Expo OTA metadata and app state for exceptions $expo_ props @marandaneto
    • 🟢 React native resetError support @marandaneto
    • 🟢 Respect retry after headers for retryable requests web @marandaneto
    • 🟢 Distinguish MCP and AI events thru library metadata for ai, node, and python with eg $ai_ props @marandaneto
    • 🟢 Android and iOS perf improvements for session replay re encoding @marandaneto
    • 🟢 Local feature eval SDK test harness @marandaneto

    Plan

    High priority

    Low priority / side quests

    Are any other teams impacted by this plan? If so, tag them here

    • @PostHog/team-ingestion with the capture AI v1 endpoint

    🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started

  3. turnipdabeets
    pinned this issue on Sep 16, 2026

  4. langesven commented on Sep 16, 2026

    @langesven
    langesven
    on Sep 16, 2026
    Contributor

    Team Cloud Platform

    Quarter Goals

    Retro

    Details

    High Prio

    • 🟡 Burrow PoC - Dedicated dev infra @k33lan
    • ✅ Investigations Trial - Support/Optimise/Document @k33lan
    • 🟡 Deployments - explore analysis templates more and test with our synthetic service @Z3r0Sum
    • 🟡 Deployments - migrations to our new system @Z3r0Sum
    • ✅ HostHog - get postgres db integration working @langesven
    • ✅ HostHog - establish proper path for agentic access to e.g. hosted APIs/MCPs @langesven

    Low Prio

    • ⚪ Run Vmgather to get diagnostics for VM support @k33lan
    • 🟡 Refactor Q3 ‘Agentify’ issue tracker @k33lan
    • ✅ Deployments - Deployment Events Milestone 2 - incident io integration @Z3r0Sum
    • 🟡 Get more out of pganalyze, easier setup, feed it more data, etc @langesven

    Side Quests

    • 🟡 Rollout docker terraform provider for docker hub admin @k33lan
    • 🟡 Rollout docker hub OIDC for image pushes instead of tokens @k33lan
    • 🟡 Deployments - OSS contributions upstream: @Z3r0Sum -> issue deliberation around implementation details for the UI changes. I through up both a backend/frontend set of PRs that contained the prototype.
    • 🟡 Upgrade Argo CD and Kargo (will do kargo) @Z3r0Sum
    • 🟡 Downgrade more DB users @langesven
    • 🟡 Reduce crazy pgbouncer costs @langesven

    ✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

    Plan

    High Prio

    • HostHog - Finish OAuth story for authenticated logins from "outside" @langesven
    • HostHog - Improve docs around Postgres usage, find a first candidate for migration @langesven
    • Burrow - E2E test suite on new burrow-dev infra @k33lan
    • Sherlock/@.PostHog @k33lan
      • Address triage quality gap between the 2 agents
      • Support for freezing deployments (inc-1023)
    • Incident.io investigations post-trial feedback/analysis @k33lan
    • Deployments - testing/bug fixing around analysis templates work @Z3r0Sum
    • Deployments - implement easy/golden path for helm charts that wrap infra we have (non-posthog app) @Z3r0Sum
    • Deployments - more migrations @Z3r0Sum

    Low Prio

    • HostHog - Explore "promote to prod" path w/ posthog-app onboarding @langesven
    • Rollout docker terraform provider for docker hub admin @k33lan
    • Rollout docker hub OIDC for image pushes instead of tokens @k33lan
    • Deployments - enable / get working some of the instrumentation for services like kargo-mcp / deployment-events @Z3r0Sum

    side quest

    • Continue pgbouncer consolidation/cross-az traffic reduction @langesven
    • Continue to try and get upstream traction around UX changes we want into Kargo @Z3r0Sum
    • Argo CD - we still can't upgrade because of a bug related to manifest paths, so look into options - contribute fix, workaround, etc. @Z3r0Sum
    • Cloud Platform Times! @k33lan

  5. MichaelKutsch-ph commented on Sep 16, 2026

    @MichaelKutsch-ph
    MichaelKutsch-ph
    on Sep 16, 2026
    Contributor

    Team Cloud Foundations

    Quarter Goals

    Retro

    Details

    High Prio

    • 🟡 Vendor negotations @MichaelKutsch-ph @sinthetix
    • networking:
    • 🟡 CDP and temporal-workers-* egress @MichaelKutsch-ph
    • 🟡 NLB + EIP: check DNS setup for potential migration and a plan @MichaelKutsch-ph - seems like we might be looking for a new ingress as contour is almost in maintenance mode with only two contributors left -> propsing as quarterly goal
    • review EC2 spend and projections to account for optimizations @sinthetix @MichaelKutsch-ph
    • ⚪ rollout EKS intelligence to prod clusters @MichaelKutsch-ph there was a blocker on DoIt's side, which is now resolved - can go on with prod the next few days
    • 🟡 vendors in PostHog data warehouse @sinthetix
    • 🟡 cost granularity improvements @sinthetix
    • 🟡 legacy managed reverse proxy - communication for moving customers off @danielxnj

    Low Prio

    side quest

    • upgrade EKS to 1.36 on dev and then take it to prod @danielxnj

    ✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

    Plan

    High Prio

    Low Prio

    side quest

  6. tomasfarias commented on Sep 16, 2026

    @tomasfarias
    tomasfarias
    on Sep 16, 2026
    Contributor

    Team Batch Exports

    Support hero: @tomasfarias / @rossgray

    Quarter goals

    • Objective 1: Make HogQL-backed data exportable
    • Objective 2: Agent-driven batch exports
    • Objective 3: The pipeline must grow

    Retro

    Details

    High priority

    • HogQL batch exports
      ✅ Internal testing required: Let's run a bunch of these.
      ✅ Roughly in the millions of rows.
      • Some more testing for stress cases is required.
        🔴 Load testing: Can we hook into any existing exports?
        🔴 Power SQL editor downloads with batch exports.
      • Started planning this, we'll likely tackle it in the future
        🟡 Support for query placeholders.
        🟡 Main blocker: Version key, merge key, data interval.
      • Data interval we'll probably get it done.
        • This already enables all batch exports just without merges.
      • Version key / merge key we'll tackle afterwards
        ✅ HogQL modifiers
      • We are now using Team modifiers everywhere.
      • Keeping an eye out on support queue

    ⚪ Deprecation of $set/$set_once
    ⚪ Do a quick test on dev to make sure everything works (it should!)!

    • Got pushed back, we should still test this.

    • Integration clean up
      🔴 Redshift: migrate and clean up.
      🔴 PostgreSQL: clean up.
      🟡 Snowflake: clean up.
      ✅ S3: clean up.

    Low priority

    🔴 Improve SLA alerts
    🔴 Too noisy when continuous runs keep going over

    ⚪ UX/UI for hogql batch exports

    • We can work on this during the closed beta, so moved to low-priority
    • File download batch exports in the Exports view
    • Combine file download export and SQL editor download (check with team-data-tools)
      • File download batch exports are billed differently from SQL editor downloads
      • This may be a surprise for users, we need to think how to communicate.
    • Scheduled batch exports link to SQL editor for query (or saved mat view)

    ⚪ Make integrations easier to use for agents

    • Redirect to integration page when creating a batch export with an agent.

    ⚪ Resource based allocator + auto-scaler for batch export workers

    ✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

    High priority

    • Resource based allocator + auto-scaler for batch export workers

      • We may need separate workers for memory-heavy activities.
        • 2 queues: "Internal" (low-memory) queue, and "External" (high-memory) queue.
      • This is to allow tuner to more accurately gauge memory usage.
      • Initially, just start using the tuner. Then see if we need this for improved accuracy.

    • HogQL batch exports

      • If we have willing customers, we can start them on a closed beta
      • Define version key and merge key, so we can do mutable batch exports.
      • Support for different modes (only for warehouse destinations):
        • APPEND
        • FULL_REFRESH
        • MERGE (requires both key fields)
      • We may need to distinguish warehouse vs object storage destinations.

    • Deprecation of $set/$set_once

      • Do a quick test on dev to make sure everything works (it should!)!
      • Got pushed back, we should still test this.

    Low priority

    • Cost management

      • What's costing us more? Egress, workers, temporal, etc...?
      • Are there opportunities to optimize our costs?

    • Batch exports powers SQL editor

      • Decide billing (need RFC)
      • Ideally, keep this separate from the other work (different feature flag, A/B test)
      • Support more file formats

    • Improve SLA alerts

      • Too noisy when continuous runs keep going over
      • We should look into switching to event based alerts, rather than log lines

    • Integration clean up

      • Redshift: migrate and clean up.
      • PostgreSQL: clean up.
      • Snowflake: clean up.

  7. mariusandra commented on Sep 16, 2026

    @mariusandra
    mariusandra
    on Sep 16, 2026
    Collaborator

    Team Data Tools

    Last sprint of the season! Time to wrap this up.

    Off during the sprint: Sinan 1st week

    Quarter goals

    1. Make notebooks the default way to analyze data (Sinan)
      🟢 Polished markdown-first notebook UX
      🟢 Better integration with HogQL, DuckDB, external DBs, and visualizations
      🟢 AI agents can create/edit notebooks directly (great MCP support)
      🟡 Python notebooks for customers
      ⚪ Publicly shareable notebooks

    2. Define and level up HogQL as a query engine (George)
      🟢 First optimization passes using the improved type system
      🟢 Typed pre-execution errors
      🟢 Dry-run and cost estimation for agents
      🟡 Improved HogQL / query observability
      ⚪ HogQL roadmap with owners and milestones (rust wen?)

    3. Make BI, SQL, and visualizations feel mature and reusable (Marius)
      🟢 Improved charting / visualization UX
      🟢 Support more databases as first-class citizens (MySQL, Snowflake, BigQuery, etc)
      🟢 SQL editor papercut cleanup
      🟡 Work with Desktop to standardize PostHog visualization components
      🟡 Variables: multiselect, query-backed, and time-based variables
      ⚪ Row drilldown from query results (AI-powered "next steps"?)

    Retro

    • cost estimation for agents @georgemunyoro
      • TODO
    • wrap up notebook widgets, work through the BI tasklist @mariusandra + supported by @annaszell
      • wrapping up notebook widgets as we speak
      • was out 🌡️ for 2 days, didn't get to BI tasklist
    • python notebooks launch and post launch, semantic layer? @sinan-ku
      • TODO
    • more feedback on notebooks @annaszell
      • TODO

    Tasks

    Plan

    High priority

    Low priority / side quests

    Are any other teams impacted by this plan? If so, tag them here

  8. meikelmosby commented on Sep 16, 2026

    @meikelmosby
    meikelmosby
    on Sep 16, 2026
    Collaborator

    Team Workflows

    Time Off

    Quarter goals - Q3 2026 objectives

    Details
    • 🟡 Become a 2030 Workflows Product (@mayteio)
      • 🟡 Fully AI native & agentic workflow product
        • ✅ Chat interface for rapid iteration
        • ⚪ Move to read-only UI for workflows / email templates / messaging
      • ⚪ Removal of hefty existing UI if new experience & user testing is superior
      • ✅ Revisions
      • 🟡 Reshape APIs to be agentic-friendly for rapid turnaround
    • 🟡 Fit into self-driving products (@dmarchuk)
      • 🟡 Get our data right so 'self-driving' can first suggest changes
      • 🟡 Integrate with 'self-driving' to propose the change (using revisions and APIs)
      • ⚪ Test revisions of actions against each other for improvements (still human in the loop)
      • ⚪ Self-driving applying the outcomes of the A/B tests
    • 🟡 Reliability & Trust (@meikelmosby)
      • ✅ Harden our systems to never drop data
      • ✅ Finalise the re-run system so we can replay failed invocations
      • ✅ Full visibility into every messaging channel
    • 🟡 Nail Messaging (@dmarchuk and @meikelmosby)
      • 🟡 Behavioural cohorts (no backfilling)
      • 🟡 Push notifications
      • ⚪ A/B testing
      • ✅ Email events
      • ✅ Messaging metrics
      • ✅ Email with multiple links / more detailed metrics

    ✅=finished, 🟡=in progress, 🔴=won't finish, ⚪=not started

    Retro

    Details

    @dmarchuk

    • build a self improving loop (v0)
    • roll out push to GA with discounted pricing for now (same as destinations)
    • create channel for push-feedback to get traction
    • experiment for growth: separate out broadcasts as its own thing, ai first & great ux

    @mayteio

    • rollout of AI stuff to GA or have a plan for it

      • park a workflow until a AI task is completed (wait until)
      • similar to destinations being triggered the last 7d something like that for workflows
      • Grafana
      • docs
      • alerts
      • FLIP THE FLAG

    • Experiment for PHAI being the default view when creating a new workflow or email template

    • Attempt to isolate the workflows product to improve the CI story

    AI tasks improvements

    • Cannot blast-radius from slack or GitHub triggers
    • Service user owner of tasks to prevent personal billing

    Lower priority

    • Email sender config UX improvements
    • reusable action templates / canonical settings (RFC)

    @meikelmosby

    • workflow email tiers for domain warm-up & to protect SES reputation

      • implement tier calculation and backfill for all teams
      • collect metrics about throttling & caps
      • notifications after rollout for demotion and promotion of tiers
      • send email about this change to all customers
      • verify collected metrics & roll-out to everyone

    • automatic shutdown of harmful email steps within workflows

      • hourly calculation of harmful workflows against bounce & complaint rates
      • shutdown of workflows
      • notifications at warning level with grace period & then automatic shutdown of harmful workflows
      • rollout to everyone

    • roll out email tier for everyone

    • roll out automatic shutdown of harmful email steps in workflows to everyone

    • move all legacy plugin transforms to hog

    • find sustainable solution for blast radius query constantly OOMing

    • DLQ for cdp & workflows

    • Smokescreen canary for cdp & workflows

    • Entity relationship feature

    • realtime supported cohorts

      • trigger type
      • wait until
      • for all actions
      • batch workflows

    @abheek9

    • growth growth growth with sales
    • growth growth growth with onboarding
    • analysis with templates (2 are used the rest is rubbish, trash them)
    • docs & stuff

    This Sprint

    @dmarchuk

    • build a self improving loop (v1)
    • experiment for growth: separate out broadcasts as its own thing, ai first & great ux

    @mayteio

    • Marketing Push for PostHog Tasks, Loops etc.
    • Attempt to isolate the workflows product to improve the CI story

    AI tasks improvements

    • Cannot blast-radius from slack or GitHub triggers
    • Service user owner of tasks to prevent personal billing

    Lower priority

    @meikelmosby

    • DLQ for cdp & workflows

    • realtime supported cohorts

      • trigger type
      • wait until
      • for all actions
      • batch workflows

    • Entity relationship feature (workflows & cdp with action, cohorts & integrations)

    • managed IP pools for email tiers

    • growth work

    @abheek9

    • growth
    • support with marketing

  9. frankh commented on Sep 16, 2026

    @frankh
    frankh
    on Sep 16, 2026
    Contributor

    Team APM (formerly Team Logs)

    Support hero:

    Quarter goals (ends September 30th)

    Details APM in GA - Ship Metrics + Tracing and have paying customers - All 3 should feel like complete products, not obvious missing basic features that competitors have Product autonomy - Headless usage is a (or the?) typical way to use the product (e.g. a significant number of customers use MCP more than UI) - Work on MCP visibility so we can track headless usage - Build a (proactive?) Agent SRE - Expand signals - Anomalies - Spikes - Rate limits - Error logs ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned

    Retro

    Details

    High priority

    • 🟢 finish anomaly detection @jonmcwest
    • 🟡 add metrics autocapture to SDKs @frankh
    • 🟡 custom retention+per service retention @frankh @abheek9
    • 🟢 implementation RFC for unified alerting @jzhu13 @jonmcwest
      • turning ben's doc into concrete implementation plan
    • 🟢 addressing customer metrics feedback @DanielVisca
    • 🟢 user interviews @abheek9
    • 🔵 metrics collection summary @jonmcwest
    • 🟢 better integrations between metrics+posthog products @DanielVisca
    • 🟢 explore APM<->Error tracking integrations @jzhu13
    • 🟢 promql compatibility @frankh

    Low priority / side quests

    • 🟢 more chart customization / grafana parity @frankh @DanielVisca
    • 🟢 optimise metrics queries @frankh
      • 🟢 why overview page lags
      • 🟢 much faster attribute filtering

    High priority

    • add metrics autocapture to SDKs @frankh

    • finish custom retention+per service retention @frankh @abheek9

    • attribute json parsing @jonmcwest

    • logs alerting shadowed on new alerting @jzhu13 @jonmcwest

    • better query size management for paid customers @jonmcwest

    • booking the offsite

    • ingestion framework refactor

      • compare with/without avro

    • traces customer comms + grandfathered usage @abheek9

    • collect more metrics customer feedback @DanielVisca

      • metrics user interviews

    • link sessions to logs/traces/metrics @jzhu13

    • error tracking -> APM linking @jzhu13

    • cloudwatch integration @jzhu13

    • prom remote write path verified and send all dev metrics via it @frankh @DanielVisca

    • book Q4 planning @frankh

    Low priority / side quests

    • more hiring/stealing from other teams?
    Details ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned

  10. rorylshanks commented on Sep 16, 2026

    @rorylshanks
    rorylshanks
    on Sep 16, 2026
    Contributor

    Team ClickHouse

    AKA Team Read Fewer Bytes Please

    Quarter Goals

    🧬 Cell-based architecture @rorylshanks
    📦 JSON datatype in the app @rorylshanks
    🔐 ClickHouse is up to date and secure @tpgilmore
    🚚 ClickHouse migration system @orian
    🗑️ Data lifecycle management @orian
    🤖 Self-driving operations @bciaraldi

    Retro

    Details

    High priority

    Low priority / side quests]

    • HogQL Language Server @orian

    🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started

  11. vdekrijger commented on Sep 17, 2026

    @vdekrijger
    vdekrijger
    on Sep 17, 2026
    Contributor

    Team Query Performance

    Support hero: @aspicer
    Off during the sprint:

    ⚪ = Not Started · 🟡 = In Progress · 🟢 = Completed · 🔴 = Won't complete · 🔵 = Abandoned · 🟣 = Ongoing

    Quarter goals

    Carry-forward context for Q4 planning; updated goals and owners still need team agreement.

    • 🟡 Improve HogQL query quality and performance. Continue query analysis, guidance and guardrails. Goal-level completion measures still need confirmation.
    • 🟡 Protect ClickHouse from disproportionate query usage. Andy has proposed event-volume-scaled API read-byte limits, initially in shadow mode. The scaling window remains open for discussion. Proposal
    • ⚪ Monitor query regressions and develop automated investigation. Confirm the agreed first delivery and success measure during Q4 planning.
    • HogQL DevEx / ClickHouse support: confirm current priorities and status for experiment logs, legacy endpoints and JSON-column work; no completion is inferred from missing updates.
    • Ownership transition: dashboards, actions, exports, subscriptions and alerts are moving to Product Analytics. Carry remaining product work in the handover, with any finishing commitments explicitly agreed. Handover context

    Retro

    Retro notes are here

    Tasks

    Based on the previous sprint's high-priority plan:

    @andyzzhao

    • 🟣 Query rate limiting: next rollout proposal is ready for feedback, with shadow-mode validation planned.
    • 🟣 Support data retention: status to confirm.
    • 🔵 Query rewriting wizard skill: status to confirm.
    • 🟢 Additional verified delivery: removed the HTTP-level query coalescer in #100667, merged 16 September.

    @aspicer

    @mjwarren3

    • 🟢 Growth reviews
    • 🟡 Data retention decision

    @vdekrijger

    Plan

    High priority

    Proposed for discussion; confirm priorities and capacity before treating these as commitments.

    @andyzzhao

    • session v3
    • rate limit rollout

    @mjwarren3

    • Data retention decision
    • Update cowork scheduled task on query performance (simplify US one, add EU one)
    • Look into what monthly metrics we might track for query performance
    • Exploration: Bounce rate based on query time

    @aspicer

    • Improve query scanner
    • Enable query scanner for API / MCP calls
    • Work on insight by insight performance metrics

    @vdekrijger

    • I'd like to see what comes out of Q4 Planning, but I would like to work on improving our observability and gain better visibility into customer frustrations first things first.
    • Support the handover towards product-analytics, and possibly keep the prompt subscription work on context and pulse in a side agent.

    Low priority / side quests

    Are any other teams impacted by this plan? If so, tag them here

  12. sakce commented on Sep 17, 2026

    @sakce
    sakce
    on Sep 17, 2026
    Contributor

    Team Modeling Sausages

    Quarter goals

    🟢 Objective 1: Semantic layer (owner: Thiago)
    🟡 Objective 2: Integration with Managed warehouse (owner: Jovan)
    🟡 Objective 3: Version control (owner: Jovan)
    🟡 Objective 4: Testing (owner: Thiago)
    🟢 Side quest 1: Templated models (owner: Anna)

    Retro

    Good progress on semantic layer performance. Testing framework made safer and faster. UX of modeling in an okay spot now. Version control under way.

    Details @thiagosalvatore - 🟢 finish the data quality / test framework and release it internally - 🟢 analyze the semantic layer scout reports + merge the new `metric list`, `metric describe` tools and compare to see if the numbers are improving - explore how we can analyze query patterns from our clients to start proposing metrics proactively - see if there are metrics that could be created on the semantic layer for EVERY new org that joins posthog

    @sakce

    • 🟢 heavy customer modeling usage optimization
      • ball on their side of the court to implement changes
    • 🟢 retire v1 modeling workflow
    • 🟡 reviving version control - working on an RFC and going back to understanding requirements
    • 🟡 tracking which models are in demand by queries
    • 🟢 lots more UX work around Models scene
    • 🅿️ start blocking CH data modeling usage after "free" tier (decide the free tier first)
      • investigating where the free tier lies, we landed on "why allow CH at all?" - so if a team wants to materialize, they get a MWH
    • ⚪ incremental views (on trino; how do dependencies work? where's it sit with the version control system)
    • ⚪ UX of modeling together with the managed warehouse

    @annaszell

    • ⚪ hogfood the semantic layer
    • ⚪ UX ideas for the data catalog product

    Plan

    @sakce

    • version control RFC & v1
    • managed warehouse UX with data modeling & onboard to Trino (figure out where we're at)

    @thiagosalvatore

    • publish documentation about the test framework and release it to alpha
    • setup a pre-built dashboard for data quality so customers can have visibility of historical failures and current situation of their tests
    • add metrics to data lineage
    • work with the team to figure it out customers for the alpha release of the test framework

  13. rafaeelaudibert commented on Sep 18, 2026

    @rafaeelaudibert
    rafaeelaudibert
    on Sep 18, 2026
    Member

    Team Growth

    Support hero: @fercgomes
    Off during the sprint:

    Quarter goals

    1. Redesign authentication and onboarding flows 🟢 (@fercgomes)
    2. Measure success of the AI positioning at the company level 🟠 (@rafaeelaudibert, @minekansu)
    3. Streamlined data layer for the RevOps flow 🟠 (@MattBro)
    Details ⚪ = Not Started 🟡 = In Progress and On-Track 🟤 = In Progress and Off-Track 🟠 = Completed in essence, going the extra mile 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned

    Plan

    High priority

    • Act on feedback from other teams around ICP scope calculation - @MattBro
    • Figure out what's next on the wizard architecture - @MattBro and @PostHog/team-wizard-docs
    • Expose wizard cloud runs throughout the app - @fercgomes
      • Experiment running for AI Observability + audit in billing page
    • Cleaning up the OAuth flow - @rafaeelaudibert
    • Audit all empty states in a brand new account - @rafaeelaudibert

    Low Priority / side quests

    Retro

    Details
    • Figuring out how we make people actually pay for self-driving after the 3 free PRs @rafaeelaudibert ❌ but I tried 🟠
    • Monitor the new sidebar campaigns @rafaeelaudibert 🚧
    • Improvements for AI-pilled calculation
    • Agree on interface to feed lead gateway @MattBro ❌
    • Evaluate whether startup/YC plans are worth it @minekansu ❌
    • Handoff SalesOps things over to Erika @minekansu ✅
    • Ship interactive cloud runs for the wizard @fercgomes 🟠

    Low Priority / side quests

    • Add PostHog Desktop/Slack/Self-Driving to the sidebar ads rotation @rafaeelaudibert ✅
    • Consider building the embedding layer for AI chats/event properties @rafaeelaudibert ❌
    • POC on how we could cross-sell based on wizard data @MattBro ❌
    • Keep building prinbox.dev multianalytics hydra @fercgomes ✅

    What else did we do?

  14. hpouillot commented on Sep 18, 2026

    @hpouillot
    hpouillot
    on Sep 18, 2026
    Contributor

    Team Error Tracking

    Previous sprint: #92782 (comment)

    Retro 🟢 🔴 🟡 🚫

    @hpouillot - Finish fingerprints modal 🟢
    @hpouillot - AI Triage 🚫 -> Jev test

    @ablaszkiewicz - Finish with new wizard + empty state screen 🟢
    @ablaszkiewicz - Stretch: review global onboarding screen ? ->
    Incident management on git creds

    @cat-ph - alerting all the way 🟢 Backend merged, front-end waiting review

    Objectives for the quarter

    Onboarding
    Alerting
    Fingerprint
    Release Management
    Integration

    Team PRs

    @ablaszkiewicz

    @cat-ph

    @hpouillot

    @fivestarspicy

    High priority

    @fivestarspicy - surveys on code health
    @fivestarspicy - subs analysis

    @hpouillot - poc with jev
    @hpouillot - alerting follow ups

    @ablaszkiewicz - releases on interpreted languages
    @ablaszkiewicz - better github context

  15. Radu-Raicea commented on Sep 21, 2026

    @Radu-Raicea
    Radu-Raicea
    on Sep 21, 2026
    Member

    Team AI Observability

    Retro

    Details

    Plan (W39, W40)

  16. lucasheriques commented on Sep 21, 2026

    @lucasheriques
    lucasheriques
    on Sep 21, 2026
    Contributor

    Team MCP Analytics

    Support hero - @gesh

    OKRs

    Details
    • 🤖 Goal 1: Self-Driving MCP
    • ✨ Goal 2: Magical Onboarding
    • 🚀 Goal 3: Launch & GA
    • 💫 Goal 4: Skills & CLI Analytics (stretch)

    See all goals in detail here

    This team and product is very new, so it's likely those will change throughout the quarter

    Retro

    Details ⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned 🟣 = Ongoing

    @gesh

    • ⚪ Scout to monitor our MCP server and suggest new MCP analytics features
    • 🟢 Missing capabilities capturing in our MCP server via TS SDK
    • ⚪ Feed missing capabilities into self-driving
    • 🟢 Support capturing agents' feedback

    @lucasheriques

    Original goals:

    • Harness, intent clusters and failure logs showing as "unknown"/blank
    • conversation-level quality insight, not summaries: was the user happy, if not why and how to fix it, trended and clustered by topic
    • See how to handle multiple mcp servers in project

    Actual goals (changed mid sprint):

    • 🟢 Make MCP Analytics capture and attribution reliable across models, resources, harnesses, and SDKs.
    • 🟢 Improve onboarding and core usability through setup tracking, dashboard fixes, Activity, Notifications, and shared filters.
    • 🟢 Ship explicit session feedback collection, with Georgis owning the analysis follow-up.

    @lucasheriques

    • Ship shared filters and per-server visibility, validated with two MCP servers in one project (#73814).
    • Add the MCP protocol/client version breakdown requested by Resend after confirming the exact dimension.
    • Remove remaining blank or unknown data from Sessions and failure views, then validate it against real customer data.

    @gesh

    • Support 2 weeks
    • Create a new tab for agent feedback
    • Scout to monitor our MCP server and suggest new MCP analytics features

  17. TueHaulund commented on Sep 21, 2026

    @TueHaulund
    TueHaulund
    on Sep 21, 2026
    Contributor

    Team Session Replay

    Support hero:

    @arnohillen

    OKRs

    🚀 Goal 1: Make Replay Vision the fastest growing PostHog product by revenue
    💰 Goal 2: Solve cost and pricing
    🛠️ Goal 3: Build out Replay Vision
    👥 Goal 4: Build group summaries
    🧠 Goal 5: Contribute AI improvements back into Session Replay

    Retro ✅ 🔴 🟡 🚫

    ✅ @fasyy612 'Read' state on observations list
    ✅ @fasyy612 Semantic search UI improvements

    🟡 @arnohillen Improve LLM testing for Replay Vision
    🟡 @arnohillen Setup more experiments for the calibration tab and nudge users to try it out

    High priority

    @ksvat Get what-to-watch feed polished + released
    @ksvat Scanner overview polish
    @ksvat Usage view polish

    @fasyy612 Polish search UI and improve performance
    @fasyy612 Iterate on observation tab in Session Replay

    @arnohillen Wrap up RV testing work for handover

    @fivestarspicy Follow up on compression-algorithm proposal
    @fivestarspicy Cost-tagging crypto shredding
    @fivestarspicy Follow up w/ event team wrt customer-meeting @ small team offsite in SF

    @TueHaulund Implement highlight-reel generation

    Side quest

    @ksvat Make decision on goal-based-flow
    @arnohillen Go over old open PRs

  18. thmsobrmlr commented on Sep 21, 2026

    @thmsobrmlr
    thmsobrmlr
    on Sep 21, 2026 – with Claude Github MCP Connector
    Collaborator

    Team Product Analytics

    Support hero: @GeneralistDev
    Off during the sprint:

    • 🌴 @thmsobrmlr — likely 1 day off during the sprint
    • 🌴 @MattPua — 30 September 2026 → 10 October 2026
    • :hahabusiness: @sampennington — at a conference 22–23 September 2026, also travelling some of 21 September 2026
    • :hahabusiness: @GeneralistDev — at the same conference 22–23 September 2026 (minus travel)

    Quarter goals

    Details
    1. MCP/Wizard improvements and Slack bot
      1. How it's displayed across harnesses and agents
      2. Make product analytics easier and more useful to access from Claude Code, Slack, etc.
      3. AI knows when to use a runner rather than one-shotting SQL every time
    2. Improvements and features for core product analytics (Prioritized list in GitHub, Papercuts, Tech debt)
      1. Sam
        1. Make creating insights and dashboards via MCP faster and better quality (Reports that users will need #1)
        2. Make charts great everywhere
        3. ✅ More options and flexibility with date queries (Mapping xpaths to our product #2)
      2. Thomas
        1. 🔁 Dogfood MCP analytics so working with insights and dashboards doesn't feel sluggish (Reports that users will need #1)
        2. ✅ Dashboard filter overrides and chart color enhancements (Mapping xpaths to our product #2)
        3. 🔁 Paths V2 (Mapping xpaths to our product #2)
        4. 🔁 Remove legacy filters and legacy insights, and move code to the "product analytics" product (Mapping xpaths to our product #2)

    Retro

    Details

    High priority

    Low priority / side quests

    • Run some experiments around insight/chart type discovery @sampennington
    • Work on legacy removal and separating product analytics things into our folder @thmsobrmlr
    • Property usage in insights/dashboards/etc. @thmsobrmlr

    Plan

    High priority

    • Create a PA home tab once again, launch experiment @GeneralistDev
    • Continue with usability testing and user interviews @GeneralistDev
    • Make the load times feel faster for dashboards & insights, lazy load as much as possible particularly in sidebars @MattPua
    • Spend more time on dashboard drag & drop — people aren't loving it @MattPua
    • Iterate/expand dashboard template experiments, inc. default template, and others @sampennington
    • Get chart picker experiment live @sampennington
    • Finish off all started stuff before going into the next quarter: fix for faulty regexes, filters removal, moving our things to the product analytics folder (at least stuff we had before the analytics platform re-merge), Paths V2, property usage tracking @thmsobrmlr
    • Add quality metrics / activation back to growth reviews @mjwarren3

    Low priority / side quests

    • Monitoring MCP tool usage and potentially more skill tweaks @GeneralistDev
    • (Timebox — 1 day) Improving the eval sandbox harness to make working on evals easier going forward @GeneralistDev
    • Work with the platform UX team to get some alignment @GeneralistDev
    • User research — interview a bunch more people before Q planning @sampennington
    • Some tweaks to alerts in Slack to make them more usable (similar to Grafana alerts) @MattPua
    • Figure out how to increase adoption of anomaly alerts @MattPua

    Are any other teams impacted by this plan? If so, tag them here

  19. richardsolomou commented on Sep 21, 2026

    @richardsolomou
    richardsolomou
    on Sep 21, 2026
    Member

    Team Context & MCP

    Support hero: N/A
    Off during the sprint: Nobody!

    Quarter goals

    • 🟡 Goal 1: Prove or disprove whether the context layer works, improves agent outcomes, and is something that users want
    • 🟡 Goal 2: Identify ideal MCP architecture
    • 🟡 Goal 3: Identify Skills store and MCP store next steps

    Retro

    First sprint planning!

    Plan

    High priority

    @richardsolomou

    • Look into current state of Skills and MCP stores and how they work
    • Start looking into users of both stores and find people to jump on a quick call with
    • Support and incident stuff

    @adboio

    • research usage for existing "context" products (business knowledge, semantic layer, phai memory)
    • conduct user interviews for people who do and don't use those existing products

    @JakeRuth

    • (not this team) finish up migration of Tasks -> Conversations, currently in progress/going well
    • Finish up finalizing "learn" tool for MCP for skill discovery (took ownership on this from Georgiy, close to release)
    • Dive DEEP on MCP. What are the best architectures? Is ours good? Does it scale? Gain hard opinions here and share with the team

    Low priority / side quests

    • how can i use jev in the context layer @adboio

    Are any other teams impacted by this plan? If so, tag them here

    • @PostHog/team-self-driving
    • @PostHog/team-posthog-desktop

  20. jurajmajerik commented on Sep 23, 2026

    @jurajmajerik
    jurajmajerik
    on Sep 23, 2026
    Contributor

    Team Experiments 🧪

    Retro

    Sprint #18, from Sep 7, 2026 to Sep 20, 2026

    Anders

    • Flags V2

      • Good progress!
      • Shipped lots of PRs

    • Code cleanup and refactors

      • Deleted a lot of code

    Juraj

    • Prompt management

      • Prompt references (partials), end to end: tracked (#101224), validated on publish (#101471), resolved at fetch time (#102076), protected from deletion (#101609, #103037), editor support (#102368), docs (#20289)
      • Batch fetch in one request, by label (#96137) and unlabeled (#966, #5000), in the Python (#938) and JS (#4903) SDKs; docs (#20093, #20238)
      • SDK hardening: malformed rows and old servers handled (#942), throw instead of silently returning nothing (#4961), refetch cooldown after failures (#968)

    • Precompute & query performance

      • Precompute extended to avg/min/max metrics (#96149) and unique user/session means (#98356); retention precompute kill switch removed after a clean soak (#102073)
      • Audit fixes: coverage decided on the job set actually served (#97252), reads can't see half-built windows (#97251), stuck windows unblocked (#96127)
      • Canary hardening: empty reads flagged instead of skipped (#98966), byte-capped and untestable queries no longer waste runs (#98284, #100496)
      • Staff tooling: read latency trends (#96150), TTL verdict banner (#96526), bytes-per-read now measures cache pruning correctly (#98180)

    • Shared metrics safety

      • Editing a shared metric used by running experiments blanked their results with no warning; save (#101234) and delete (#101605) now warn first
      • Save errors surfaced, double submits blocked (#101842); edit page lists which experiments use the metric (#102790)

    • Experiments UI & history

      • Retention metrics can anchor on the exposure event (#102768)
      • Single-metric results in one panel (#100993); compact velocity stats (#101205)
      • History tab noise cleanup: calculator drift no longer logged (#101606), proper lifecycle copy (#101853), freeze-driven flag rewrites explained (#102075)
      • Fixes: metric loads no longer hang on late flag resolution (#96525), invalid user queries no longer logged as platform failures (#100479)

    Marcel

    • What-to-watch

      • Now rolled out to 15% of users as experimental feature
      • #95330 - fix(experiments): compare the watch shelf over the exposed population
      • #99529 - fix(experiments): watch shelf compares first sessions after exposure
      • #92859 - feat(experiments): give the watch shelf an honest empty state
      • #98598 - fix(experiments): leave null session ids out of the watch shelf comparison
      • #101181 - fix(experiments): say the watch shelf is unavailable for group-aggregated experiments

    • Recordings tab

      • #83999 - feat(experiments): add filter for in-session exposure
      • #95046 - fix(experiments): clip replay session variants to the experiment window
      • #95050 - fix(replay): reach exposures captured outside the playable window
      • #98912 - fix(experiments): anchor recordings metric filter to the latest exposure
      • #98917 - fix(experiments): open experiment recordings at the exposure
      • #98902 - perf(experiments): cheaper exposure linkage for pinned and empty lists
      • #96196 - feat(experiments): explain why the recordings tab list is empty
      • #96938 - fix(experiments): Add note for 'hide' setting on an empty list

    • Recordings generally

      • #96102 - fix(replay): stop the recordings list issuing duplicate requests
      • #96802 - fix(replay): read the recordings list once per playlist open

    • Vision

      • #94499 - fix(experiments/vision): give wizard scanners the same population as the recordings tab

    • Other

      • Support
      • #99476 - fix(mcp): point agents at built-in skills instead of the skills store

    Rodrigo

    • PTO 🙂

    • Recalculation

      • Tweaking the UX: make the experience responsive and quick.

    Ruby

    • MCP Improvements

    • Completed tags rollout

    • Initial prompts investigation

    • Growth reviews

    • PTO

    Sprint Goals

    Sprint #19, from Sep 21, 2026 to Oct 4, 2026

    Anders

    • Continue on flags V2

    • Q4 planning prep

    • Side quests

      • Code cleanup / simplification likely

    Juraj

    • Round out Q3 goals - remaining precomputation paths to be covered

    • Prompts issues and hardening

    • Add ability to have multiple recalculation times per day

    • Make timeseries + nightly recalculation opt-in - to reduce load on Clickhouse

    • Q4 planning

    Marcel

    • Analyse if there are any insights from 15% what-to-watch rollout (biggest problem: mostly showing empty)

    • Empty state refinement recordings tab

    • Q3 cleanup

    • Q4 prep/planning

    Rodrigo

    • Recalculations

      • Continue monitoring and working on UX and improvements

    • Breakdown Attribution

      • Complete the backend implementation

    • Prepare for Q4 Planning

    • Move code to product if time allows

    Ruby

    • Prompts RFC

    • MCP errors

    • Client outreach

    • Q4 planning

  21. skoob13 commented on Sep 25, 2026

    @skoob13
    skoob13
    on Sep 25, 2026
    Contributor

    Team Self-driving

    Support hero: @skoob13 (both weeks)
    Off during the sprint: ___

    Quarter goals

    Q3 2026 objectives

    Retro

    Details

    Tasks

    ✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

    Plan

    High priority

    Platform & cost

    Evals

    Scouts

    Pipeline & reports

    Report UX

    User research & measurement

    Desktop feedback

    Low priority / side quests

    Are any other teams impacted by this plan? If so, tag them here

    • DevEx: ReviewHog handover
    • AI Gateway: flex tier fallback and retries
    • PostHog AI: interactive tasks move onto its budget
    • Agent infra: task cost ↔ spend mapping

  22. pl commented on Sep 28, 2026

    @pl
    pl
    on Sep 28, 2026
    Contributor

    Team Ingestion

    Retro

    Details

    High priority

    🟢/🟡/🔴

    • PersonHog
      • 🟢 Implement the janitor delete jobs
      • 🟢 Investigate performance issues in identity
      • 🟢 Do a load test on merge traffic
      • 🟡 Run high traffic benchmarks through ingestion
      • 🔴 Run team 2 shadow
      • 🟢 Move over the personhog replica delete to soft-delete mode
    • Ingestion consumer
      • 🔴 Pack messages into optimally sized batches
      • 🔴 Support timeouts and partial response in the consumer
    • Capture fallback
      • 🟡 Implement selective Kafka config in capture
      • 🔴 Verify Kafka topic existence on startup
    • Capture V1
      • 🟡 Refactor the backend SDKs with v1-only capture
      • 🟢 Add the ai v0/v1 endpoints
      • 🟢 Upgrade ai SDKs to use v1 ai endpoints
      • 🟡 Update docs, specs and runbooks
      • 🟢 Decide what to do with the capture options object

    Incident follow-up

    • 🟡 Restructure WarpStream deployments to isolate capture, ingestion and other services
    • 🔴 Investigate replay duplicates in WarpStream due to timeout misconfiguration

    Support follow-up

    • 🟢 Emit cookieless ingestion warnings

    Side quests

    • 🟢 Alerts review
    • 🟢 Prefetch teams and hog functions on non-analytics lanes
    • 🟢 Improve error tracking retry strategy
    • 🟢 Upgrade sessionreplay WarpStream
    • 🟢 Improve alerts all around
    • 🟡 Isolate capture-analytics and capture-ai

    OKRs

    • 🟢 Scale PersonHog for person property updates
    • 🟢 Harden the persons Postgres database
    • 🔴 Faster, more reliable CI/CD
    • 🔴 Add redundancy and fallback to capture
    • 🟢 Help users self-troubleshoot ingestion issues

    Projects

    High priority

    • PersonHog
      • Run high traffic benchmarks through ingestion
      • Run team 2 shadow
      • Investigate the drift in PersonHog person properties
      • Plan how to move deletes to PersonHog leader
      • Prepare operationally for deploying on prod
    • Ingestion consumer
      • Pack messages into optimally sized batches
      • Support timeouts and partial response in the consumer
    • Capture fallback
      • Implement selective Kafka config in capture
      • Verify Kafka topic existence on startup
    • Capture V1
      • Refactor the backend SDKs with v1-only capture
      • Update docs, specs and runbooks
      • Upgrade to capture-ai v1 for remaining SDKs
      • Isolate capture-analytics and capture-ai
    • WarpStream improvements
      • Move sessionreplay to the new rebalance protocol
      • Isolate produce roles from consume and jobs
      • Upgrade WarpStream everywhere

    Incident follow-up

    • Restructure WarpStream deployments to isolate capture, ingestion and other services
    • Investigate replay duplicates in WarpStream due to timeout misconfiguration

    Support follow-up

  23. marandaneto
    unpinned this issue on Oct 14, 2026
  24. marandaneto
    closed this as completedon Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    sprintSprint planning

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions