Projects
A project represents a single game or application. All reports, events, environments, integrations, and tokens belong to a project.
Creating a project
Navigate to Projects and click New Project.
| Field | Required | Description |
|---|---|---|
| Name | Yes | Display name (3-120 characters) |
| Slug | Yes | URL-safe identifier — lowercase letters, numbers, hyphens only (3-120 chars). Must match pattern ^[a-z0-9]+(?:-[a-z0-9]+)*$ |
| Description | No | Free-text description (up to 1000 characters) |
| AI Summary | No | Enable automatic AI-generated summaries and reproduction steps for bug reports. Default: enabled |
| AI Deduplication | No | Enable embedding-based deduplication that collapses identical reports. Default: disabled |
AI features
AI Summary
When enabled, every incoming bug report is processed by AI to generate:
- A summary of the issue based on the title, description, context, and attached events
- Reproduction steps — a step-by-step list to reproduce the bug
- A confidence score indicating how reliable the AI analysis is
You can regenerate the AI summary for any report from the report detail page.
AI Deduplication
When enabled, the backend computes an embedding for each report and compares it against existing reports. If a match is found above the similarity threshold, the new report is marked as a duplicate and linked to the root report. The dashboard shows an occurrence count on the root report.
Editing a project
Open a project and go to the Settings tab. You can update the name, description, and AI feature flags. The slug cannot be changed after creation.
Deleting a project
Delete a project from its Settings tab. This permanently removes all associated data including reports, events, environments, integrations, and tokens.
Dashboard
Each project has a dashboard showing:
- Metrics — critical reports count, new reports today, sessions today, latest build version
- Recent reports — the most recent bug reports with severity, status, and environment tags
- Activity by environment — report counts broken down by environment
- Reports by severity — distribution across low, medium, high, critical
- Reports by build — which build versions are generating the most reports