# 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.

**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. Use the right Korium account

Sign in to [your Korium account](https://app.kyroco.ai/login). If your team invited you, use that invitation so you join your company’s account. Your assistant then reads what you can read there: your own notebook, memories shared with you, the workspaces you belong to and, where your plan has it, Everyone. A separate account is not automatically part of your company’s account.

If you need an account, see the [account options](https://app.kyroco.ai/pricing.md). You also need access to the assistant you want to connect; Korium does not replace that subscription.

## 2. Connect the assistant you use

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

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

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

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 account. 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

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

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 download shows on your dashboard only once your account has Code Indexer ([see how to get it](indexing-your-code.html)). Its sign-in is separate from your assistant’s memory connection. Keep those two setups separate when troubleshooting.

[All Korium guides](index.html) [Next: Your first memory](getting-started.html)

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