Korium documentation

1. Getting started

These guides assume you haven’t connected Korium before. You’ll need access to a Korium account and an assistant that can connect to it. You do not need the Mac CLI just to use memory.

• Getting StartedChoose your assistant, connect it and check its permissions.
• Your first memorySave a decision, find it in a new chat and make a correction.
• What to SaveDecisions, corrections, lessons and the context that makes them useful.

2. Using Korium well

Once the first round trip works, make the memory useful to someone who wasn’t in the room. Keep the evidence, make corrections explicit and teach your agents when to read and write.

• How to Find and correctFind the relevant memory, follow the sources and record what changed.
• The four parts of KoriumSee how memory, code, skills and workflows work together.
• Korium:CodeFind the implementation and understand the decisions behind it.
• Korium:SkillsLoad a reusable method, adapt it and check the result.
• Korium:WorkflowChoose a playbook and take a task through its steps and reviews.
• Build the habit into your workProject instructions, useful captures and checks that don’t trap the agent.
• Sharing and accessDecide who can read, who can write and what should never be saved.

3. Build it into your workflow

This section is for people setting up a team or building the integration. Each guide separates the configuration from the check that proves it worked.

• Codex / ChatGPTConnect either client; add project skills and hooks for local Codex work.
• Claude Code and CoworkUse a remote connector in Cowork or project instructions and hooks in Claude Code.
• OpenClawConnect memory, verify it and build meeting, briefing and handoff workflows.
• Index your codeInstall the Mac CLI and build a commit-aware map.
• CLI and BashCommands, scripts, exit handling and unattended runs.
• Git and GitHubPost-commit hooks and a carefully scoped Actions example.
• MCP and OAuthConnection details, scopes and read-only clients.
• How memory worksRetrieval, ranking, relationships and changing truth.
• Tool referenceThe tools your assistant uses, their inputs and their boundaries.
• TroubleshootingFind the failing part before changing the setup.

Before you change an existing setup

Use the setup checklist to verify transcript sources, memory connections and your branch code indexes before automating the work.

If you get stuck

Keep the exact error and the step that produced it. Don’t paste a token, a credential file or private memory content into a support request. Start with the troubleshooting guide, or ask us.

For account limits, exports and billing, read questions and answers. Current plan prices stay on the account pricing page.