Insights
Insights turn findings from completed Develop sessions into workspace-scoped suggestions that teams can review, dismiss, or convert into tickets.
Generation
Insight generation runs after an eligible Develop session reaches Done, provided Insights is enabled under Settings → Insights. Chat sessions and sessions without enough useful conversation may produce no insights. Each workspace controls which categories may be extracted under its insight prompt settings. If no categories are selected, extraction still runs but should produce no categorized suggestions.
| Category | Typical use |
|---|---|
| Documentation | Record a prerequisite, convention, or operational issue. |
| Skill | Capture reusable agent guidance. |
| Process Improvement | Change a team workflow or handoff. |
| Performance | Track a performance concern. |
| User Experience | Record a usability issue. |
| Nice to Have | Preserve a non-blocking improvement. |
| Tests | Add missing regression coverage. |
| Other | Classify a finding that does not fit another category. |
Generation is asynchronous. The Insights page and the session's Session Insights tab update automatically when results become available.
Review and action
The Insights page is the workspace-level review queue for generated findings.
- Create Ticket opens ticket creation with the insight attached, links the resulting ticket, and dismisses the insight from the active queue.
- Dismiss hides an irrelevant or duplicate insight without deleting its source session.
- Open Source Session returns to the conversation that produced the finding.
- Regenerate Insights reruns generation for a completed eligible session. Existing insights are not removed automatically.
- Bulk dismissal applies the same soft-dismiss behavior to the selected rows and requires confirmation.
Filter by type, workspace, linked-ticket state, dismissed state, or text. The page supports paginated results of up to 100 rows per page.
Access control
Insights require both workspace access and the relevant role permission.
| Permission | Capability |
|---|---|
| View Insights | View accessible insights, filters, counts, and source sessions the user can access. |
| Manage Insights | Dismiss or regenerate insights and link them to tickets. |
Creating the resulting ticket also requires the normal ticket-management access for that workspace. Administrators can access all workspaces.
Operations and troubleshooting
Insight generation depends on the session's selected model and valid model credentials.
| Symptom | Check |
|---|---|
| No insight appears | Confirm Insights is enabled globally, the session is a Develop session in Done state, the workspace enables at least one category, and the conversation contains substantive user and agent messages. |
| Generation fails | Check the session messages and system logs for the reported failure stage. Model authentication, quota, connectivity, and response errors require model configuration checks. A Windows launcher connection or command start error identifies the failed launch stage; check CLI installation or service-account PATH only when the error explicitly reports that the executable was not found. Then regenerate. |
| Regenerate is unavailable | Confirm the user has Manage Insights and access to the source workspace and session. |
| An expected workspace is missing | Add the user to the workspace or use an administrator account. |
| A ticket cannot be created | Confirm ticket management access and that the source workspace is still available. |
Insights can contain repository and conversation content. Apply the same access controls and retention expectations used for sessions and tickets.