merkhain

what happens in context stays in context

Give your agents the context to work faster, spend fewer tokens, and avoid repeating mistakes.

merkhain remembers what you and your agents learn about a codebase. The next agent can use those findings—even in a different tool, on another computer, or working with a teammate.

Claude Code · Codex · OpenCode · pi

Across agents. Across devices. Across your team.

End-to-end encrypted sync. Your devices hold the keys.

Where do you need your memory?

Stays on this device

Just this computer

Your agents remember past work on this device. No server or sync needed.

Start locally
Only your devices

My computers

Start on your desktop. Pick up on your laptop. Your agents keep the context.

Connect your devices
The teammates you invite

Our team

Your agent learns something. Your teammate’s agent can use it. Share the projects you choose.

Connect your team

Sync is end-to-end encrypted. Only devices with the right private keys can read the memories. Self-host your sync ↓

An incident, with shared memory

Two engineers. One investigation.

Checkout is failing. Alice and Ben ask their agents to help.

Alice’s laptop → merkhain → Ben’s laptop
  1. Alice + Claude Code

    INVESTIGATION

    Payment ✓ succeeded

    Receipt email ✕ timed out

    FindingPayment went through.
    The receipt email caused the error.

    Alice’s agent traces the failure and finds the cause.

  2. merkhain · end-to-end encrypted

    Shared memoryPayment went through.
    The receipt email caused the error.

    Automatically recalled by Ben’s agent

    merkhain delivers the finding to Ben’s agent. No copy-paste.

  3. Ben + Codex

    CONTEXT FROM ALICE’S AGENT

    “The receipt email caused the error.”

    Codex“I’ll fix the email error path so checkout still succeeds.”

    ↳ Investigation already done

    Ben’s agent uses the finding and goes straight to the fix.

Find it once. Use it together.Fewer repeated tool calls. Fewer tokens. Faster fixes.

Illustrative workflow with team sharing and automatic recall enabled.

Private by default. Self-hosted when shared.

Your sessions contain sensitive work.
Your memory deserves privacy.

Prompts and coding sessions can contain private code, customer details, and internal decisions. merkhain keeps raw conversations out of sync and encrypts every shared memory end to end.

01

Share project knowledge.

Choose which projects to sync or share. Sync carries extracted notes, not raw conversations. Joining a team doesn’t automatically publish your own work.

02

End-to-end encrypted.

Your memories are end-to-end encrypted when synced between devices or shared with your team. Only authorized devices holding the required private keys can decrypt them. The merkhain sync server cannot read your memories.

03

Run sync yourself.

Host a relay on your infrastructure for your team. For personal sync, you can also use one of your computers over Tailscale. Local memory keeps working when the sync host is offline; queued notes sync when it returns.

Read the sharing and hosting guide →

Give the next agent a head start

Keep the discovery.
Skip the repeat.

Start with memory on your computer. Connect your other devices or your team when you’re ready.