init feature selection: pre-select features based on actual project usage
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Summary
The sentry init feature selection step pre-selects all features (Crons, AI Monitoring, Profiling, etc.) regardless of whether the project actually uses them. The wizard should analyze the project first and only pre-select features that are relevant to the detected stack.
Current behavior
All features are toggled on by default in the multi-select prompt, including Crons and AI Monitoring, even when the project has no scheduled jobs or AI model calls.
Gap
Pre-selecting irrelevant features adds noise to the generated config (unnecessary sample rates, DSN registrations) and gives the wrong impression that these features apply to every project. Users who don't notice the defaults end up with config for features they don't use.
Options
- Static heuristics: during the platform/framework detection step, check for signals like cron libraries (node-cron, APScheduler, Celery beat), AI SDKs (openai, anthropic, langchain), and only pre-select matching features
- AI analysis: since the wizard already uses AI to analyze the project, extend that pass to emit a features manifest that drives pre-selection
- Default none: ship with all features off by default and let users opt in
Recommendation
Use the existing AI analysis pass (or static heuristics as fallback) to drive pre-selection. Default to off for anything with no detected signal.
Action taken on behalf of Sergiy Dybskiy.
- Dominant language
- TypeScript
- Stars
- 121
- Forks
- 14
- Avg merge
- 22h 3m
- Merged PRs (30d)
- 94
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
bug jared
-
jared
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·