Korium / Find the memory.
Korium is memory for the AI tools you already use.
Everything you explain to an assistant is gone when the chat ends, and if you use more than one, they do not share a memory either. Korium saves it, with the reason and who decided, so the next chat, a different assistant or a coworker’s assistant starts by looking up what came before.
Example. Five questions people ask Korium, and what it answers.
While you were out October 6 to October 24 · from 14 memories in Marketing and Sales
Decided
- Midwest accounts keep net-45 through Q1, because of the Q2 dispute.Dana, on the October 14 call. Replaces the September 2 decision.
- Acme’s renewal holds at the current rate.Lee, October 9, from the renewal call.
- The onboarding flow now belongs to Priya.Riley, October 17. It was yours.
Needs you next
- Approve the Q1 terms memo before it goes to the whole company.Lee asked on October 21. Waiting for you.
- Acme wants the Midwest exception explained in writing.Promised on October 9. Nobody has sent it.
Who owns what now
Onboarding flow PriyaAcme renewal LeeMidwest terms Dana
Every line links to the memory behind it: who said it, when, and what it replaced.
Why did we move the save button to the top of the form?
Save moved above the fold Decision · Product · October 3 · 1 memory, 2 sources
What was decided
- The Save button sits at the top of the memory form, not under it.Priya decided, October 3.
Why
- Four of five testers in the September 29 round scrolled past the old button. Two saved nothing.Sam’s test notes, attached to the memory.
What it replaced, and since then
- The August layout, kept on file.One follow-up: keyboard order was wrong, fixed October 8. Nobody has questioned the move.
A product decision with its evidence, so the next redesign starts from the test, not the opinion.
Where is the invoice export code, its tests, and what calls it? And why does it skip canceled orders?
Invoice export Code map at commit 9f3c2a1, indexed this morning · 1 decision
Where
- InvoiceExport.build, lib/billing/invoice_export.ex, lines 41 to 97.The filter is in the query, lines 58 to 63.
- Tests: test/billing/invoice_export_test.exs, lines 12 to 140. Eleven tests; the canceled-order one is at line 88.From the map, which indexes test names too.
- Called from BillingController.export, line 120, and Jobs.NightlyExport.run, line 33.The agent found the callers by reading the code the map pointed it at.
Why it skips canceled orders
- Finance disputed three canceled invoices in Q1, so canceled orders never reach the export.Lee decided, March 12. Test: invoice_export_test.exs, line 88.
Watch out
- The April 2 change moved the filter from the view into the query.The memory was updated the same day. The old note is kept, marked replaced.
The map says where. The memory says why. The agent reads the code itself before it changes anything.
What did we promise Acme on the renewal call?
Promises to Acme October 9 renewal call · from the transcript and 2 memories
Kept
- Hold the current rate through the renewal.Lee, October 9. Confirmed in the October 16 order.
Still open
- Send a written explanation of the Midwest net-45 exception.Promised October 9. Nobody has sent it.
- Name a support contact for Acme by November 1.Riley owns it. Six days left.
A promise is a memory with a date on it. Korium keeps the date.
Is there tension between teams on the Q1 launch?
Three teams, three different Q1 launches From 9 memories across Marketing, Sales and Engineering, October 2 to 23
What each team wants
- Marketing wants the launch on January 12, to land before the trade show.Riley, October 2 planning note. Date already in the newsletter draft.
- Sales wants the Midwest exception in the launch, or they will not pitch it.Lee, October 9, after the Acme call. “No exception, no demo.”
- Engineering wants the exception out of Q1, because it touches the invoice export.Priya, October 20. The export is mid-change until November 14.
Where it collides
- Marketing’s date assumes a scope Engineering has not agreed to. Nobody has said so in one room yet.No memory records the three of them deciding together.
Who should be in the meeting
Marketing RileySales LeeEngineering PriyaDecides Dana, who owns the Midwest terms
Four people, one decision. Korium names them because the memories do, not from the org chart.
Coming next: your own notebook, workspaces, and one Inbox, where the asks that need you wait, and where what a teammate shared with you alone shows up.
How you use it
Three steps. No new app to learn, no one to train.
Connect the assistant you already use.
Claude, Codex, Gemini or any tool that speaks MCP. One address, a browser sign-in, done.
Say “remember this.”
When something gets decided, tell your assistant to save it: what was decided, why, and where it came from. It is the sentence you would have said out loud anyway.
Ask for it back, from anywhere.
Next week, in a new chat, from a different assistant, or from a teammate’s: “What did we decide about the Midwest terms, and why?” The answer comes with the memory behind it, so you can check it.
In plain words
What Korium is. What it is not.
| Korium is | Korium is not |
|---|---|
| One memory your people and your agents both read and write. | Another chatbot. You keep the assistant you have. |
| Decisions with their reasons and sources, and the old decision kept when a new one replaces it. | A search engine over every file your company owns. It does not crawl your drives and inboxes. |
| Something you choose to put in, and choose who can see. | Blanket access to every service your company uses. |
Who it is for
People first. Agents second.
Most memory products are built for agents. Korium is built for the people who do the work, and agents read from the same memory.
When Jane is on leave, her team asks Korium instead of Jane. The agent drafting the invoice reads the same memory, in context, while it works. What either of them learns goes back in.
What happens after you say “remember this”For teams building software
Your agent should not have to rediscover the whole codebase.
Korium also keeps a map of your code: the symbols, files and line ranges, tied to a commit, so an agent finds the right code without rereading the repository. The source stays on your Mac. Only the map goes up.
Index your first repositoryWho can see what
It’s your company’s knowledge. Treat it that way.
Access is checked on the server, per account and per person. An assistant can be given read-only access, so it finds memories but cannot save new ones.
Keep credentials and private information out of memory; Korium does not need them to be useful. Our published security and privacy documents explain the data handling and the terms that apply.
Put it to work
Start with something you don’t want to explain twice.
Start free, on your own, with no card. Add your team when you want to share. Plans are per seat.
Compare subscription plans without signing in. Choose your plan, then create your account.