Agentlytics Session Analysis

Purpose

Use this after Agentlytics setup is complete to audit sessions: prompt quality, context quality, trajectory efficiency, verification rigor, outcome, and collaboration habits.

REQUIRED SETUP: Before analysis, use agentlytics-setup or confirm it already succeeded in the current workflow. The database must be freshly joined with the selected Agentlytics --join localhost:4638 --username <username> command, and MCP tools should be visible or the user must have approved the documented fallback path.

If setup is missing or stale, stop analysis and run agentlytics-setup first.

MCP Collection Workflow

1. Discover candidate sessions.

   • Known username: get_user_activity(username, limit=50); increase limit if the requested period is broad.
   • Useful queries: project names, repo folder names, ticket keys, distinctive task terms.

2. Filter by the requested date range.

   • Keep sessions whose lastUpdated is inside the range.
   • Preserve source/project diversity; do not over-sample one repo when several repos appear.