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 a Develop session reaches Done, when Enable Insights is on under Management → System → Insights (on by default). It uses the Insight Extractor model configured there. Chat sessions, sessions from insight-created tickets, and sessions without enough substantive conversation produce no insights. Each workspace chooses which categories to extract under Guidelines → Insights → Extraction Types; selecting no category currently extracts all categories, not none.
| 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 and links the resulting ticket; the insight moves to the Ticket Created filter.
- Create Tickets (bulk) creates a Task ticket for each selected insight.
- Dismiss hides an irrelevant or duplicate insight without deleting its source session. Bulk dismissal requires confirmation.
- Open Session / Open Ticket return to the source conversation or the linked ticket.
- Regenerate on a session's Insights sidebar tab reruns generation for that completed session. Existing insights are not removed.
Open Developer Tools → Insights. Filter by type, workspace, Ticket Created, Dismissed, or text; results are paginated (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 Insight Extractor model and its credentials; failures are recorded in the system logs, not in the session.
| Symptom | Check |
|---|---|
| No insight appears | Confirm Enable Insights is on, the session is a Develop session in Done state, it did not come from an insight-created ticket, and the conversation contains substantive user and agent messages. |
| Generation fails | Search the system logs for the session. Fix model authentication, quota, or connectivity for the Insight Extractor model, then use Regenerate. |
| Regenerate is unavailable | Use the session's Insights tab; confirm Manage Insights and access to the source workspace and session. |
| Unwanted categories appear | Select the intended categories under Guidelines → Insights → Extraction Types; an empty selection extracts all. |
| 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.