Sessions and logs

Sessions are the readable ledger of past sittings. The list page shows a derived title from the first prompt, project/cwd, prompt count, tool count, and skill signal count.

Session detail

Opening a session should feel immediate. Kanade now loads the session aggregate and first 200 timeline events first, then hydrates slower details in the background:

• lesson detection,
• summary-context extraction,
• local LM Studio/Ollama narration.

If the local voice runtime is offline or slow, the deterministic placeholder chronicle remains visible and the page explains the fallback.

Logs tab

The right-rail Logs tab is scoped to the active lane. It shows structured events rather than raw terminal output:

• timestamp,
• event type,
• tool name when present,
• expandable prompt/input/output/raw envelope detail.

The raw PTY log is still available under the diagnostic details block, with ANSI escape codes stripped for readability. Use raw PTY only when diagnosing terminal rendering or CLI behavior.

The Live Floor page keeps only the newest 80 events in the visible stream so the browser stays light. That is not a retention limit: events are still inserted into the local SQLite database, and raw lane logs remain under Kanade’s local data directory.

Performance guard

The daemon supports event_limit=0 for metadata-only session reads. This keeps right-rail refreshes and summary-context calls from pulling event bodies when they do not need them.