Check your Korium setup

Start with a working connection

For memory, connect your assistant to the intended workspace and complete the save, find and correct exercise. Use harmless sample material while checking the connection.

For code indexing, record korium-cli version and check that the instructions match your installed client. These guides describe korium-cli 1.0.0, which you download from your dashboard. It reads repositories as version 0.3.12, which is the VERSION korium-cli repos shows for an index this client read in full. The starter toolkit has its own version and file hashes; inspect those before installing or updating hooks.

Keep existing project instructions and hooks when adding Korium. Review how the new steps fit the project instead of overwriting its setup.

Check the memory and its connections

A wrong-link correction is retained as a labeled example. It does not grant permission to change unrelated records or make a source trustworthy by itself.

Memory currency is a separate question. The lifecycle guide explains replacement, use-based ranking and type-based expiry.

Follow a passage back to the meeting

Suppose a meeting contains a report decision, its reason and several unrelated discussions. Korium keeps the original transcript and links the smaller pieces back to it, so you can retrieve a useful passage without losing where it came from.

The underlying search favors a matching piece over a duplicate hit for its own transcript. If only the whole transcript matches, it can still be returned. At most three pieces from one transcript occupy the same search page, so one long meeting does not crowd out all the other sources.

1. Save a transcript you have permission to use and keep its capture ID.
2. Ask for a specific decision and compare the returned passage with the original words.
3. Follow the piece’s source link to inspect the surrounding discussion.
4. Ask a broader question, then a precise one. Check that the answer fits what you asked rather than repeating every matching passage.
5. Confirm the storage count: the original save uses one memory of room, not one for every piece.

Processing a transcript does not turn every comment into an approved decision. Record who made the decision and what evidence supports that attribution.

Check your branch indexes

Every branch has its own index. korium-cli index indexes the branch the checkout is on, and indexing one branch never replaces another branch’s index.

One index per repository is the trunk: the index a search reads when it names no branch. Normally it is the repository’s default branch, as git records it for the origin remote, and indexing that branch makes it the trunk. korium-cli tells Korium which branch is the default only when git knows; git remote set-head origin -a teaches git. When git does not know, korium-cli says so, and a repository with no trunk yet takes the first branch it indexes. Once a repository has a trunk, it moves to another branch only when an index of that branch finishes, sent from a checkout whose remote names it as the default, by an account allowed to publish this repository’s index. Until a repository has a trunk, a search that names no branch lists the branches Korium holds for it.

Korium removes the index of any branch other than the trunk once nobody has indexed that branch for 14 days. The trunk is kept. When the trunk moves, the old trunk becomes an ordinary branch and its 14 days start from that moment.

The CLI compares the repository with the server before sending an update. If they match, there is nothing to upload; if they differ, the update is based on what the server actually holds.

1. Run korium-cli repos and check that the branch marked (trunk) is the one you expect. It also shows, for every other branch, how long until Korium removes it.
2. Index from a named branch. A detached checkout is turned down. The --branch flag only checks the branch you have checked out; it never picks which branch is indexed.
3. Decide which updates run by themselves: the Git hook, an agent’s end-of-task hook, CI. Each one updates the index of the branch it runs on.
4. In CI, explicitly check out the intended branch and verify it before indexing.
5. After an index finishes, search for a known symbol and compare the returned branch and commit with the ones you expect. Read the source in your checkout before changing it.

An accepted upload and verified publication are different results. Follow the indexing guide to distinguish them. korium-cli search reads the index of the branch you are on when Korium holds one, and the trunk otherwise, and says which.

Test the whole handoff before automating it

Use a harmless repository and a clearly labeled memory example. The Codex and Claude Code guides cover the client-specific setup.

• A fresh task can search the intended workspace and show its source memory.
• A refused capture is reported as refused; a successful correction has a checked replacement link.
• The index hook turns down a detached checkout and lets the task finish, even when this Mac is not signed in.
• A CLI failure produces a useful notice and does not force an endless Stop continuation.
• An accepted upload is not announced as verified publication.
• A missing graph or incomplete result is not presented as a complete count.

Keep the client version, time and non-sensitive result IDs when a check fails. Share those through the support path, not credential files or private source material.