Skip to content
Aknov0.18.16
Color scheme
Contrast
Color scheme
Contrast
Akno logo

Memory your agent can cite, and you can edit.

Akno gives an agent continuity across conversations without turning memory into an opaque chat-provider feature—the Markdown files you already own stay the source of truth.

Evidence, not fragments

Ordinary retrieval hands an agent text. Akno hands it evidence with enough structure to act responsibly: every returned claim carries a page line or document-page citation, recall finds and ranks that evidence while answer produces a separately verified response, and a clean miss stays distinct from a failed model or a degraded ranking path.

Files stay authoritative

Indexing leaves the set and bytes of your source files unchanged by default. Search projections are rebuildable, so the same notes you edit in Obsidian, vim, or any other editor remain the thing Akno reads from.

Evidence is not automatically belief

Pages, source documents, inferred observations, and ignored material carry different roles and retrieval policies. A proposal or an attributed report stays useful as context without silently becoming a current fact.

Writes are bounded

Mutations are journalled and undoable. The nightly dream cycle plans exact diffs before a human or a separate curator decides what may apply, and scheduled maintenance defaults to audit mode.

Choose a path

If you want to… Start with
Install Akno or try the demo Getting started
Understand the everyday memory workflow Memory lifecycle, Concepts
Read or supply agent context Reading memory
Write memory or ingest documents Writing and ingestion
Configure autonomous maintenance The dream cycle
Deploy, diagnose, or recover Akno Operations
Understand the implementation How Akno works

Akno is in active pre-1.0 development and runs on a real personal knowledge base. It does not replace your editor, backup system, or judgment—it only knows what the indexed files and documents contain. See Limitations for the boundaries that matter before you rely on it.