Roadmap
Goals
Q2 2026 Objectives
Recommendations - Setup & Priorities - (Driver: Aleksander Błaszkiewicz)
Right now we are mostly visual and reactive, but we could surface some important actions that need to be taken (by users or agents) to get the best out of Error Tracking. What we'll ship:
- Detect project misconfiguration
- Surface spiking issues
- Detect high-priority issues
- Recommend assignment and suppression rules
Grouping - Grouping - (Driver: Hugues Pouillot)
Why use boring deterministic grouping when you can have a better probabilistic one with shiny visualizations? What we'll ship:
- Improve stacktrace parsing for JS SDKs
- Improve grouping using stacktrace embeddings
- Add clusters visualization
Agent experience - MCP & Wizard - (Driver: Catalin Irimie)
Buttons and inputs are so Q1 2026, what we want is Skills and Tools for our cute little agents. What we'll ship:
- Expose the full Error Tracking operation set through MCP
- Expose new Skills to set up and interact with Error Tracking from one prompt with AI anywhere
Pricing exploration - Value alignment - (Driver: Cory Slater)
Your agent You shipped a tiny bug that made your bill explode? Well, until you can take from their pocket money, we will explore new pricing models for the new era ahead of us.
What we'll ship:
- Explore new pricing models that better align with the insight you get.
- What agent-based workflows imply in terms of pricing models?
Issue Report - Signal integration - (Driver: Hugues Pouillot)
Issues are analyzed and prioritized by the signal team, how can we get the most of those tokens? What we'll ship:
- Enrich issues with reports generated by the signal team
- Allow users to autofix issues using sandbox mode
Search query - Migration & Performance - (Driver: Aleksander Błaszkiewicz)
Migrate issue to clickhouse to avoid dual query order problems and start optimizing search performance. What we'll ship:
- Migrate issues and fingerprint overrides to clickhouse
- Explore optimization options (sampling, pre-computation, cache warm-up)
Handbook
What the Error Tracking team does
- Exception capturing (autocapture, manual)
- Exception querying
- Exception management (assigning, merging, alerting)
How to work with the Error Tracking team
Reach out in our Slack channel #team-error-tracking
Who are we building for?
Primary (building for, churn indicates product failure)
Product & Growth Engineers
- JTBD: Get notified when new issues happen / escalate, identify impact, have context to fix
- Why prioritize: champion persona who adopts ET
Founders
- JTBD: Same as above but specifically want to know when early users face any exception
- Why prioritize: YC/high-potential, core to get-in-first strategy at product-led startups shipping multiple times/week
Who we somewhat support (product will fully support them in time but we’re ok with churn in the short term)
DevOps/SRE Engineer
- JTBD: Cost control, release tracking, cross-service correlation, custom grouping for high-volume services
- Why: we will ideally support these use cases but do not have full coverage right now (missing releases UI, automatic request ID instrumentation, complex snoozing / alerting rules based on thresholds, logs integration)
AI/ML Engineer (emerging)
- JTBD: Track LLM quality degradation, hallucinations, cost explosions (non-traditional "exceptions")
- Why: might churn to specialized tools while we work on integrating deeper with LLMA
Support Engineer
- JTBD: Quick context on user-reported errors to triage severity, share details with product engineers
- Why: not a regular user but happy to support requirements that are a subset of the primary persona
Who we’re not building for (do not expect the product to be of great value)
Product Managers
- JTBD: Understand which bugs block conversion/revenue, help prioritize by business impact
Vibe coders
- JTBD: Be informed of improvement to metrics from automatic bug fixes
- Why: Engineers in our ICP companies (high-growth startups, and those who could become that) generally do not vibe code their products