monolog 0.2.2, OpenCLIs build
2026-06-30-035910. The executing binary, registry, and public CDN metadata
agree on this release.
See the work across three lenses
Use Monocli for conversations, Monometer for usage, and Monolog for terminal activity; this page remains the Monolog command reference.
Quick Start
What Gets Recorded
Every time an AI CLI (Claude Code, Codex, Gemini) runs a tool inside Monolex, the operation is captured.Search Paths
Sessions
Hot Files
Timeline
Statistics
Gate Configuration
gate and ops print configured rows only, so a successful empty result means no custom rows are currently registered rather than a command failure.
Sources
Monolog identifies where each activity came from:Complete Command Reference
An unknown first argument is treated as a search query, but only that one token
is used; use
monolog search "multiple words" for a multi-word query. A missing
query after search or find exits quietly.
index reads parsed_activities from the shared PTY database and writes
documents named pty-activity/<id> to
Monolex/protocols/niia/database/monolog-memo.db beneath the platform data
directory. find reads that derived database. Direct search, session, file,
timeline, and stats views remain backed by the PTY activity database.
Monolog queries persisted evidence; it does not drive a terminal and cannot
reconstruct events that were never recorded. A healthy logger now and a
complete historical range are separate claims.