Monolex tools / Observe
See the work.
A conversation, a usage ledger, and a terminal trace are three different witnesses. Choose the one that can answer the question you actually have.
Three records. One point of inspection.
Choose a lens
Begin with the question.
Observation gets noisy when one record is asked to explain everything. Sessions preserve dialogue. Usage records measure consumption and activity. PTY logs preserve terminal operations. Pick one before searching.
monocli list --limit 10
List recent conversations across the supported AI CLI stores, then open the session that contains the decision.
Three witnesses
Each record tells a different truth.
These tools meet at inspection, not storage. Their outputs remain separate so a transcript cannot masquerade as a usage ledger and a usage estimate cannot masquerade as an invoice.
SESSIONS / MONOCLI
What was said?
List, inspect, read, and export conversations from the AI CLIs already on your machine through one session interface. Use it when the missing evidence is the dialogue itself.
monocli list --limit 10USAGE / MONOMETER
What was used?
Check the local measurement stack, then inspect token, cost-equivalent, activity, model, block, or available quota views. Usage and provider quota remain distinct records.
monometer healthTERMINAL / MONOLOG
What happened?
Read recent PTY activity, search operations, group sessions, find touched files, or inspect the activity timeline. It records operations; it does not replay the terminal.
monolog recent 20Open Monolog reference →Boundaries
Evidence is useful when it stays named.
The page does not merge the three datasets or promise more certainty than each source can provide.
MONOCLI ≠ MEMORY
A session is a witness.
Read what was said, then hand the useful decision to the project continuity layer. A transcript alone is not the whole project.
MONOMETER ≠ INVOICE
Measurement is not billing proof.
Local token and cost-equivalent records describe activity. Provider quota and subscription state come from separate, availability-dependent sources.
MONOLOG ≠ REPLAY
An operation is not a screen recording.
The log answers who did what, where, and when. It does not reconstruct every visual state of the terminal.
Carry forward
Observation finds the evidence. NIIA carries the context.
Once you find the conversation, usage pattern, or terminal event that matters, return it to the wider project motion instead of leaving it in an isolated log.
Continue with project memory.
NIIA joins sessions with documents, code, and git so the next AI CLI can continue from evidence rather than a vague recollection.
Need the whole tool map?
Return to the searchable catalog and choose another job without turning this page into a command encyclopedia.