Works with the tools your team already uses

Cursor
Claude Code
Windsurf
Codex
Zed

Your code does not explain itself.

Coding agents can read all of it. None of it says why.

Decisions

The reasons behind a choice live with the person who made it, and leave when they do.

Documentation

It was true when it was written. Nothing marks it stale when the code moves on.

Conventions

The rules a team actually follows are the ones nobody wrote down.

Every new session works it out again, in tokens and in your team’s time.

Memory that moves with every branch and merge.

Memkith gives each coding agent the memories reachable from the branch it is working on. The history belongs to the team, not to the tool.

@sam · fix/replay
Lessons land with the code that taught them.
Sam's first attempt at deduping does not hold once a second worker picks up a retry. He fixes it, and his agent saves the reason from the branch he is on, addressed to the file it concerns.
Ticket assigned PAY-1042
Duplicate charges when Stripe retries a webhook
new memory
Claim each event in Postgres before enqueueing
An in-process cache misses retries that land on another worker.
scopesrc/payments/stripe.ts
@sam · Codex
Ticket assigned PAY-1042
Duplicate charges when Stripe retries a webhook
new memory
Claim each event in Postgres before enqueueing
An in-process cache misses retries that land on another worker.
scopesrc/payments/stripe.ts
@sam · Codex
@priya · feat/refunds
The next feature starts from them.
Priya opens a new feature and her agent asks before writing anything. Sam's memory answers, so nobody pays to work the same problem out twice.
Ticket assigned PAY-1108
Add refund handling to the payments service
Asked by Claude Code
How should we dedupe webhook events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
new memory
A refund can arrive before its charge settles
Stripe sends the two events independently, so the charge row may not exist yet.
scopesrc/payments/refunds.ts
@priya · Claude Code
Ticket assigned PAY-1108
Add refund handling to the payments service
Asked by Claude Code
How should we dedupe webhook events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
new memory
A refund can arrive before its charge settles
Stripe sends the two events independently, so the charge row may not exist yet.
scopesrc/payments/refunds.ts
@priya · Claude Code
@jordan · feat/payouts off feat/refunds
A branch off a branch inherits both.
Jordan needs Priya's work before it has merged, so he branches off it. Her reasoning reaches him through the parent branch and Sam's through staging, without him reading either pull request.
Asked by Cursor
How do we handle refund events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via feat/refunds, not staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
Asked by Cursor
How do we handle refund events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via feat/refunds, not staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
@priya · feat/refunds
The merge carries the reasoning too.
feat/refunds merges. Priya's lesson moves onto the trunk with the code it describes, so it is there for everyone who branches next rather than only for her.
now on staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
now on staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
@jordan · feat/payouts
Documentation that writes itself.
Each merge leaves its reasoning on staging. The next feature starts with all of it, written by the agents doing the work rather than by someone remembering to write it down.
new memory
Reconcile payouts from the receipts table
A charge total moves when a refund lands early. Receipts do not.
scopesrc/payments/payouts.ts
@jordan · Cursor
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
via staging
Reconcile payouts from the receipts table because a charge total moves after a refund
@jordan · Cursor
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
via staging
Reconcile payouts from the receipts table because a charge total moves after a refund
@jordan · Cursor
new memory
Reconcile payouts from the receipts table
A charge total moves when a refund lands early. Receipts do not.
scopesrc/payments/payouts.ts
@jordan · Cursor

Stop paying to re-explain the codebase.

Every agent session starts cold: paste the context, restate the decision, re-argue what was settled last month. Memkith serves it instead.

Review pricing

Engineers

LightSteadyHeavy

Most engineers, most days. 20 sessions a week, 6 minutes and 300k tokens of context each.

Estimated savings

$229,632

a year

Engineer time: $139,776; 2,496 hours a year
Token spend: $89,856; 7.8B tokens a year

Your estimate, not our measurement: $ per hour per engineer, and Claude Fable 5 API list at $10 in and $50 out per million tokens.

What engineering teams ask before they adopt.

What does Memkith remember?

Decisions, constraints, failed approaches, review outcomes, and other engineering context, attached to the code it explains.

How is this different from an agent’s built-in memory?

Agent-native memory stays with that tool. Memkith gives supported agents access to shared team memory, so the engineering record remains when the team changes agents.

Which coding agents work with Memkith?

Memkith works over MCP with Cursor, Claude Code, Windsurf, Codex, and Zed.

Who can access team memory?

Shared memory stays inside the team that owns the code. Memories can also be scoped to a repository, branch, file, function, or line.

Review security

How long does setup take, and what does it cost?

Setup is 3 CLI commands. The published plan is free for teams of up to 4 seats, then starts at $15 per user per month.

Review full pricing

Supported by

memkith

Works with the tools your team already uses

Cursor
Claude Code
Windsurf
Codex
Zed

Your code does not explain itself.

Coding agents can read all of it. None of it says why.

Decisions

The reasons behind a choice live with the person who made it, and leave when they do.

Documentation

It was true when it was written. Nothing marks it stale when the code moves on.

Conventions

The rules a team actually follows are the ones nobody wrote down.

Every new session works it out again, in tokens and in your team’s time.

Memory that moves with every branch and merge.

Memkith gives each coding agent the memories reachable from the branch it is working on. The history belongs to the team, not to the tool.

@sam · fix/replay
Lessons land with the code that taught them.
Sam's first attempt at deduping does not hold once a second worker picks up a retry. He fixes it, and his agent saves the reason from the branch he is on, addressed to the file it concerns.
Ticket assigned PAY-1042
Duplicate charges when Stripe retries a webhook
new memory
Claim each event in Postgres before enqueueing
An in-process cache misses retries that land on another worker.
scopesrc/payments/stripe.ts
@sam · Codex
Ticket assigned PAY-1042
Duplicate charges when Stripe retries a webhook
new memory
Claim each event in Postgres before enqueueing
An in-process cache misses retries that land on another worker.
scopesrc/payments/stripe.ts
@sam · Codex
@priya · feat/refunds
The next feature starts from them.
Priya opens a new feature and her agent asks before writing anything. Sam's memory answers, so nobody pays to work the same problem out twice.
Ticket assigned PAY-1108
Add refund handling to the payments service
Asked by Claude Code
How should we dedupe webhook events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
new memory
A refund can arrive before its charge settles
Stripe sends the two events independently, so the charge row may not exist yet.
scopesrc/payments/refunds.ts
@priya · Claude Code
Ticket assigned PAY-1108
Add refund handling to the payments service
Asked by Claude Code
How should we dedupe webhook events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
new memory
A refund can arrive before its charge settles
Stripe sends the two events independently, so the charge row may not exist yet.
scopesrc/payments/refunds.ts
@priya · Claude Code
@jordan · feat/payouts off feat/refunds
A branch off a branch inherits both.
Jordan needs Priya's work before it has merged, so he branches off it. Her reasoning reaches him through the parent branch and Sam's through staging, without him reading either pull request.
Asked by Cursor
How do we handle refund events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via feat/refunds, not staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
Asked by Cursor
How do we handle refund events?
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via feat/refunds, not staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
@priya · feat/refunds
The merge carries the reasoning too.
feat/refunds merges. Priya's lesson moves onto the trunk with the code it describes, so it is there for everyone who branches next rather than only for her.
now on staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
now on staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
@jordan · feat/payouts
Documentation that writes itself.
Each merge leaves its reasoning on staging. The next feature starts with all of it, written by the agents doing the work rather than by someone remembering to write it down.
new memory
Reconcile payouts from the receipts table
A charge total moves when a refund lands early. Receipts do not.
scopesrc/payments/payouts.ts
@jordan · Cursor
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
via staging
Reconcile payouts from the receipts table because a charge total moves after a refund
@jordan · Cursor
via staging
Claim each event in Postgres before enqueueing because retries land on another worker
@sam · Codex
via staging
A refund can arrive before its charge settles because the two events are independent
@priya · Claude Code
via staging
Reconcile payouts from the receipts table because a charge total moves after a refund
@jordan · Cursor
new memory
Reconcile payouts from the receipts table
A charge total moves when a refund lands early. Receipts do not.
scopesrc/payments/payouts.ts
@jordan · Cursor

Stop paying to re-explain the codebase.

Every agent session starts cold: paste the context, restate the decision, re-argue what was settled last month. Memkith serves it instead.

Review pricing

Engineers

LightSteadyHeavy

Most engineers, most days. 20 sessions a week, 6 minutes and 300k tokens of context each.

Estimated savings

$229,632

a year

Engineer time: $139,776; 2,496 hours a year
Token spend: $89,856; 7.8B tokens a year

Your estimate, not our measurement: $ per hour per engineer, and Claude Fable 5 API list at $10 in and $50 out per million tokens.

What engineering teams ask before they adopt.

What does Memkith remember?

Decisions, constraints, failed approaches, review outcomes, and other engineering context, attached to the code it explains.

How is this different from an agent’s built-in memory?

Agent-native memory stays with that tool. Memkith gives supported agents access to shared team memory, so the engineering record remains when the team changes agents.

Which coding agents work with Memkith?

Memkith works over MCP with Cursor, Claude Code, Windsurf, Codex, and Zed.

Who can access team memory?

Shared memory stays inside the team that owns the code. Memories can also be scoped to a repository, branch, file, function, or line.

Review security

How long does setup take, and what does it cost?

Setup is 3 CLI commands. The published plan is free for teams of up to 4 seats, then starts at $15 per user per month.

Review full pricing

Shared memory for your team’s AI coding agents.

Works with the tools your team already uses

Your code does not explain itself.

Decisions

Documentation

Conventions

Memory that moves with every branch and merge.

Lessons land with the code that taught them.

The next feature starts from them.

A branch off a branch inherits both.

The merge carries the reasoning too.

Documentation that writes itself.

Stop paying to re-explain the codebase.

Estimated savings

What engineering teams ask before they adopt.

Supported by

memkith

Shared memory for your team’s AI coding agents.

Works with the tools your team already uses

Your code does not explain itself.

Decisions

Documentation

Conventions

Memory that moves with every branch and merge.

Lessons land with the code that taught them.

The next feature starts from them.

A branch off a branch inherits both.

The merge carries the reasoning too.

Documentation that writes itself.

Stop paying to re-explain the codebase.

Estimated savings

What engineering teams ask before they adopt.

Supported by