Sprint - April 20 to May 3

[dustinbyrne]

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

-

[dustinbyrne]

Team Client Libraries

Support hero: @dustinbyrne then @marandaneto
OOO: @marandaneto @ioannisj 1 day

Quarter goals

• ⚪ Goal 1: What makes PostHog more tailored to how you actually use it
  • ⚪ Discover SDK + default gaps
  • ⚪ Proactive user research (interviews, surveys, mobile/backend focus)
  • ⚪ AI-assisted SDK setup + usage improvements
• ⚪ Goal 2: PostHog libraries vNext
  • ⚪ Offline-first / async-first posthog-js
  • ⚪ Distributed tracing headers + remote config support
  • ⚪ More framework-specific wrappers
  • ⚪ Framework expansion (e.g. Angular wrappers)
  • 🟡 Mobile session replay (triggers, min duration, RN/Flutter/macOS, perf)
  • 🟡 Mobile error tracking (iOS improvements, RN support & restructuring, breadcrumbs)
  • ⚪ Flutter desktop support (Windows/Linux)
• 🟡 Goal 3: Maintaining the SDKs
  • ⚪ SDK test harness + CI integration
  • 🟢 SDK rotation ownership
  • ⚪ Config standardization (API key/token)
  • ⚪ Ingestion rate limiting support
  • 🟢 Unified remote config endpoint (/static/token/config)
  • ⚪ SDK design guidelines and best practices
• ⚪ Goal 4: Log for Mobile
  • ⚪ Add support for collecting and sending app-side logs from Android
  • ⚪ Add support for collecting and sending app-side logs from iOS
  • ⚪ Add support for collecting and sending app-side logs from Flutter
  • ⚪ Add support for collecting and sending app-side logs from React Native

Retro

Details

High priority

• 🟢 Get Anna up and running & discover at least 2 new food obsessions @PostHog/team-client-libraries
• 🟡 iOS rage touch support @ioannisj
• 🟡 Android element interaction autocapture & rage touch @ioannisj
• ⚪ React Native plugin for native exceptions - error tracking (Android and iOS) @ioannisj
• 🟡 Review and finalize autoresearch results on iOS/Flutter replay perf @ioannisj @marandaneto
  • 🟡 Flutter @marandaneto
  • ⚪ iOS
• 🟢 Unified remote config endpoint (/static/token/config) @marandaneto
  • Replace SDKs using the old one if needed
  • Remove &config=true from all SDKs if not yet
• 🟢 Clean up stale issues/PRs across most important SDKs @marandaneto
• 🟡 Snippet v2 live on posthog.com @dustinbyrne
• 🟡 Metrics and observability for snippet v2 infrastructure @dustinbyrne
• 🟡 Snippet v2 runbooks @dustinbyrne
• 🟡 Managed reverse proxies support dynamic script loading of versioned assets @dustinbyrne
• 🟡 Wrap up symbol set versions and project for React Native @turnipdabeets
• 🟡 Update version and project names in iOS tooling @turnipdabeets
• 🟢 Promote CLI hermes cmd out of exp flag @turnipdabeets

Low priority / side quests

• ⚪ MacOS support for session replay @ioannisj
• 🟢 Bunch of SDK improvements @marandaneto
  • unified settings config
  • unified pr template, issue template, etc

Plan

High priority

• Devise a plan for collecting feedback from mobile or backend SDK users @dustinbyrne
• Distributed tracing headers + remote config support @dustinbyrne
• 🟡 Capture Swift error messages from fatalError, assert, and precondition crashes @ioannisj
  • 🟡 vendor-in PLCrashReporter
• Review and finalize iOS autoresearch results on replay perf @ioannisj
• SDK design guidelines and best practices @marandaneto
• Config standardization (API key/token) @marandaneto
  • ps: only if not breaking changes (alias, etc)
• Review logs feature @turnipdabeets
• Start on Android or iOS API for logs @turnipdabeets

Low priority / side quests

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

[MichaelKutsch-ph]

Team Infra

Support hero: @danielxnj @MichaelKutsch-ph

Retro

High Prio

• 🟡 migrate more apps to The Application™
  • django stack
  • admin api
  • web and worker still outstanding, needs some work still
• 🟡 more network things (tailscale setup cleanup) @MichaelKutsch-ph - standardized ECS done, in rollout
• ✅ Cilium: own nodepools with cilium only, route percentage of traffic to it on dev - let it sit for a while and then progress @danielxnj
• ✅ improve argoCD notifications - increase transparency about appHealth and deployments @Z3r0Sum - rollout per teams for team-based notifcations, feature flags, managed warehouse...
• ⚪ use bigger node sizes to reduce overall node count / lighten EKS API load @langesven
• 🟡 VictoriaMetrics:
  • Upgrade VM to latest @MichaelKutsch-ph
  • Node optimization VM: @danielxnj
    • Move vm to own nodepools (noisy neighbour)
    • More beefy nodes?
    • Tackle noisy neighbour (guaranteed QoS)
  • 🟡 Analyze expensive queries @langesven
• 🟡 Dev env: argo test env with actual dev environment -> long term goal immutable infrastructure @Z3r0Sum - PoC with agent-based orchestration
• 🟡 smokescreen rollout @Daesgar - rollout to some services in prod, e.g. capture, temporal.... -> golden chart integration

side quest

• GitHub secret terraform provider, start using it again @-support-hero
• Alerting / Monitoring for our gh actions

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

OKR Infra

• 🚀 Make deployments great - Driver: @langesven
• 🤖 Agent-first infra services - Driver: @danielxnj
• 📈 EKS scaling - Driver: @MichaelKutsch-ph
• full list of goals

High Prio

• MSK with kafka 4 @MichaelKutsch-ph
  • dev first plus switch-over
  • identify things for better automation
  • prod-* too once everything is clear
• more network things (tailscale setup cleanup) @MichaelKutsch-ph
• smokescreen rollout @Daesgar + golden chart integration-
• migrate more apps to The Application™
  • django stack
  • admin api
  • web and worker still outstanding, needs some work still
• Cilium: starting EU rollout @danielxnj
• argo notifications: rollout to teams @Z3r0Sum
• VictoriaMetrics:
  • Upgrade VM to latest @MichaelKutsch-ph
  • Node optimization VM: @danielxnj
    • Move vm to own nodepools (noisy neighbour)
    • More beefy nodes?
    • Tackle noisy neighbour (guaranteed QoS)
  • Analyze expensive queries @langesven

side quest

• GitHub secret terraform provider, start using it again @-support-hero
• Alerting / Monitoring for our gh actions
• argoCD appset templating

[tomasfarias]

Team Batch Exports

Support hero: @tomasfarias / @rossgray

Quarter goals

• Objective 1: Unify batch exports and real-time destinations
• Objective 2: Reduce pipeline architecture technical debt
• Objective 3: Self-serve debugging

Retro

Details

High priority

✅ Display for realtime destination backfills failed/successful runs @rossgray

• Now displaying partial errors
• Now supporting an error threshold that, when reached, fails the run.
  • Currently, not configurable, but we may open this up for users to configure in the future.
• Other enhancements to logs/runs view.
  ✅ Add concurrency for workflows batch export @tomasfarias
  🟡 With load testing
  • Need to take a look at configuration.
  • Seeing connection timeout errors.
    🟡 Review metrics and alarms
• backlog_count
• Building a new grafana dashboard
• Next sprint: Resource based allocator + auto-scaler

Low priority

🟡 Add documentation/tooltip for table setup for BigQuery

• Add query to create the table

• Would be nice if this was available via the API

• Improve debugging tools
  🟡 Enable MCP integration

  • Check status, and try to get it over the line
  • Partially already completed: System tables & Integrations MCP.
    ✅ Improve backfill script

🔴 Refactor logging library

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

High priority

• Split up S3 destination into supported destinations into:

  • S3-compatible (catch-all)
  • AWS S3
  • Cloudflare R2
  • GCS

• Integration for AWS S3 with support for no-credentials authentication

• Integration for PostgreSQL

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

Low priority

• Add new snowflake inserted_at column

• Explore retryable/non-retryable in response body of CDP API

  • So that batch export can retry the request

[frankh]

Team Logs

Write more bytes somehow

Retro

Details

High priority

• 🟢 saved views @jonmcwest
• 🟢 context view @frankh @jonmcwest
• 🟡 investigate MCP improvements/suggestions from georgiy https://posthog.slack.com/archives/C08S66N93FX/p1773775752691839
• 🟢 SDK capture @jonmcwest
• ⚪ clean up old S3 bucket data @frankh
• 🟢 finish retention settings (with at-capture-time expiry) @frankh
• 🟢 retention pricing @abheek9
• 🟡 traces out for posthog internal use @frankh

Low priority / side quests]

• 🟡 services overview @jonmcwest
• ⚪ investigate ways to make PostHog be willing to pay for PostHog logs
• ⚪ server side settings/filters
• 🟡 merge in ben's metric stuff

High priority

• PII scrubbing / server side settings/filters / ingestion pipeline @DanielVisca
• traces out for posthog internal use in prod @frankh
• finish up backups @frankh
• column configurations in saved views @jonmcwest
• have real internal users for alerts @jonmcwest
• Add alerting to MCP, and get claude to create a bunch of alerts to stress test @DanielVisca

Low priority / side quests

• Get metrics MVP running in dev

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

[meikelmosby]

Team Workflows

Time Off

• Abe (24th of April until 27th)
• @havenbarnes put in your PTO if you have any :)

Retro

High priority

• Rolling out postgres-v2 to team 2 / all services @dmarchuk
• Email delivery throttle @meikelmosby
  • new email queue and consumer with dynamic routing @meikelmosby
  • SES throttle @meikelmosby
  • Redis rate limiter + new email sending consumer @meikelmosby
• Solve memory problem on hog-worker @meikelmosby
• Solve auto-scaling issues (oscillating a lot) for hog-worker @meikelmosby
• Solve problem around runaway partition lag for consumers @meikelmosby
• "Wait until event" workflow action / conversion goal @dmarchuk
• Push Notifications for android / ios @havenbarnes
  • Look into GDPR
  • Look into just storing device tokens in person props
• Roll out recurring workflows @dmarchuk
• Move all services to /apps in charts repo @meikelmosby

Low priority

• Make PostHog actions free @meikelmosby
• Implement versioning for workflows @meikelmosby
• Reminder: cleanup for cyclotron migration @havenbarnes
  • spin down legacy workers once the final delayed workflows have executed
  • clean up legacy code as well once it's no longer in hot path
• Split up grafana Dashboards into different linkable sections @meikelmosby
• support encrypted secrets for workflow inputs (Support destinations with encrypted secret inputs in schema #43579) @meikelmosby
  • Moving to encrypting in place

This Sprint

High priority

• Handover Documentation / Session around everything Email @havenbarnes @meikelmosby @dmarchuk

• Being able to create/debug Workflows through MCP @meikelmosby

  • Implement versioning for workflows @meikelmosby
  • support encrypted secrets for workflow inputs @meikelmosby

• Email delivery throttle @meikelmosby

  • new email queue and consumer with dynamic routing @meikelmosby
  • SES throttle @meikelmosby
  • Redis rate limiter + new email sending consumer @meikelmosby

• "Wait until event" workflow action / conversion goal @dmarchuk

• Push Notifications for android / ios @havenbarnes

  • Look into GDPR
  • Look into just storing device tokens in person props

• LLM workflow node @dmarchuk

Low priority

• Reminder: cleanup for cyclotron migration @havenbarnes
  • spin down legacy workers once the final delayed workflows have executed
  • clean up legacy code as well once it's no longer in hot path

[rafaeelaudibert]

Team Growth

Support hero: @rafaeelaudibert and @MattBro
Off during the sprint: Rafa's honeymoon 2nd week of the sprint, Pipa, Rio Grande do Norte, Brazil

Quarter goals

1. Make agentic sign ups first-citizen of PostHog 🟡 (@MattBro @fercgomes )
2. Allow anyone to integrate/provision an org + project in PostHog 🟡 (@rafaeelaudibert @MattBro)
3. Activation rate across all onboarding experiences should be 60%+ 🟡 (@fercgomes @MattBro @rafaeelaudibert)
4. Shape the external interface for Signals ⚪ (@fercgomes @MattBro @rafaeelaudibert )

Details

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

Plan

High priority

• Stripe Workflows @rafaeelaudibert
• Add "Customer" view inside Stripe @rafaeelaudibert
• 4 experiments geared towards the activation metric @fercgomes
• PostHog AI in the toolbar @fercgomes
• Finish Stripe Projects @MattBro
  • Depends on Stripe fixing their bugs + legal
• Wizard account creation via agentic provisioning @MattBro
• Self-serve registration @MattBro
• OAuth scope management improvements @MattBro

Low priority / side quests

• Finish surveys @fercgomes
• Improve "action" flow in the toolbar @fercgomes
• Clean up provisioning code to stop mentioning Stripe @MattBro

Retro

Details

• SPT for Stripe Projects @MattBro 🚧 (broken on Stripe-side)
• Stripe OAuth in DWH @rafaeelaudibert ✅
• Stripe Workflows @rafaeelaudibert 🚧
• Stripe Full Screen app @rafaeelaudibert ✅
• Make Agentic Provisioning generic enough to work with the wizard @MattBro ✅
• Allow the wizard to provision accounts programatically 🚧
• Clean up OAuth management page @MattBro :constr
  • Seeing the existing OAuthApplication ✅
  • Seeing existing OAuthAccessToken issued for your account, revoke them. ✅
  • Change the scopes + email asking for permissions 🚫
• VSCode extension ready to market @fercgomes @rafaeelaudibert ✅
• Keep up with all of the experiments @fercgomes @MattBro ✅ @rafaeelaudibert 🚫
• Solve/figure out what agentic onboarding is/means @fercgomes 🚧

Low priority / side quests

• Call with Cline to figure out if there's something we can do here @rafaeelaudibert ✅
• Foster Cmd K adoption with some UI changes to the sidebar @rafaeelaudibert 🚧
• Keep digging more on the Vercel integration, possibly Edge FF resolution @MattBro 🚫
• Finish survey support for toolbar @fercgomes 🚧
• Support vision for PostHog AI via the toolbar @fercgomes 🚧

What else did we do?

• Cross-sell on the sidebar is much smarter, using weighted selector @rafaeelaudibert
• Improved billing/project notice component @rafaeelaudibert
• Deployed mcpcat @rafaeelaudibert
• Adding Activated intent event for all products available during onboarding @fercgomes
• Worked on general posthog activation (ingested event + something from product, correlated to 3-month retention) @fercgomes
• POC Claude Managed Agents @MattBro
• In-person talk in NYC @MattBro

[mariusandra]

Data Team Tools

Q2 2026 objectives

Objective 1 - Build a BI experience that feels competitive and joyful (Marius)

• ⚪ New chart types, prioritizing the most-requested visualizations
• 🟡 SQL editor reliability and UX improvements
• ⚪ Better variables, including multiselect, query-backed and time-based variables (e.g. for dashboards)
• ⚪ Easier schema exploration and an alternate “no-sql” query building interface (manual controls + AI integration).
• ⚪ Ability to click in and out of rows to explore deeper.

Objective 2 - Make notebooks the default way to analyze data (Anna)

• ⚪ Python notebooks for customers
• ⚪ Core notebook UX and stability improvements
• ⚪ Better integration between notebooks, HogQL, DuckDB, and external databases
• 🟡 Initial collaboration improvements for notebooks (lock nodes if someone is editing, etc)
  • Was taken over here: https://github.com/PostHog/requests-for-comments-internal/pull/1059
• ⚪ A clearer default analysis flow centered on notebooks

Objective 3 - Build a first-class querying and DuckDB experience (George)

• ⚪ First-class DuckDB support (not treated as “just Postgres”)
• ⚪ Better query errors so failures are understandable and actionable
• ⚪ Improvements to the HogQL type system to support earlier errors
• ⚪ Calculated properties and lambdas on top of HogQL tables
• ⚪ Improved UX for connecting to databases

Retro

• Could we release direct postgres queries? @annaszell
• Gather (and fix?) notebook papercuts @annaszell
• Splitting up postgres/duckdb (not "just postgres"), quality of life improvements from this @georgemunyoro
• Calculated properties (clearing the way for it) @georgemunyoro
• SQL editor papercuts @mariusandra
• Whatever is most important for SQL/BI when I'm back one week later @mariusandra

Plan

Support rota: George then Marius

High priority

• Projections / schema editing
• SQL editor to notebooks (Filters, AI chat?)
• Notebook papercuts and vibeation @annaszell

Low priority / side quests

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

• N/A

[rorylshanks]

Team ClickHouse

AKA Team Read Fewer Bytes Please

Retro

• Setup AI Events Custer @rorylshanks 🟢
• OPS cluster in EU @rorylshanks 🟢
• Fix all dashboards to read from new ops cluster @orian 🟢
• Query of death / Upgrade cluster US @orian 🟢
• Start ALTER TABLE REWRITE PARTS to check performance @rorylshanks 🟢
• Fix backups @matt-metivier 🟢
• PoC Migrations replacement @matt-metivier 🟡
• PoC Query Gateway @matt-metivier 🔴
• CLickhouse 26.3 Upgrade @rorylshanks 🟡
• OPS Cluster instance size change to is4gen @bciaraldi 🟢
• Fix deletes Bryan @bciaraldi 🟢
• Part breaker @bciaraldi 🟢
• Alert visibility & improvements @tpgilmore 🟢
• Dev migration @tpgilmore 🟡
• AUX cluster is operating and we have first users @orian 🟢
• DataDeletionRequests and actual Dagster deletion @orian 🟢
• Batch-exports in new cluster @bciaraldi 🟡
• Improved GitHub workflows to trigger other playbook stuff and be just generally better @tpgilmore 🟢
• Retuned disk balancer @tpgilmore 🟢

High priority

• Batch-exports in new cluster @bciaraldi
• Dev migration @tpgilmore
• CLuster Upgrade 26.3 @rorylshanks
• DataDeletionRequests polishing @orian
• Look into creating team 2 cell in US @rorylshanks
• Cluster balance automation @bciaraldi
• Dynamic remote servers initial investigation @bciaraldi

Low priority / side quests]

• Add VARIANT Support to CH @rorylshanks

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

[andrewjmcgehee]

Team Data Modeling

OOO

• no one

Retro

High priority

• get materialized insight endpoint results to parity with non-materialized @sakce 👈
• remove cache age from endpoints in favor of data freshness @sakce 👈
• remove the beta label from endpoints (includes any work to get us "there") @sakce 👈
• improve error handling ui/ux surfaced to customers for models @andrewjmcgehee 👈
  • errors not displaying in EU 👈
  • show logs on syncs so customers can self-diagnose 👈
• team 2 billing models runs against duckgres completely successfully @andrewjmcgehee
• smooth transition into models backed/synced by GitHub @andrewjmcgehee 👈

Low priority

• explore & implement modeling team isolated CI / DB stuff @andrewjmcgehee
• project secret API keys @sakce 👈
• MCP for endpoints @sakce 👈
• write a persona map (check experiments for example) @andrewjmcgehee 👈

👈 = WIP

This Sprint

High priority

• remove the beta label from endpoints @sakce 🚧 chore(endpoints): remove BETA label #54808
• smooth transition into models backed/synced by GitHub @andrewjmcgehee 👈
• remove beta label for modeling if error rates below 3% @andrewjmcgehee
• allow required/optional vars on endpoint execution (filtering and grouping) @sakce 🚧
• make duckgres work properly for endpoint execution @sakce
  • todo: come up with a set of endpoints to verify this
• plan migration / deprecation of /query api @sakce
• think about skills / ai and schedule customer interviews @andrewjmcgehee
  • write a rfc following guidelines
  • write first skills PR

Low priority

• explore & implement modeling team isolated CI / DB stuff @andrewjmcgehee
• incremental matviews @andrewjmcgehee
• project secret API keys @sakce 👈
• docs for endpoints @sakce
• streamlit @sakce
• clickhouse test new versions against queries @sakce

Q2 Goals

Let's review them

[joshsny]

Team PostHog AI

Support hero: @cvolzer3, ?
Off during the sprint: @joshsny - 1.5 days 💒, @tatoalo - 1 day

Retro

Tasks

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

High priority

• 🟢 @tatoalo @VojtechBartos test and improve ux of cloud runs in posthog code - working through issues in canvas in order
• 🟡 @skoob13 @cvolzer3 migrate CI evals to sandboxes
• 🔴 @skoob13 start posthog ai migration
• 🟢 @skoob13 finish experiment with cli tools mcp, we should ship this
• 🟢 @ryans-posthog ship structured output to production
• 🔴 @ryans-posthog understand why our agent is much slower than claude code directly
• 🟢 @ryans-posthog get a better understanding of current sandbox infra
• 🟡 @ryans-posthog babysitting PRs
• 🟢 @cvolzer3 keep improving UI/UX papercuts of PostHog AI
• 🟡 @cvolzer3 expand the surface of the MCP store
• 🟢 @cvolzer3 get MCPs working in the sandbox
• 🟢 @cvolzer3 regional support for bedrock in the gateway

Side quests

• 🔴 @VojtechBartos batch exports mcp tools

Plan

High priority

• @skoob13 release single-tool mcp server that works with haiku
• @skoob13 start working on context for sandbox agents, injecting context from current UI / insight
• @skoob13 write docs for evals
• @skoob13 make sure skills docs are 😘
• @VojtechBartos @tatoalo continue working through the cloud run ux in posthog code
• @VojtechBartos @tatoalo try get to parity with local runs (terminal, bash commands from message)
• @cvolzer3 ship the MCP store, make it a great experience in PostHog Code
• @cvolzer3 support hero
• @tatoalo ship the full version of cloud attachments
• @tatoalo github repo cache + refresh api
• @tatoalo full parity for codex in cloud
• @ryans-posthog babysitting PRs
• @ryans-posthog improve how our temporal workflow manages sandbox lifecycle
• @ryans-posthog multi repo support for task runs in sandboxes
• @ryans-posthog take a look at sandbox setup ux
• @joshsny look into the modal sandbox snapshot situation
• @joshsny BAA with OpenAI / checking if we need any legal things in PostHog Code

Side quests

• @VojtechBartos batch exports mcp tools

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

[hpouillot]

Team Error Tracking

@hpouillot OOO 3 days

Retro 🟢 🔴 🟡 🚫

@cat-ph - add error tracking MCP tools 🟡 Few tools remaining
@cat-ph - stretch: agent usage instrumentation 🟢

@ablaszkiewicz - issue migration follow-up 🟢 Done, investigation on the performance. Sync has delays
@ablaszkiewicz - design recommendation center 🟢
@ablaszkiewicz - stretch: integration with feature flags / experiments 🔴

@fivestarspicy - conduct ET usage interview 🟡 Power users list collected + outreach messages ready.
@fivestarspicy - cost analysis 🚫 Delayed
@fivestarspicy - market research AI / ET 🟢 Need to create a Slack canvas with the findings

@hpouillot - architecture diagram for cost analysis 🔴
@hpouillot - breadcrumbs 🟡 UI is ready, PR for JS SDK
@hpouillot - code owners usage for assignment rules 🔴 -> Replace with cymbal metrics, symbol set sticky routing inside cymbal.

OKR

Recommendations - Setup & Priorities
Grouping - Grouping
Agent experience - MCP & Wizard
Pricing exploration - Value alignment
Issue Report - Signal integration
Search query - Migration & Performance

High priority

@hpouillot - code owners usage for assignment rules
@hpouillot - breadcrumbs web SDK
@hpouillot - architecture schema for cost analysis
@hpouillot - stretch: react and node SDK for breadcrumbs

@cat-ph - Remaining MCP Tools
@cat-ph - Skills for the wizard inside context mill

@fivestarspicy - send outreach to ET users
@fivestarspicy - pitch with Christophe for issue rate limiting

@ablaszkiewicz - issue migration sync, clickhouse union with dirty issues
@ablaszkiewicz - add recommendations to center (alerts, weekly digest, ingestion issues, cross-sell)
@ablaszkiewicz - issue rate limiting

[lucasheriques]

Team Surveys

Support hero: @lucasheriques

Quarterly goals

🟡 Goal 1: Surveys research & pricing exploration
🟡 Goal 2: Surveys MCP & skills
⚪ Goal 3: MCP analytics

Retro

• Rework survey notifications + hosted surveys so they are actually good @lucasheriques ✅
• Kick off research tasks for pricing and schedule ~10 calls with active customers @lucasheriques 🟡
• Wrap up Q2/26 goals ✅

High priority

• Work on Surveys' skills to make it simpler for people to create them without leaving PostHog AI/Claude Code/Codex @lucasheriques
• Have at least 5 calls during this sprint to discuss surveys' pricing @lucasheriques
• Look into adoption by medium and large customers @fivestarspicy

Side quests

• Finish dashboard for surveys' o11y