Sessions

A session is one continuous conversation with your agent host. TokenPilot tracks per-session metrics and applies context management within each session.

The CLI report and session-pinning examples below apply to OpenClaw, Codex, Claude Code, pi, and OpenCode. In DeepSeek Harness, open the relevant session and run /tokenpilot-status to inspect estimator, scheduling, application, and deferral state.

Viewing Session Info

# Current session summary
lightrsi report

# Specific session
lightrsi codex session <session-id> report
lightrsi claude-code session <session-id> report

Pinning a Session

Pin a session to make it the default for subsequent commands:

lightrsi use codex session <session-id>
lightrsi use claude-code session <session-id>

Now lightrsi report and lightrsi visual will use the pinned session.

Session Reports

The report shows metrics accumulated over the session:

• Total input tokens
• Cache read vs. cache miss
• Output tokens
• Estimated cost

Next

• Reports and Visuals — understanding reports
• CLI Reference — session commands
• Reports and Visuals — browser dashboard