Session logs

Session Logs

AgentUse automatically tracks every agent execution with detailed logs, providing full visibility into what happened during each run.

Quick Start

# List recent sessions
agentuse sessions

# View session details (partial ID match supported)
agentuse sessions show 01JFN8

# Show full tool inputs/outputs
agentuse sessions show 01JFN8 --full

# Export as JSON
agentuse sessions show 01JFN8 --json

What Gets Tracked

Each session captures:

Category	Data
Session	Agent name, model, MCP servers, project context, timestamps
Messages	User prompts, system prompts, token usage, cost, duration
Parts	Text output, tool calls, reasoning, step boundaries
Tools	Tool name, input, output, duration, errors

CLI Reference

List Sessions

agentuse sessions list [options]
agentuse sessions ls [options]

Options:

• -s, --subagents - Include subagent sessions
• -n, --limit <n> - Limit results (default: 10)
• -j, --json - Output as JSON
• --all - Show sessions across all projects
• --project [path] - Show sessions for a project path; defaults to the current project

Example output:

Sessions for current project: /Users/you/project

ID            STATUS     AGENT                 DATE
--------------------------------------------------
01JFN8K3M2P1  done       daily-reporter        Today 14:32
01JFN7XYZAB   suspended  seo-analyzer          Yesterday 09:15
01JFN6DEFGH   fail       code-reviewer         Mon 16:45

Session state is stored globally and partitioned by project. The CLI defaults to the current project; use agentuse sessions list --all when you are looking for a session but are not sure which project owns it.

Show Session Details

agentuse sessions show <id> [options]

Options:

• -f, --full - Show complete tool input/output (not truncated)
• -j, --json - Output as JSON
• --project [path] - Search a project path; defaults to the current project
• --all-search - Search all projects if not found in the selected project

Example output:

════════════════════════════════════════════════════════════
SESSION: 01JFN8K3M2P1NRXZW4Y5V6Q7B8
════════════════════════════════════════════════════════════

Agent:       daily-reporter
Description: Generate daily motivation quotes
Model:       anthropic:claude-sonnet-4-6
Started:     12/21/2025, 2:32:45 PM
MCP Servers: postgres

Project:     /Users/you/project
Working Dir: /Users/you/project

────────────────────────────────────────────────────────────
Task: Generate a daily motivation quote with an interesting fact
Tokens: 1523 (in: 892, out: 631)  Duration: 3.2s
Parts: text: 2, tool: 3

Output:
Here's today's motivation quote...

─── ✓ Postgres{query} (SELECT * FROM quotes...) 0.8s ────────
{"rows": [{"id": 1, "quote": "..."}]}
────────────────────────────────────────────────────────────

Generated your daily quote successfully!

Show Storage Path

agentuse sessions path
agentuse sessions path --project ../other-project

Shows where session data is stored for the current project.

Subagent Sessions

Use --subagents to include subagent sessions in listings:

agentuse sessions list --subagents

Use Cases

Debugging Failed Runs

# Find recent failed session
agentuse sessions list | grep -i fail

# View full details with complete tool outputs
agentuse sessions show 01JFN8 --full

Cost Tracking

# Export sessions as JSON for analysis
agentuse sessions list --json > sessions.json

# Query costs with jq
cat sessions.json | jq '.[].cost'

Audit Logging

Session logs provide a complete audit trail:

• What prompts were sent
• Which tools were called with what inputs
• What outputs were generated
• Token usage and costs
• Error details and stack traces

Related

• Session Storage Reference - Directory structure and data schemas
• Environment Variables - Configure storage location with XDG_DATA_HOME