feat(insights): analyze a single session - #997
Merged
Merged
Conversation
roborev: Combined Review (
|
mariusvniekerk
approved these changes
Jul 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The insights generator can analyze agent activity, but the request path is date-window scoped, so starting from a single session still asks the backend for a sessions-list prompt. That makes the top-bar workflow in #445 impossible without manually narrowing dates and still getting surrounding sessions in the prompt.
This adds a session-scoped path to the existing insights generation flow instead of creating a parallel endpoint. The session breadcrumb starts an
agent_analysistask with the current session id, the server validates that session scope only applies to agent analysis, and the prompt builder switches to a single-session branch that reads the session, messages, timing, and usage through the existing store interface.The storage shape stays unchanged for this pass. The PR keeps the generated insight pipeline, SSE stream, task handling, and ordinary date-range analysis intact, and limits the new behavior to the missing session scope.
Closes #445