How It Works

An agent maps your material. What it leaves behind is the memory.

A mapping agent reads your files and builds structure from them. The result is a local memory layer your tools and assistants can query, inspect, and keep updated.

Input

Existing notes, specs, transcripts, PDFs, and working documents stay in place.

Output

A local .clio/ memory layer of concepts, facts, and linked situations.

Access

Query through the CLI or expose to assistants through local MCP.

The Process

From source files to structured memory in one pass.

Point Clio at an existing folder. The agent reads what's there, extracts concepts, facts, and linked situations, and writes a local memory layer your tools can work against.

Your files

Notes, specs, transcripts, PDFs, and working documents. They stay exactly where they are.

Clio Agent

Maps concepts, facts, and linked situations from the material using local or hosted inference.

.clio/ memory

A local graph layer built beside your files. Queryable, inspectable, and kept in sync.

Your tools

Access through the CLI directly, or expose to any MCP-ready assistant via local MCP.

Vault Structure

Clio works alongside your files, not on top of them.

Running clio init creates a hidden .clio/ directory inside an existing folder. Your original files stay untouched while Clio writes the graph, facts, interaction history, and config into this local memory layer.

A simplified folder looks like this
project-folder/
  notes.md
  interview-transcript.pdf
  pricing-postmortem.md
  .clio/
    graph/
    facts/
    interactions/
    .manifest.json
    config.yaml
graph/

Concept nodes and the structure that organizes the memory.

facts/

Fact nodes attached to the concepts that contextualize them.

interactions/

Interaction history tied back to the memory a query touched.

.manifest.json

Tracking for processed files and change detection.

Commands

A small surface. A short path to working memory.

Initialize a folder, sync the agent over your material, query the memory, and connect an assistant. Four commands cover the full operating loop.

clio init Create the local .clio/ layer inside an existing folder.
clio sync Run Clio Agent over new or changed files and update the memory structure.
clio query "..." Ask questions against the structured memory instead of relying on flat retrieval.
clio mcp Run a local MCP server so assistants can access the memory through tools.
Local-first CLI + MCP EUR 5 / month

Put your material to work.