Skip to the content
Create your org
  1. Docs
  2. Company
  3. Read me first.md
3 agents connected

Open to your teamMonday 08:55

Give every agent your team's memory.

kmem is a knowledge base for your team. Agents read it and propose changes. People decide what changes.

Create your orgSee how it works

This is a live example. Your choices change only this page.

Works with the agents your team uses

One day with your team's memory

Scroll through a working day. Each step is a part of kmem that you can try.

A new session starts with your team's decisions.

Before an agent writes code, it calls recall. kmem returns the paragraphs that answer the question, with a link to each source doc.

Compare the session

Add retries to the refund job.

I will retry 5 times with exponential backoff, and I will add a new queue for failed refunds.

A guess. Your team chose 3 retries and one queue.

Example session.

Three paragraphs, not three hundred pages.

recall ranks each paragraph in your docs and returns the best ones inside a token budget. If your docs do not have the answer, recall says so.

Choose a question

recall("refund job retries")

Your docs186,400 tokens

This answer412 tokens

  1. 1payments/refunds.mdRetry a failed refund 3 times, 10 minutes apart. Use the same idempotency key for each try.148
  2. 2adr/0007-one-queue.mdPayments work uses one queue. A second queue doubled the refund incidents, so we removed it.131
  3. 3runbooks/refund-stuck.mdAfter the third failed try, page the payments on-call and add the order to the incident doc.133

Not in your docs: the refund limit for orders in Japan.

Example docs and questions.

Agents propose. People decide.

When an agent learns something, it proposes a change. In a new org, each agent change waits in Review until a person accepts it. Each block records who wrote it.

1 change waits in Review

Claude Code proposes a change

A refund over $10,000 needs a second approver.

Why The finance call this morning set the limit. At 09:01, recall named this gap.

refunds.md

Refunds

Priya wrote this on 12 Sep.

Retry a failed refund 3 times, 10 minutes apart. Use the same idempotency key for each try.

Priya wrote this on 12 Sep.

Treat a 409 from the provider as a success.

Codex proposed this on 14 Sep. Sam accepted it.
  • Written by a person
  • Proposed by an agent, accepted by a person
Example doc. Sam, a teammate, accepts the change.

Your docs are Markdown files.

kmem stores each doc as a plain .md file. Import Markdown files, a folder or a zip. Export each doc at any time, byte for byte, and open it in any editor.

  1. your-team/
  2. adr/
  3. 0007-one-queue.md
  4. 0011-timeouts.md
  5. payments/
  6. ledger.md
  7. providers.md
  8. refunds.md
  9. runbooks/
  10. refund-stuck.md
  1. your-team
  2. payments
  3. refunds.md
Show the doc as

Refunds

Retry a failed refund 3 times, 10 minutes apart. Use the same idempotency key for each try.

Treat a 409 from the provider as a success.

A refund over $10,000 needs a second approver.

After 3 failed tries

  • Page the payments on-call.
  • Add the order to the incident doc.

The same doc, two views. kmem adds no markup to the file.

Your team goes home. The memory stays.

Tomorrow at 09:00, each agent starts from the same docs.

Connect the agents your team uses.

Claude Code, Codex, Cursor and OpenCode connect over MCP with a token. Claude and ChatGPT sign in to kmem. A connection reads only the docs that its person can read.

Terminal
claude mcp add --transport http --scope user your-team-kmem https://your-team.kmem.app/mcp --header "Authorization: Bearer <your-token>"
Read the setup guide

kmem gives an agent 7 tools.

  • browse
  • read
  • recall
  • remember
  • edit
  • link
  • verify

Each logo belongs to its owner.

What you get

Format
Plain Markdown. Import and export at any time.
Agents
7 MCP tools. Their definitions use 1,827 tokens.
Changes
Agent changes wait in Review. Agent writes start off.
Answers
Ask answers a question and names its source docs.
Access
Each doc is Open or Private. A connection reads what its person reads.
Hosting
The kmem team runs it for you. You install nothing.

Overnight, agents still use the docs.

  1. Codex recalls runbooks/refund-stuck.md for an on-call alert.
  2. Claude Code reads payments/refunds.md before a hotfix.
  3. A change from Cursor waits in Review for the morning.

Example night.

On Tuesday, a new session starts with Monday's decisions.

Sam accepted the approver rule on Monday. Today a new agent session recalls it, with a link to the doc. Nobody explains it again.

Add a refund limit to the admin page.

kmem recall("refund approver limit")1 paragraph, 142 tokens

  1. kmem://payments/refunds#approverA refund over $10,000 needs a second approver.Claude Code proposed this on Monday at 11:42. Sam accepted it at 11:44.

I will add a second approver step for each refund over $10,000.

Monday's decision is in the answer, with its source.

Example session.

Start with the docs your team has.

Create your org, import your Markdown, and connect your first agent.

Create your orgRead the help center

kmem is a paid, hosted service. We announce the price before checkout opens.