# Korium documentation

You don’t need to learn the whole product before you use it. Start by saving one useful memory and finding it in a fresh conversation. The rest builds from there.

**Need a Korium account?** Choose a plan and sign up before connecting your assistant.

[View plans & sign up](https://app.kyroco.ai/pricing.md) [Manage subscription](https://app.kyroco.ai/account)

## 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 Started](connect-korium.html) Choose your assistant, connect it and check its permissions.
- [Your first memory](getting-started.html) Save a decision, find it in a new chat and make a correction.
- [What to Save](what-you-can-store.html) Decisions, 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 correct](working-with-memory.html) Find the relevant memory, follow the sources and record what changed.
- [The four parts of Korium](capabilities.html) See how memory, code, skills and workflows work together.
- [Korium:Code](code.html) Find the implementation and understand the decisions behind it.
- [Korium:Skills](skills.html) Load a reusable method, adapt it and check the result.
- [Korium:Workflow](workflows.html) Choose a playbook and take a task through its steps and reviews.
- [Build the habit into your work](make-it-automatic.html) Project instructions, useful captures and checks that don’t trap the agent.
- [Sharing and access](security-and-access.html) Decide who can read, who can write and what should never be saved.
- [How your company's knowledge moves](how-company-knowledge-moves.html) Notebooks, workspaces, Everyone, sharing and promoting, and what is still coming.
- [Workspaces](workspaces.html) Make a workspace, add people, and see what each role can do there.
- [Share a memory](sharing-memories.html) Share into a workspace or with one person, and stop sharing.
- [Promote to Everyone](promoting-to-everyone.html) Ask for a memory to reach the whole account, and see who answers.
- [The Inbox](the-inbox.html) Answer requests, read updates and track what you asked for.
- [People and roles](people-and-roles.html) Add people, set roles and pick a default workspace.
- [The activity log](activity-log.html) See who did what, without ever showing a memory’s words.
- [Row menus](row-menus.html) What each three-dot menu offers and why an item may be missing.

## 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 / ChatGPT](codex.html) Connect either client; add project skills and hooks for local Codex work.
- [Claude Code and Cowork](claude-code.html) Use a remote connector in Cowork or project instructions and hooks in Claude Code.
- [OpenClaw](openclaw.html) Connect memory, verify it and build meeting, briefing and handoff workflows.
- [Index your code](indexing-your-code.html) Install the Mac CLI and build a commit-aware map.
- [CLI and Bash](cli-and-bash.html) Commands, scripts, exit handling and unattended runs.
- [Git and GitHub](git-and-github.html) Post-commit hooks and a carefully scoped Actions example.
- [MCP and OAuth](connect-any-mcp-client.html) Connection details, scopes and read-only clients.
- [How memory works](how-memory-works.html) Retrieval, ranking, relationships and changing truth.
- [Tool reference](tool-reference.html) The tools your assistant uses, their inputs and their boundaries.
- [Troubleshooting](troubleshooting.html) Find the failing part before changing the setup.

## 4. Advanced

Settings that change how Korium behaves for your whole account. Each guide says why the setting is yours to choose, what moving it does, and how to test a change before you keep it.

- [Tuning Memories Fade](memories-fade.html) How much a memory’s age lowers its rank in search, with worked examples.

## Before you change an existing setup

Use the [setup checklist](release-status.html) 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](troubleshooting.html), or [contact support](mailto:support@kyroco.ai).

For account limits, exports and billing, read [questions and answers](../../korium-qa.html). Current plan prices stay on the [account pricing page](https://app.kyroco.ai/pricing.md).

[All Korium guides](index.html) [Next: Getting Started](connect-korium.html)

Use the [setup checklist](release-status.html) before changing an automated workflow. Check your installed client’s help if its interface differs.