Skip to main content

​
Session Logs

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

​
Quick Start

​
What Gets Tracked

Each session captures:

​
CLI Reference

​
List Sessions

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
  • --no-mock - Hide mock/test runs. The CLI lists them by default, marked · mock
Example output:
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

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:

​
Show Storage Path

Shows where session data is stored for the current project.

​
Subagent Sessions

Use --subagents to include subagent sessions in listings:

​
Use Cases

​
Debugging Failed Runs

​
Cost Tracking

​
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

​
Browse Sessions in the Browser

When agentuse serve is running, the same sessions are browsable as web pages:
  • /sessions lists every run, newest first. Filter the list with ?agent=<id>, ?status=running|suspended|completed|error|incomplete (incomplete matches only runs blocked on a person; other incomplete runs are listed under error), ?trigger=scheduled|manual|slack|api, ?days=<n|all>, and ?mock=include|only. Mock/test runs are hidden by default; include adds them to the list and only shows nothing else. A mock session’s detail page is always reachable by id, filter or not.
  • /sessions/<id> is the per-session page: the full run log, and when the session is suspended on an approval gate, the approve / reject / comment and resume controls.

​
Internal agent-revision sessions

A completed, failed, or approval-paused run can start a reviewable agent revision. The original session remains the launch point and durable history, with a link to each revision. An agent that has never run can instead start from its detail page and use the current agent file as evidence. The revision session links back to its origin when one exists and holds the diagnosis, source proposal or no-change result, reviewer feedback, apply decision, and restore action. The Sessions list and feed label these AgentUse-owned jobs as internal revision, group them under Internal revisions, and name them Revising agent. They are distinct from delegated subagents and automated Judge sessions. See Agent Revisions for the full review and write-safety workflow. For delegated runs, the parent timeline also surfaces important work from nested descendants. Reviewer comments appear as timestamped feedback; a child working on that feedback is labeled revising, and its next gate is labeled awaiting-approval. Judge sessions are identified as automated pre-review attempts so they are not mistaken for human decisions. The /agents page opens each agent’s detail hub, where you can inspect source, recent runs and revisions, and start a run. Schedule rows also link to the agent detail hub; last-run badges still link to the matching session page. When the model streams its reasoning, it renders inline in the log as dimmed “Reasoning” entries (the model’s “why”, subordinate to the visible answer it precedes). This is on by default for reasoning-capable OpenAI models; for Claude it requires opting into extended thinking. See model configuration for the openai.reasoningSummary and anthropic.thinking options.
If a session is stuck at running long after its process is gone, usually after a crashed daemon or a killed container, settle it with agentuse sessions reconcile. Runs that are still executing are never touched. On an exposed host these pages require the API key, or a per-session token on the session page link. See Approval Gates.