"Feature Request: Agent Session Tracking for Multi-Tool Operations"
Resolved 💬 3 comments Opened Aug 4, 2025 by UncTed Closed Aug 15, 2025
## Problem
When agents use multiple tools, telemetry shows them as "idle" between tool calls, making it impossible to:
- Track total agent session duration
- Calculate aggregate token usage for the entire agent task
- Know when an agent is truly complete vs waiting between tools
## Current Behavior
Agent Start → Tool 1 → [Shows IDLE] → Tool 2 → [Shows IDLE] → Agent Complete
Each tool fires separate completion events with no session correlation.
## Requested Feature
Add agent session tracking that:
- Assigns a unique session_id when an agent starts
- Maintains this ID across all tool calls within that agent's task
- Emits an "agent_complete" event with total metrics:
- Total tokens used (sum of all tools)
- Total duration
- Tool count
- Agent name/type
## Use Case
Building dashboards to monitor agent performance and resource usage in multi-agent systems and to better implement optimization for token usage per agent.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗