Concepts

Session info

Everything lazyagent surfaces per session and where each field comes from.

lazyagent computes a single Session record per conversation, regardless of which agent produced it. The record is shown in the detail panel (TUI and GUI), returned by /api/sessions/{id}, and reused by session-oriented commands such as lazyagent sessions, prune, compact, and search.

The fields

FieldSource
Session IDJSONL / SQLite (per agent)
Working directoryJSONL / SQLite
Git branchJSONL / SQLite
Agent versionJSONL
Model usedJSONL
Is git worktreegit rev-parse at discovery time
Main repo path (if worktree)git worktree
Message count (user / assistant)JSONL / SQLite
Token usage & estimated costJSONL + per-model pricing, when the agent records token counters
Activity sparkline (last N minutes)JSONL entry timestamps
Last file writtenTool call inspection
Recent conversation (last 5 messages)JSONL / SQLite
Last 20 tools usedJSONL / SQLite
Last activity timestampJSONL / SQLite
Custom session name~/.config/lazyagent/session-names.json
Session source (CLI / Desktop)Claude Desktop metadata
Desktop session titleClaude Desktop metadata
Permission mode (Desktop)Claude Desktop metadata
Remote control URLJSONL (Claude bridge_status entries)
Normal and YOLO resume commandsComputed per agent when available

Custom names

Every session can be renamed (r in TUI or GUI, PUT /api/sessions/{id}/name in the API). Names persist to ~/.config/lazyagent/session-names.json and survive restarts. An empty name resets to the default (agent-assigned) label.

Resume command

Lazyagent builds both normal and YOLO resume commands when the agent exposes a distinct permissive mode:

AgentNormalYOLO
Claude Codeclaude --resume <id>claude --dangerously-skip-permissions --resume <id>
Codex CLIcodex resume <id>codex --yolo resume <id>
Ampamp threads continue <id>amp --dangerously-allow-all threads continue <id>
pipi --session <id>Not available
OpenCodeopencode -s <id>opencode --auto -s <id>
Kilokilo --session=<id>kilo --auto --session=<id>
Cursorcursor-agent --resume="<id>"cursor-agent --force --resume="<id>"
Grokgrok --resume '<id>'grok --yolo --resume '<id>'
Kimi Codekimi --resume <id>kimi --yolo --resume <id>

YOLO is lazyagent’s common label for the most permissive mode exposed by each CLI. The exact guarantees are tool-specific: flags such as --auto and --force do not necessarily have the same approval or sandbox semantics as a full permission bypass, and configured deny rules may still apply. pi has no separate toggle, so lazyagent exposes only its normal resume command.

In the TUI, c copies the normal command and C copies the YOLO command. The GUI exposes open and copy actions for both variants. The API returns resume_command and resume_command_yolo in the session detail.

Cost estimation

Cost is derived from the token counters already present in the transcript, multiplied by the per-model price list baked into lazyagent. Supported model families include Claude (Opus, Sonnet, Haiku), GPT (4o, 4.1, o1, o3), and Gemini. Unknown models show tokens but no cost. Grok sessions show no per-session token or cost figures because Grok’s local transcript data does not expose an input/output/cache token split.

Costs are estimates — the authoritative number is always your provider’s billing console.