Monolex tools / NIIA

One memory across AI CLIs.

NIIA does not replace your AI tools. It remembers their work together — so a new session can return, find, continue, and understand.

SESSIONS

DOCS

CODE

GIT

NIIA

01 / Continuity

The tool can change. The work keeps moving.

Each AI CLI sees a session. NIIA sees the project motion around it: the conversations that shaped a decision, the documents that explain it, the code that embodies it, and the history that changed it.

YOUR AI CLIS

NEW SESSION

SESSIONS · DOCS
CODE · GIT

◈ NIIA

RECALL · SEARCH

CONTINUE · UNDERSTAND

A conceptual continuity map, not live telemetry.

02 / Four motions

Ask for the next piece of continuity.

Start with the smallest motion that answers the question. Each command returns evidence and guides the next move; none requires a frozen dashboard or a remembered internal path.

RETURN / RECALL

niia recall

Return to the current project context before deciding what to do next.

03 / Contracts

Memory without capture.

Continuity is useful only when its boundaries stay legible. NIIA keeps the official tools official, begins from local work, and crosses a network boundary only through a chosen motion.

01 / NOT A WRAPPER

Keep your tools.

Your AI CLIs, models, subscriptions, and native workflows remain theirs. NIIA joins the memory around their work rather than replacing their interfaces.

02 / ONE WORKING MEMORY

Carry the project, not the transcript.

A session is one witness. Documents, code, git, and prior conversations form the wider context that lets the next session continue responsibly.

03 / LOCAL FIRST

Network when chosen.

Recall and search begin from local project artifacts. Remote, MCP, and synchronization surfaces remain explicit actions with their own contracts.

04 / Documentation

The full operating surface stays in docs.

This page explains the role. The documentation owns command options, session providers, indexing, security, consciousness navigation, setup, and troubleshooting.

START