You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
-
✅ HogQL batch exports release
✅ Documentation / Changelog entry for closed beta announcement
✅ Where would docs live? Under a new "File download" section in Destinations
✅ Agent skill (maybe current skill already works)
✅ Query size estimation
- Start off with a naive count() endpoint (With execution duration and potentially query size limits).
- When limits exceeded, just report "Warning: TOO MANY ROWS"
- Eventually, monitor load, and try to cache results of count
🟡 Wrap up integration work
✅ Redshift integration
✅ Backend PRs are (almost) ready
✅ Frontend DONE
- Redshift now needs cleanup/migration
🟡 PostgreSQL/S3 integration
- PostgreSQL migration done, clean up pending
- S3 migration done, clean up in progress
🟡 Snowflake integration
🟡 Data migration
- Clean up
✅=finished 🟡=in progress 🔴=won't finish ⚪=not started
High priority
HogQL batch exports
Internal testing required: Let's run a bunch of these.
Roughly in the millions of rows.
Load testing: Can we hook into any existing exports?
Power SQL editor downloads with batch exports.
Support for query placeholders.
Main blocker: Version key, merge key, data interval.
HogQL modifiers
Deprecation of $set/$set_once
Do a quick test on dev to make sure everything works (it should!)!
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
🟡 Migrate more Postgres users away from rds_superuser permissions @langesven (aurora_user_management v3 rollout)
🟡 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.
⚪ Rollout docker terraform provider for docker hub admin @k33lan
⚪ Rollout docker hub OIDC for image pushes instead of tokens @k33lan
✅=finished 🟡=in progress 🔴=won't finish ⚪=not started
Get more out of pganalyze, easier setup, feed it more data, etc @langesven
side quest
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.
🟡 Move prod US apps to Cilium @MichaelKutsch-ph@danielxnj - contour envoys are done among other smaller things, we're almost there! 🥳
✅ NLB + EIP PoC in dev @MichaelKutsch-ph - this needs some dedicated time to plan properly and to take a deep look at side-effects like header-forwarding, timeout settings, DNS setup and general feasibility.
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
Figuring out how we make people actually pay for self-driving after the 3 free PRs @rafaeelaudibert
Make notebooks the default way to analyze data (Sinan)
🟡 Python notebooks for customers
🟢 Polished markdown-first notebook UX
🟢 Better integration with HogQL, DuckDB, external DBs, and visualizations
🟢 AI agents can create/edit notebooks directly (great MCP support)
⚪ Publicly shareable notebooks
Define and level up HogQL as a query engine (George)
⚪ HogQL roadmap with owners and milestones (rust wen?)
🟡 Typed pre-execution errors
🟡 Dry-run and cost estimation for agents
🟢 First optimization passes using the improved type system
🟡 Improved HogQL / query observability
Make BI, SQL, and visualizations feel mature and reusable (Marius)
🟡 Improved charting / visualization UX
🟡 Work with Desktop to standardize PostHog visualization components
🟢 Support more databases as first-class citizens (MySQL, Snowflake, BigQuery, etc)
⚪ Row drilldown from query results (AI-powered "next steps"?)
🟡 SQL editor papercut cleanup
🟡 Variables: multiselect, query-backed, and time-based variables
Retro
solid sprint. performance optimizations, including for database.py @georgemunyoro
Notebooks are ready to be released. Polish, variables, pricing done. Working through an actual release @sinan-ku
Got notebook widgets ready and (almost?) launched internally. Loads of new charting/viz options now. @mariusandra
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
🧬 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
Backfill team 2 data, setup ingestion on test cluster for new schema @rorylshanks 🟡
support events_json in squash and deletes @orian 🟢
⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned 🟣 = Ongoing
Quarter goals
Improve how AI writes HogQL — Andy Zhao
🟡 Measure how performant and correct AI queries are
⚪ Improve the AI context when writing HogQL
Monitor query regressions across internal teams — Andy Zhao, Vasco de Krijger
⚪ Set up automation that monitors PRs into the PostHog repo, flagging any suboptimal queries
⚪ Set up automatic auto research
Improve the DevEx of making HogQL changes — Sandy Spicer
PR gate on having an experiment log on the test cluster
Think about how we can be more confident in HogQL transformations
Protect against small customers using a significant % of our ClickHouse compute — Mike Warren, Andy Zhao
⚪ What should the limits be? Part of packages? (Mike Warren)
⚪ Rate limiting based on cost of queries rather than number of queries, scaled for bigger customers (Andy Zhao)
Make PostHog proactive for analytics users — Vasco de Krijger
🟡 Help users figure out what is relevant to them at a glance / what to best build next
🟡 Forecast alerts
🟣 Further enhance prompt subscriptions
⚪ Allow pre-prompted code agents / tasks to fire as a result of an alert trigger
⚪ Further build out the brainstormed ideas from the product analytics team regarding proactive scouts
Cross product integration — Matt Pua
⚪ Auto-create a dashboard with relevant metrics about your feature when developing with PHCode (or sell as a GH action using the MCP under the hood with widgets?)
🟣 Increase number of widgets available to cover most product areas
🟣 Help increase number of products activated per org
Signal + PHC integration: first class citizens | subs + alerts — Matt Pua
⚪ Integrate alerts + subscriptions as signal sources
Shared team objective: support team ClickHouse in their endeavours
Delete the legacy ClickHouse non-HogQL endpoints, or redirect to HogQL (Sandy Spicer)
🟢 Continue with the remaining support hero work (e.g. adding new apis for the log alerts so that we can add a new TF resource, and adding teams support to subscriptions)
Enabled dedicated exposure event for all teams. Experiments with start_date > 1th of sept. will use the new event in queries. Exact time for when we will stop storing $feature_flag_called in events table not set yet
Juraj
Precompute & query performance
Added a daily job that finds teams with slow experiment queries who would benefit from precompute, as a first step toward enrolling them automatically (#88455). Fixed canary false alarms: tiny event gaps in low-volume metrics no longer page as divergences (#87880), and a missing query tag no longer fails ~52 canary runs a week in EU (#90719). When a user writes invalid HogQL in a metric, they now get a clear error instead of us retrying it and logging it as a platform failure (#90715).
API robustness & MCP
The API accepted misplaced keys in exposure criteria, and experiments saved with them failed every results query. Now rejected on write (#86938) and cleaned up from stored experiments (#88225). Users denied access to a specific experiment could still summarize it through Max; now blocked (#87802). Exposed flag cleanup in the MCP tools (#86946) and removed dead paths from the AI summary tool (#87799). Open: claude.ai hides tools whose schema is too long, and ours was 5 characters under the limit; it now shrinks itself to stay under (#88949).
Experiment history
Rebuilt the History tab on the experiment activity endpoint (#87906), added linked flag changes to it (#88220), and logged pause/resume actions (#88226). Also record who toggled precomputation for a team (#89176).
Experiments UI
Completed experiments no longer warn that results are stale or silently re-run their queries (#88219). Metric actions shown on hover (#87952). Explainer tooltips for p-value and interval (#90712). Aligned results wording with docs (#88216). Smaller fixes: a variant with no data no longer shows a red dash as if it were losing (#90721), interaction polish (#88275), code tab styling (#88266), dead code removal (#90714).
Marcel
PTO
Catching up on everything
Evaluating recordings tab and what-to-watch over PTO period for follow-up tasks
Done:
#87310 - fix(experiments): change scan-skill to use server-derived exposure targeting
#84598 - fix(experiments): Gate Replay Vision on AI-consent and show its price
#91281 - fix(experiments): repair dead qualitative-feedback links in experiment skills
Rodrigo
Metrics recalculation
Reused existing metric results when a metric configuration changes, so a config edit no longer forces a full recalculation (#90484).
Making recalculation react correctly to edits: fold stats_config into the recalculation fingerprint so a stats change invalidates cached results (#92541), and queue a rerun for edits made while a recalculation is already running (#93414).
Breakdown attribution
Shipped the metric breakdown attribution UI so experiment breakdowns attribute the value from the exposure event: added the UI (#84861) and its schema changes (#84867). Persisted the user's choices across sessions: the breakdown limit (#85122) and the attribution mode (#86544).
Running time
Added an endpoint for running-time estimates (#92590) and showed the live remaining time on the experiments list (#92868).
Product folder migration
Moved the experiments scene and its view logic into the product frontend folder: main scene (#87249), legacy experiment view (#87319), view logic (#88856).
Migrated the smaller scene pieces: status tag (#90507), velocity stats (#90508), experiment status (#90511), experiment actions (#90512), and shared constants (#90513).
Continuing with the modals: copy (#90509), duplicate (#90510), cuped (#92586), stats method (#92587), running time config (#92588), details (#92589), timeseries (#92591), select existing feature flag (#92593), experiment metric (#92594), metric source (#92595), shared metric (#92597), and shared metric details (#92598).
@ablaszkiewicz finish with releases 🟢 banner as follow-up to warn cli / sdk mismatch @ablaszkiewicz stretch: onboarding 🟡 hardcore tests with wizard
@cat-ph - alerting poc / design session 🟢 @cat-ph - alerting implementation 🟡 Stack in merging progress @cat-ph - stretch/discuss with client lib: logback plugin for java autocapture (similar to Elixir logger.error capture) 🟢
@hpouillot - Finish issue severity filtering and display 🟢 Backfill to be done @hpouillot - Error tracking loop templates 🚫 Triage automatically 🟡 @hpouillot - Fingerprints visualization 🟡 Merge managing fp with similar issue into a modal @hpouillot - Logs integration 🚫
@fivestarspicy - investigate effect of price changes (free tier changes) @fivestarspicy - another look at our cost (after cost tagging) @fivestarspicy - come up with user research questions
🚀 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
🟢 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
Details@thiagosalvatore
- 🟡 finish the testing framework
- 🟢 release the semantic layer to beta
- 🟢 anything that comes up with the semantic layer once we release it to beta
Details
⚪ = Not Started
🟡 = In Progress
🟢 = Completed
🔴 = Won't complete
🔵 = Abandoned
Retro
Most of the sprint went into the flag_evaluations pipeline, cohort infrastructure, and flag reliability fixes. Haacked shadow-routed $feature_flag_called into flag_evaluations, added observability and cost controls around it, and kept working on removing $feature_flag_called from taxonomy and autocomplete surfaces.
Gustavo made major progress decommissioning warpstream-calculated-events and pushed the realtime cohorts effort forward, then started migrating the flags-cache infrastructure to the posthog-app golden chart.
Patricio shipped flag filter validation and rollout-percentage fixes, closed out several cohort correctness bugs, and built the scoped-JWT work that unblocks the PSAK migration's cross-app access investigation.
James continued the HyperCache Rust port, adding shadow-mismatch tracking and cache-builder dashboards, and separately shipped flag lifecycle endpoints as MCP tools.
Matheus advanced both the cohort_membership_changed cutover and the streaming cohort backfill with a large batch of merged PRs.
@lricoy getting the docs really, really ready @lricoy release the self-driving scouts (csp, web vitals, generic web analytics) for everyone @lricoy shipaton event
@mjwarren3 events pricing update / group analytics changes @mjwarren3 work with arthur to get query and storage data on CA for us
High priority
@arthurdedeus unalive vitally @arthurdedeus backfill whatever data we still have on vitally @arthurdedeus migrate all automations from onboarding team to customer analytics @arthurdedeus rollout new account details UI
@jabahamondes merge attribution explorer precomputation PRs @jabahamondes add revenue, acquisition and engagement metrics to the new marketing dashboard @jabahamondes integrate retention, conversion into the new dashboard (already existing) @jabahamondes track dashboard and Setup usage, goal changes and source connections by entry point, and update the usage dashboard @jabahamondes unalive onboarding in the new dashboard and show useful data immediately @jabahamondes stretch -> include new-customer conversion goals in Acquisition @jabahamondes stretch -> show suggested sources and conversion goals in the dashboard ideally cg would be automatically created
TBD - we're doing planning async and will fill this in ourserlves
🟡 Shipped provider fallback onto Bedrock's Mantle service for GPT models plus new failover telemetry, which then caused a real incident — Codex sent tool shapes the new validation logic didn't recognize, so it got reverted and is back up for review with the fix (#439)
🟡 Making provider traffic splits configurable instead of a hardcoded 50/50, with percentage sliders in the admin (PostHog/ai-gateway#448)
🟢 Reworked the provider-routing admin page to show where a model's traffic is actually going instead of a rule list (PostHog/ai-gateway#417), and fixed it mislabeling active traffic splits as fallback chains
🟢 Fixed two correctness bugs: a poisoned catalog feed could silently delete stored provider rows, and gateway analytics could misattribute one team's traffic to an unrelated person when IDs collided
🟢 Closed out a string of provider compatibility bugs: rejecting empty tool lists, Codex's namespace tools and metadata fields, malformed non-streaming Bedrock responses, and generation metadata drifting across providers
🟢 Added GLM-5.3 and wired Azure OpenAI as a real routing option across all three environments
Side quests:
🟢 Built a mirror so EU generation events reach US dashboards again, with alerting and a new panel — closes the reporting gap the Signals cutover opened
🟡 Quieted the pager for provider overload instead of treating it like a real error, with a new warning-only alert
🔴 Decided against Cloudflare Workers AI dispatch — GLM's Baseten/Modal serving already covers it
🟡 Merged the wizard cutover's mint infrastructure end to end — scoped tokens per run, environment wired in both regions, client IDs set, a routing fix, mint logging (posthog#87269, wizard#1130, charts#14567, charts#14841) — still gated behind a feature flag matching no organizations yet, so no wizard traffic has actually moved
🟡 Billing attribution — stamping which requests are billable and resolving which team to bill — is up for review (PostHog/ai-gateway#414)
🟡 Drafted the RFC for what the gateway looks like after the migration: one budget per run, tier-based model selection, and a real-time billing handoff (#1260), decision targeted for the October AI teams meeting
Side quests:
🟢 Got the gateway attribution and auth RFC over the line
🟢 Extended the Signals cutover to inbox, chat, suggestion runs, and eval-report summaries
🟡 Landed the StampHog review-digest cutover in production; the reviewer leg is staged behind a model-pin flag
🟡 Shipped a flag-driven wizard abuse blocklist for spend farming — self-flagged as a stopgap until a proper admin ban list exists
🟢 Caught and fixed his own pricing bug before it shipped wrong (an OpenRouter promotion fix had overcorrected onto directly-priced models too)
🟢 Fixed a reliability bug that was killing about 9% of self-driving runs mid-task from oversized safety margins on spend holds, plus a related billing bug on aborted requests that delivered nothing
🟢 Closed out the auth-stack design issues
🟢 Led a team-wide API key rotation, cleaning up stale credentials from departed employees
🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started
Land the data warehouse semantic enrichment cutover, pending its AWS secret setup (charts#15162, posthog#94494)- Report which OpenAI fields the Anthropic translation silently drops (#445)
Low priority / side quests
Housekeeping: close PostHog/ai-gateway#432 (resolved by the merged EU mirror), PostHog/ai-gateway#442 (resolved once PostHog/ai-gateway#443 merges), and PostHog/ai-gateway#248 pending its last child issue PostHog/ai-gateway#247
Name every unpopulated event field in one emitter test run instead of one per cycle (#454)
The durability gap: rebuild spend counters after a dropped Redis write (PostHog/ai-gateway#320), record which minted token spent each ledger entry (PostHog/ai-gateway#374), rebuild pending balance from the ledger when Redis recovers (PostHog/ai-gateway#204)
Refill a team's rate-limit buckets from the admin (PostHog/ai-gateway#385)
Are any other teams impacted by this plan? If so, tag them here
@PostHog/team-billing — the billing RFC and the billed-team attribution work both feed into how gateway spend reaches a customer's bill
@PostHog/team-self-driving — signals scout runs still hit an EU rate ceiling with no owner yet (PostHog/ai-gateway#409)
@PostHog/team-ai-observability — the data warehouse enrichment cutover and dropped-params reporting change what shows up in AIO-facing traces
Activity
[-]Sprint - September7 to September 18[/-][+]Sprint - September 7 to September 18[/+]dustinbyrne commentedon Sep 1, 2026
Team Client Libraries
Support hero: @marandaneto then @ioannisj
OOO: 2 days @turnipdabeets
Quarter goals
Q3 2026 objectives
Retro
Details
High priority
posthog-nodeMVP: spans, W3C trace context propagation, OTLP exportLow priority / side quests
Plan
High priority
posthog-nodemanual tracingposthog-pythonmanual tracingLow priority / side quests
Are any other teams impacted by this plan? If so, tag them here
🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started
tomasfarias commentedon Sep 2, 2026
Team Batch Exports
Support hero: @tomasfarias / @rossgray
Quarter goals
Retro
Details
High priority
✅ HogQL batch exports release
✅ Documentation / Changelog entry for closed beta announcement
✅ Where would docs live? Under a new "File download" section in Destinations
✅ Agent skill (maybe current skill already works)
✅ Query size estimation
- Start off with a naive count() endpoint (With execution duration and potentially query size limits).
- When limits exceeded, just report "Warning: TOO MANY ROWS"
- Eventually, monitor load, and try to cache results of count
🟡 Wrap up integration work
✅ Redshift integration
✅ Backend PRs are (almost) ready
✅ Frontend DONE
- Redshift now needs cleanup/migration
🟡 PostgreSQL/S3 integration
- PostgreSQL migration done, clean up pending
- S3 migration done, clean up in progress
🟡 Snowflake integration
🟡 Data migration
- Clean up
✅=finished 🟡=in progress 🔴=won't finish ⚪=not started
High priority
HogQL batch exports
Deprecation of $set/$set_once
Integration clean up
Low priority
Improve SLA alerts
UX/UI for hogql batch exports
Make integrations easier to use for agents
Resource based allocator + auto-scaler for batch export workers
langesven commentedon Sep 2, 2026
Team Cloud Platform
Quarter Goals
Retro
Details
High Prio
Low Prio / Side Quests
rds_superuserpermissions @langesven (aurora_user_management v3 rollout)✅=finished 🟡=in progress 🔴=won't finish ⚪=not started
Plan
High Prio
Low Prio
side quest
Daesgar commentedon Sep 2, 2026
Team Cloud Foundations
Quarter Goals
Retro
Details
High Prio
Low Prio
side quest
side quest
✅=finished 🟡=in progress 🔴=won't finish ⚪=not started
Plan
High Prio
Low Prio
side quest
rafaeelaudibert commentedon Sep 2, 2026
Team Growth
Support hero: @MattBro
Off during the sprint:
Quarter goals
Details
⚪ = Not Started 🟡 = In Progress and On-Track 🟤 = In Progress and Off-Track 🟠 = Completed in essence, going the extra mile 🟢 = Completed 🔴 = Won't complete 🔵 = AbandonedPlan
High priority
Low Priority / side quests
Retro
Details
Low priority / side quests
What else did we do?
mariusandra commentedon Sep 2, 2026
Team Data Fools
Off during the sprint:
Quarter goals
Make notebooks the default way to analyze data (Sinan)
🟡 Python notebooks for customers
🟢 Polished markdown-first notebook UX
🟢 Better integration with HogQL, DuckDB, external DBs, and visualizations
🟢 AI agents can create/edit notebooks directly (great MCP support)
⚪ Publicly shareable notebooks
Define and level up HogQL as a query engine (George)
⚪ HogQL roadmap with owners and milestones (rust wen?)
🟡 Typed pre-execution errors
🟡 Dry-run and cost estimation for agents
🟢 First optimization passes using the improved type system
🟡 Improved HogQL / query observability
Make BI, SQL, and visualizations feel mature and reusable (Marius)
🟡 Improved charting / visualization UX
🟡 Work with Desktop to standardize PostHog visualization components
🟢 Support more databases as first-class citizens (MySQL, Snowflake, BigQuery, etc)
⚪ Row drilldown from query results (AI-powered "next steps"?)
🟡 SQL editor papercut cleanup
🟡 Variables: multiselect, query-backed, and time-based variables
Retro
Tasks
Plan
High priority
Low priority / side quests
Are any other teams impacted by this plan? If so, tag them here
meikelmosby commentedon Sep 2, 2026
Team Workflows
Time Off
Support Hero
Quarter goals - Q3 2026 objectives
Details
✅=finished, 🟡=in progress, 🔴=won't finish, ⚪=not started
Retro
Details
@dmarchuk
@mayteio
Stretch
@meikelmosby
high prio:
workflow email tiers for domain warm-up & to protect SES reputation
automatic shutdown of harmful email steps within workflows
DLQ for cdp & workflows
Smokescreen canary for cdp & workflows
realtime supported cohorts
lifting broadcasts to 1M for team2 rest 500k
low prio:
@abheek9
This Sprint
@dmarchuk
@mayteio
rollout of AI stuff to GA or have a plan for it
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
Lower priority
@meikelmosby
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
realtime supported cohorts
managed IP pools for email tiers
growth work
@abheek9
frankh commentedon Sep 2, 2026
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 🔵 = AbandonedRetro
Details
High priority
Low priority / side quests
Plan
High priority
Low priority / side quests
Details
⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandonedorian commentedon Sep 2, 2026
Team ClickHouse
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]
🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started
vdekrijger commentedon Sep 3, 2026
Team Analytics Platform
Support hero: @andyzzhao
Off during the sprint:
Legend
⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned 🟣 = Ongoing
Quarter goals
Improve how AI writes HogQL — Andy Zhao
Monitor query regressions across internal teams — Andy Zhao, Vasco de Krijger
Improve the DevEx of making HogQL changes — Sandy Spicer
Protect against small customers using a significant % of our ClickHouse compute — Mike Warren, Andy Zhao
Make PostHog proactive for analytics users — Vasco de Krijger
Cross product integration — Matt Pua
Signal + PHC integration: first class citizens | subs + alerts — Matt Pua
Shared team objective: support team ClickHouse in their endeavours
Retro
Retro notes here: https://posthog.slack.com/docs/TSS5W8YQZ/F0B741LSUVA?focus_section_id=temp:C:Ace8f4220fa108e4789928fc6056
⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = Abandoned 🟣 = Ongoing
Tasks
@andyzzhao
@aspicer
@MattPua
@vdekrijger
@mjwarren3
Plan
High priority
@andyzzhao
@aspicer
@MattPua
@vdekrijger
@mjwarren3
Low priority / side quests
Are any other teams impacted by this plan? If so, tag them here
jurajmajerik commentedon Sep 4, 2026
Team Experiments 🧪
Retro
Sprint #18, from Aug 24, 2026 to Sep 4, 2026
Anders
$feature_flag_calledin events table not set yetJuraj
Marcel
Rodrigo
Sprint Goals
Sprint #19, from Sep 7, 2026 to Sep 18, 2026
Anders
Juraj
Marcel
Rodrigo
Radu-Raicea commentedon Sep 4, 2026
Team AI Observability
Retro
Details
Plan (W37, W38)
hpouillot commentedon Sep 4, 2026
Team Error Tracking
Previous sprint: #84504 (comment)
Retro 🟢 🔴 🟡 🚫
@ablaszkiewicz finish with releases 🟢 banner as follow-up to warn cli / sdk mismatch
@ablaszkiewicz stretch: onboarding 🟡 hardcore tests with wizard
@cat-ph - alerting poc / design session 🟢
@cat-ph - alerting implementation 🟡 Stack in merging progress
@cat-ph - stretch/discuss with client lib: logback plugin for java autocapture (similar to Elixir logger.error capture) 🟢
@hpouillot - Finish issue severity filtering and display 🟢 Backfill to be done
@hpouillot - Error tracking loop templates 🚫 Triage automatically 🟡
@hpouillot - Fingerprints visualization 🟡 Merge managing fp with similar issue into a modal
@hpouillot - Logs integration 🚫
@fivestarspicy - investigate effect of price changes (free tier changes)
@fivestarspicy - another look at our cost (after cost tagging)
@fivestarspicy - come up with user research questions
Objectives for the quarter
Onboarding
Alerting
Fingerprint
Release Management
Integration
Team PRs
@ablaszkiewicz
@cat-ph
@hpouillot
@fivestarspicy
High priority
@hpouillot - Finish fingerprints modal
@hpouillot - AI Triage
@ablaszkiewicz - Finish with new wizard + empty state screen
@ablaszkiewicz - Stretch: review global onboarding screen
@cat-ph - alerting all the way
fasyy612 commentedon Sep 7, 2026
Team Session Replay
Support hero:
@fasyy612
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 Touch up observation tab
✅ @fasyy612 Semantic search MVP
@ksvat Revamped goal-based creation flow
@TueHaulund Analytics-based alerts
@TueHaulund Ship scout-based digests (including big DB migration)
@fivestarspicy User research
@TueHaulund Another round on the cost estimation UI
High priority
@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
Side quest
lucasheriques commentedon Sep 8, 2026
Team MCP Analytics
Support hero - @lucasheriques
OKRs
Details
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 🟣 = OngoingHigh priority
@gesh
@lucasheriques
High priority
@gesh
@lucasheriques
thmsobrmlr commentedon Sep 8, 2026
Team Product Analytics
Support hero: @thmsobrmlr
Off during the sprint:
Quarter goals
Details
Retro
Details
High priority
Low priority / side quests
Plan
High priority
working-with-chartsskill, test it on replay vision @sampenningtonLow priority / side quests
Are any other teams impacted by this plan? If so, tag them here
sakce commentedon Sep 8, 2026
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
Details
@thiagosalvatore - 🟡 finish the testing framework - 🟢 release the semantic layer to beta - 🟢 anything that comes up with the semantic layer once we release it to beta@sakce
@annaszell
Plan
High priority
@thiagosalvatore
metric list,metric describetools and compare to see if the numbers are improving@sakce
@annaszell
haacked commentedon Sep 9, 2026
Team Feature Flags
Support hero:
Off during the sprint: haacked, gustavohstrassburger
Quarter goals
Link to goals
Details
⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete 🔵 = AbandonedRetro
Most of the sprint went into the
flag_evaluationspipeline, cohort infrastructure, and flag reliability fixes. Haacked shadow-routed$feature_flag_calledintoflag_evaluations, added observability and cost controls around it, and kept working on removing$feature_flag_calledfrom taxonomy and autocomplete surfaces.Gustavo made major progress decommissioning warpstream-calculated-events and pushed the realtime cohorts effort forward, then started migrating the flags-cache infrastructure to the posthog-app golden chart.
Patricio shipped flag filter validation and rollout-percentage fixes, closed out several cohort correctness bugs, and built the scoped-JWT work that unblocks the PSAK migration's cross-app access investigation.
James continued the HyperCache Rust port, adding shadow-mismatch tracking and cache-builder dashboards, and separately shipped flag lifecycle endpoints as MCP tools.
Matheus advanced both the cohort_membership_changed cutover and the streaming cohort backfill with a large batch of merged PRs.
Details
@haacked
Flag evaluations pipeline:
Taxonomy cleanup:
Replay:
HyperCache observability:
Ingestion:
PostHog Code desktop:
Docs:
Side quests:
@gustavohstrassburger
Warpstream decommission:
Realtime cohorts:
Cohort fixes:
Golden-chart migration:
Docs:
@JamesPatrickGill
HyperCache Rust port:
Cache builder dashboards:
Flag lifecycle and tooling:
Devex:
@matheus-vb
Realtime cohort membership cutover:
Streaming cohort backfill:
Cohort write correctness:
HogVM fix:
@patricio-posthog
Flag filter validation:
Rollout percentage and filter validation follow-ups:
Cross-app access investigation:
Other fixes:
Plan
Project Board
High priority
@haacked
$feature_flag_calledin taxonomy, autocomplete, and product surfacesflag_evaluationsrouting@gustavohstrassburger
@JamesPatrickGill
@matheus-vb
@patricio-posthog
Side quests
lricoy commentedon Sep 10, 2026
Team Web Analytics
Legend
⚪ = Not Started 🟡 = In Progress 🟢 = Completed 🔴 = Won't complete
Support hero
@jordanm-posthog
Retro:
Details
High priority
🟢 @jabahamondes global on-call
🟢 @jabahamondes retention analysis on marketing analytics
🟡 @jabahamondes improve the performance of Mike's new attribution explorer
🟢 @jabahamondes submit Meta's scopes and reviews
⚪ @jabahamondes OOO next week
🟡 @arthurdedeus unalive vitally
🟢 @arthurdedeus track account rules
🟢 @arthurdedeus wrapped up gmail sync issues
🟡 @arthurdedeus backfill whatever data we still have on vitally
🟢 @arthurdedeus fixing papercuts
🟢 @arthurdedeus level up observability of the whole system, especially schedulers
⚪ @arthurdedeus certification for restricted scopes on Google APIs
@jordanm-posthog @lricoy getting aeo on early access alpha
@jordanm-posthog user interviews on aeo/seo
stretch: @jordanm-posthog implement a demo on our aeo/seo improvements
@lricoy getting the docs really, really ready
@lricoy release the self-driving scouts (csp, web vitals, generic web analytics) for everyone
@lricoy shipaton event
@mjwarren3 events pricing update / group analytics changes
@mjwarren3 work with arthur to get query and storage data on CA for us
High priority
@arthurdedeus unalive vitally
@arthurdedeus backfill whatever data we still have on vitally
@arthurdedeus migrate all automations from onboarding team to customer analytics
@arthurdedeus rollout new account details UI
@jabahamondes merge attribution explorer precomputation PRs
@jabahamondes add revenue, acquisition and engagement metrics to the new marketing dashboard
@jabahamondes integrate retention, conversion into the new dashboard (already existing)
@jabahamondes track dashboard and Setup usage, goal changes and source connections by entry point, and update the usage dashboard
@jabahamondes unalive onboarding in the new dashboard and show useful data immediately
@jabahamondes stretch -> include new-customer conversion goals in Acquisition
@jabahamondes stretch -> show suggested sources and conversion goals in the dashboard ideally cg would be automatically created
TBD - we're doing planning async and will fill this in ourserlves
richardsolomou commentedon Sep 14, 2026
Team AI Gateway
Support hero: N/A
Off during the sprint: Nobody!
Quarter goals
The published goals still describe the productization plan and are stale after the 4 August re-focus onto self-driving.
Retro
Details
@richardsolomou
@brandonleung
🟢 =finished 🟡=in progress 🔴=won't finish ⚪=not started
Plan
High priority
@richardsolomou
@brandonleung
Low priority / side quests
Are any other teams impacted by this plan? If so, tag them here
pl commentedon Sep 14, 2026
Team Ingestion
Retro
Details
High priority
🟢/🟡/🔴
Incident follow-up
Support follow-up
Side quests
OKRs
Projects
*
*
*
High priority
Incident follow-up
Support follow-up