Monolex Estate
Tools
One entry point per tool. Reference lives in the docs; this is the map.
37 core tools shown · five jobs
Tool estate
Find the tool by the work in front of you. This core map starts with the public harness and adds the shipped Monoterm TUI; each tool keeps its full command contract in its own initiate/ reference and documentation.
niia — open guideContinuity across AI CLIs, project memory, search, and consciousness.
monomento — open guideMemory-document search and section-level retrieval.
monoflow — open guideTemporal flow across code, commits, documents, and sessions.
monographCurated Books of engineering knowledge and fix shapes.
monobrainMemory and instruction synthesis backed by monomento.
monogram — open guideFuzzy code search, call graphs, and coupling audits.
monogram-semanticsClean-room semantic IR for code-understanding evidence.
monogram-languageCorpus-derived language roles for search scoring.
monogram-logosA review lens over the monogram semantic store.
monogit — open guideGit structure cache for branches, commits, and diffs.
monocssCSS architecture audit over static and runtime proof.
monobench — open guideMeasures whether a code tool helps an agent find root causes.
work-wiki — open guideKnowledge joins across conversations, actions, and artifacts.
monocli — open guideBrowse, filter, and export AI CLI sessions.
monometer — open guideMeasure local token, cache, cost, activity, and quota data.
monolog — open guideInspect PTY activity logs, timelines, file events, and search.
monofetch — open guideWeb pages to Markdown to searchable memory.
monoapi — open guideOpenAPI and Swagger specifications to memory.
monowiki — open guideWikipedia articles to indexed Markdown.
monorss — open guideRSS and Atom feeds to searchable memory.
monodoc — open guideDocuments, books, images, and audio to Markdown.
monosystemCross-machine transport, estate auth, and remote presence.
vpncli — open guideP2P shell, copy, and tunnels between named machines.
monoptyLocal headless PTY control for interactive agent sessions.
monosurf — open guideRust-native browser automation over Chrome DevTools Protocol.
kernel-cliObserve and drive the local OS through native evidence.
openclis — open guideThe registry client for installing, updating, and discovery.
openclis-vaultStable keychain credential storage for the tool estate.
monopassPasskeys and credentials with envelope encryption.
monoguardFile defense with timestamped backups on change.
monogrid — open guideUnicode-aware ASCII box alignment checking.
monotreeAn interactive, project-aware file tree TUI.
monoterm — open guideThe Monolex terminal experience inside a terminal TUI.
monolex-headlessThe Monolex terminal engine as a headless server.
monolex-pty-daemonThe pseudo-terminal daemon beneath every session.
monolex-niia-watcherFile events feeding code, memory, and work indexes.
codexmono — open guideThe 600-unit Brick: CJK, Nerd, and Hermes in one grid.
No tool matches this query. Try a job such as memory, browser, or terminal.
The full registry — including provider-specific companions — stays in OpenCLIs; command contracts remain in the docs. The philosophy-to-machine origin of this family lives in the Monobrain harness.
Architecture
┌───────────────────────────────────────────────────────────────────┐
│ LAYER STACK │
├───────────────────────────────────────────────────────────────────┤
│ │
│ niia consciousness + orchestration + unified search │
│ ↕ │
│ work-wiki knowledge layer (sessions, convergence, funnel) │
│ ↕ │
│ monoflow temporal flow + cross-DB analysis + quality delta │
│ ↕ │
│ monogram monogit monomento │
│ (code) (git) (docs) │
│ │
│ Each layer reads from everything below. │
│ Each layer refreshes everything below on reindex. │
│ │
├───────────────────────────────────────────────────────────────────┤
│ STANDALONE TOOLS │
├───────────────────────────────────────────────────────────────────┤
│ │
│ monogrid Box alignment (Unicode width + 9 rules) │
│ monoterm AI terminal in your terminal (sidebar, tabs, IME) │
│ │
└───────────────────────────────────────────────────────────────────┘
The memory spine of this stack is the inner three: monomento stores, monoflow connects, niia recalls — nested by literal crate dependency, with recall by far the largest layer. Storage is cheap; recall is what memory is. Why memory had to take that shape is the argument of Monobrain: The Unnamed Conversation.
NIIA — Consciousness + Orchestration
NIIA recalls context, searches project knowledge, carries continuity across AI CLIs, and opens the lower tool stack through one entry point.
niia recall
niia search "session gateway"
niia session search "what we decided"
niia consciousness "simplicity chaos"
It does not replace the AI tools you already use. It remembers their work together, beginning with local artifacts and reaching remote, MCP, or synchronization surfaces only when those motions are explicitly chosen.
Layer Tools
| Layer | Tool | Purpose |
|---|---|---|
| Top | niia | Memory continuity, consciousness, orchestration, unified search |
| Knowledge | work-wiki | Sessions, convergence funnel, knowledge DB |
| Analysis | monoflow | Cross-DB analysis, quality delta, layer chaos |
| Code | monogram | Code search + call chain tracing |
| Git | monogit | Git structure + commit symbol tracking |
| Docs | monomento | Document search + reference graphs |
Standalone Tools
| Tool | Purpose |
|---|---|
| monogrid | ASCII box alignment checker (Unicode width + 9 rules) |
| monoterm | AI terminal in your terminal (sidebar, tabs, IME) |
| monobench | Root-cause benchmark for code-intelligence tools — does monogram (or any tool) actually help find real bugs? |
The full mono* family reference lives in the docs: AI-CLIs overview →