Skip to main content

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.

CategoryTypical use
DocumentationRecord a prerequisite, convention, or operational issue.
SkillCapture reusable agent guidance.
Process ImprovementChange a team workflow or handoff.
PerformanceTrack a performance concern.
User ExperienceRecord a usability issue.
Nice to HavePreserve a non-blocking improvement.
TestsAdd missing regression coverage.
OtherClassify 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.

PermissionCapability
View InsightsView accessible insights, filters, counts, and source sessions the user can access.
Manage InsightsDismiss 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.

SymptomCheck
No insight appearsConfirm 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 failsSearch the system logs for the session. Fix model authentication, quota, or connectivity for the Insight Extractor model, then use Regenerate.
Regenerate is unavailableUse the session's Insights tab; confirm Manage Insights and access to the source workspace and session.
Unwanted categories appearSelect the intended categories under Guidelines → Insights → Extraction Types; an empty selection extracts all.
An expected workspace is missingAdd the user to the workspace or use an administrator account.
A ticket cannot be createdConfirm 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.