Insights
Insights are pieces of learning auto-extracted from completed Develop sessions. After a session finishes, Polygent reviews the conversation and surfaces a handful of insights — observations that should feed back into your team's docs, skills, commands, and process. Over time, your tooling gets smarter from your own work.
When insights are extracted
Auto-extraction triggers when:
- A Develop session transitions to Done
- The session has enough conversation to draw learnings from
Chat sessions and short sessions without enough signal are skipped.
Insight types
Each insight is categorized to help route it to the right place:
| Type | Use it for |
|---|---|
| Documentation | "We should document this gotcha" |
| Skill | "This belongs in a reusable agent skill definition" |
| Process Improvement | "Our workflow has a friction point here" |
| Performance | "We saw a perf bottleneck worth tracking" |
| User Experience | "The UX here surprised us" |
| Nice to Have | "Future improvement, not blocking" |
| Other | Catch-all |
Each workspace can choose which insight types are extracted.
Acting on insights
For every insight, you can:
- Dismiss — soft delete; useful when an insight is noise
- Create Ticket — opens the ticket creation flow with the insight as a comment, then auto-dismisses the insight
- Open Source Session — jump back to the Develop session that produced it
A New badge counts insights since each user's last visit so nothing falls through the cracks.
Filtering and search
The Insights page supports:
- Type filter
- Workspace filter
- Ticket Created filter (linked or not)
- Dismissed filter (show/hide)
- Text search — filter insights by content as you type
- Pagination — 1–100 per page
Regenerate insights
Need a fresh extraction (e.g., you've improved the prompt or want a second look)? Use Regenerate Insights on a session — Polygent spins up a temp worktree to re-run extraction without affecting the original session.
Bulk actions
Select multiple insights and bulk-delete them in one action.
Concurrency guard
Only one extraction runs per session at a time. The guard prevents duplicate insights from racing extractions.
Live updates
The Insights page and Session Insights tab update automatically — new extractions and status changes (dismiss, ticket link) appear in real time without a manual refresh.
Session Insights tab
Inside any Develop session, the Session Insights sidebar tab shows the insights generated from that session — open it to see what the AI learned without leaving the session view.
Examples
Capture a gotcha into the docs A Develop session discovers that the build fails unless an environment variable is set first. Polygent extracts a Documentation insight noting it. You click Create Ticket to turn it into a "document the build prerequisite" task — the lesson is now tracked instead of forgotten.
Promote a repeated pattern into a skill Across several sessions the agent keeps re-deriving the same data-migration steps. A Skill insight surfaces it; you create a ticket to capture those steps as a reusable agent skill so future sessions start from the known-good recipe.
Spot process friction A Process Improvement insight flags that QA keeps rejecting tickets for the same missing test. That's a signal to add a test step to your implementation workflow — surfaced automatically, no retro meeting required.
Permissions
| Permission | Capability |
|---|---|
insights.view | View insights |
insights.manage | Dismiss, regenerate, bulk-delete |
Why insights matter
The bet is simple: the team that learns from its own AI work compounds faster than the team that doesn't. Insights surface those learnings automatically — no separate retro meeting required.