Native agent history

Find what you tried before installing Velora.

Velora keeps its own durable run journal. It also reads supported native Claude Code and Codex session transcripts when you explicitly choose Read local agent history in Code → Sessions. This includes work started outside Velora in terminals such as cmux.

Search recorded work

Search a prompt, error, approach or command. Filter by repository path and agent, then expand a session to inspect recorded prompts, answers, tool calls and results. Native IDs, source files and timestamps remain visible. An agent claiming that tests passed is not independent verification.

Use Refresh files after external sessions change. Clear local index discards the in-memory index without deleting vendor files. No history is uploaded, shared with teammates, sent to a model or used to resume work automatically.

CLI

velora history --local-history --repo /path/to/repository --search "database locked"

Use --provider claude or --provider codex, --refresh, and --clear. JSON pages include nextOffset and generation for pagination.

Supported sources and limits

Claude Code session JSONL files under its projects directory and Codex sessions and archived_sessions are supported, including configured CLAUDE_CONFIG_DIR and CODEX_HOME locations. Claude's prompt-only history index is not imported. Unknown schemas, unreadable files and partial transcripts are reported instead of treated as successful empty runs.

Search uses bounded excerpts. Each refresh is limited to 20,000 files, 256 MB of reads and 15 seconds; files are limited to 16 MB. The memory-only index is capped at 128 MB of transcript text. Large events and sessions are truncated with visible labels. This does not claim support for every vendor format or a complete external activity monitor.