Docs · AiAkiv

Start here — what it is

What AiAkiv is AiAkiv is an outside service that remembers relationships, not a file locker, but a long-term memory for AI that records what happened and why. Core concepts: Event · Entity · Tag Saving creates three things. Knowing who makes each one tells you what to care about: why entities keep search alive, and why tags are worth attaching. AiAkiv is not a document store What gets stored is shaped for an AI to read. Keep the documents people read somewhere else, and leave in AiAkiv the process that produced them.

Using it

Five-minute quickstart Connect, save once, search once. Three steps is enough to see AiAkiv working. Saving It saves only when you command it with `ak`. The conventions that make memories worth having, and how to correct or retire one afterwards. Searching It finds by meaning and connection, not keyword matching. `@` attribution, causal and time questions, and how to read a result. Chained saves (threads) Chain, don't trim. Split long text and ongoing records with `prev_event_id` so the flow survives. Asking by relationship: ak graph Graph queries with `ak graph`: fix a name or tag scope, then ask. How to ask, example requests and the queries they become, the grammar, how to read the response, and the limits.

Boundaries

Teams and projects: the team owns the memory, the project is the way in Who owns the memory (the team) and how you get into it (the project). The save target (Main) and the guard on switching it. Creating and managing teams (including sub-parts) Invitations and roles, the sub-part tree, reading flows down but writing does not, the ‘Apply’ gate, and retire vs delete. Team sharing AiAkiv's real strength shows when several people build the memory together. Team isolation and `@` attribution keep it from blurring. What you may store (security and limits) It's an outside service and what you store stays. The do-not-store list, where responsibility sits, and the domains an IT admin blocks.

Connecting your AI

Authentication: OAuth and API keys OAuth has the system authenticate for you; an API key binds authentication to the key itself. Which client uses which, and the minimum key hygiene. Folder binding: pinning a save target per working folder Pin a project to a folder and the switching accident disappears structurally. Per-client setup and how to read the `binding` value. Using project binding in Claude Desktop `</> Code` is Claude Code. But it never shows the approval prompt: without approving in advance only the account connector is left and saves go to Main. Even when approved the account connector attaches alongside; leave it on and check where each save went. When the account connector and a folder connection are both attached Claude Code and Desktop's `</> Code` attach your claude.ai account connector separately from the folder connection. Leave the account connector on: turning it off removes AiAkiv from the web and the mobile app too. The AI saves through the folder connection first, but that isn't enforced, so check where each save went. If saves must go to the folder only, turn Main off for a while in the AiAkiv console. Connecting ChatGPT and ChatGPT classic Both apps install AiAkiv from the plugin directory. The API key is for pinning a project per folder. App features are not in the official ChatGPT plugin, because parts of them don't fit OpenAI's plugin review policy. To use them, connect Codex separately with the install prompt (app features and seven skills, saving to Main) or connect a folder with an API key. The Codex install prompt: AiAkiv connection and skills in one go Paste it into a Codex chat and Codex registers the AiAkiv connection, opens the sign-in window, installs the seven skills and writes an install record on its own. No developer mode needed. Before pasting, remove the existing AiAkiv Memory plugin, or, if you keep it, rename this connection to AiAkivCodex. The Codex verification prompt: checking the install Paste it into a new session after installing with the Codex install prompt. It checks the connection, the two app tools (create_aiakiv_card, run_aiakiv_app_action), the save location (binding main) and the seven skills one by one, and appends the results to the install record.

Reaching further

Links: reading another team's memory Two memories are joined by entity aliases. The link is one-directional, and when memory content changes the aliases have to be updated too. Public memory: memories anyone can read Anyone attaches and reads without an invitation, but nobody writes, and only AiAkiv can create one for now. The two ways to attach, and the public attach that ties one into your own team. Economic-Report: an economic data space everyone can read A read-only public memory of public economic data and institutional releases. Eighteen source projects, how to use it, and the data caveats before citing. Cards: pulling a memory out as one shareable page A one-page public page your AI writes from your memories. Public the moment it's made; managed from the console or by asking your AI.

With AI, and when stuck

For AIs connected to AiAkiv Written for an AI, not a person. Three rules, and a map of every tool the engine exposes. Working with several AIs (and still understanding it) Share judgment, not just output. Splitting implementer and reviewer, handing off through ak, and staying a node inside the graph rather than outside it. Console menu guide Saving and searching happen in your AI; the console is where you build and maintain the ways in. What each of the six menu groups does. Asking your AI to do console work Teams, links, audit, history, projects, the save target and cards from the conversation. You decide what is turned on in AI permissions; anything irreversible still belongs to a human. The app action tool: run_aiakiv_app_action and which connections have it The tool your AI uses to ask an AiAkiv app (such as the console app) to do something. Folder connections, API key connections, plugin installs and connections attached with the address `https://mcp.aiakiv.com/mcp?apps=all` have it; the official ChatGPT plugin and sign-in connections attached with an address that lacks `?apps=all` do not. What you can do without it, and which connections have it. In ChatGPT you get it by connecting Codex with the install prompt or by connecting a folder with an API key. Common problems (FAQ) When a memory you expected isn't there, when saving doesn't happen, when search comes back wrong. What to check, in order. Saving tokens, Claude only: work in chunks, save, then compact Claude only. Six habits (work in chunks, keep one model, return within 1 hour, ak save, compact, rest) that keep the earlier conversation in memory and add only what changed: fewer tokens, context kept. Does not apply to ChatGPT.