# Getting started with Korium

Start with the assistant you already use. Connect it to Korium, then save one decision and ask for it back in a new conversation. You do not need to set up code indexing or hooks to do that.

## 1. Use the right Korium workspace {#account}

Sign in to <a data-app-path="/login" href="https://app.kyroco.ai/login">your Korium account</a>. If your team invited you, use that invitation so your assistant reads the same company memory as theirs. A separate account is not automatically part of your company’s workspace.

If you need an account, see the <a data-app-path="/pricing.md" href="https://app.kyroco.ai/pricing.md">account options</a>. You also need access to the assistant you want to connect; Korium does not replace that subscription.

## 2. Connect the assistant you use {#client}

Each guide walks through the connection and the sign-in. Choose one to start; you can connect the others to the same workspace later.

<ul class="guide-list"><li><a href="codex.html#connect">Codex</a><span>Use the app’s MCP settings or the Codex command line.</span></li><li><a href="codex.html#chatgpt">ChatGPT</a><span>Connect remote MCP in ChatGPT, with a separate path for local desktop work.</span></li><li><a href="claude-code.html#connect">Claude Code</a><span>Add Korium, then authorize it through /mcp.</span></li><li><a href="claude-code.html#cowork">Claude Cowork</a><span>Add a custom connector through your Claude account.</span></li><li><a href="openclaw.html#connect">OpenClaw</a><span>Add Korium to the agent’s outbound MCP connections.</span></li><li><a href="connect-any-mcp-client.html">Another MCP client</a><span>Use the service address and OAuth scopes in the connection reference.</span></li></ul>

All these connections use `https://api.kyroco.ai/mcp`. Complete the browser sign-in and review the requested permissions. Do not copy tokens from another assistant to make a new connection work.

## 3. Check the connection, not just the settings {#check}

In your connected assistant, ask:

```
Use Korium to search for a decision about my project.
Show which memory you used. If nothing matches, say so.
Also tell me whether the Korium save tool is available.
```

A successful search call proves more than a server name in the settings. An empty result can be normal in a new workspace. An authentication error is different: finish signing in through this client before trying again.

The tools are `agent_search` and `agent_capture`; clients may put a prefix in front of those names. A read-only connection can search but cannot save. [Check the permissions](connect-any-mcp-client.html#scopes) if you need both.

## 4. Save something and find it again {#first-memory}

Follow [Your first memory](getting-started.html). It takes you through a labeled example, a capture receipt, a fresh-chat search and a correction. Keep the memory ID so you can check the answer against what was saved.

## Add the parts your work needs {#next}

Use [Korium:Skills](skills.html) to give your assistant a repeatable way to do a task, and [Korium:Workflow](workflows.html) to carry a piece of work through its steps and reviews. Add [Korium:Code](code.html) when the assistant needs to find its way around a codebase.

The Mac CLI is for that code map. Its sign-in is separate from your assistant’s memory connection. Keep those two setups separate when troubleshooting.