Product/Coding-agent memory

The next coding agent startswhere the last one stopped.

A small sync tool reads your Claude Code, Codex, Gemini CLI, Grok and Muse sessions into the right workspace, so whichever agent opens the repo next already knows the decisions, dead ends and fixes.

Start freeTalk to us

Free tier, no card required.

NNorthwind Live
Example data
# Sam's work laptop, set up for Northwind
$ npx @meshtale/agent-sync status
Discovered: 8
Already synced: 2
Pending: 6
$ npx @meshtale/agent-sync sync-now
Uploaded: 5
Skipped: 1 (kestrel-api, not chosen for Northwind)
Failed: 0
Arrived in Northwindauthored by AI tools
    Codexnorthwind-portal · today, new session
    Sam asks
    • recall · northwind
    • 3 cited pieces, within budget
    • recall logged
    Northwind only

    Keep per-line rounding. A Claude Code session yesterday switched to it because per-invoice rounding put totals a cent off Northwind's ledger1, and Priya's ticket confirms the client asked for it2. Streaming the CSV was already tried and dropped3.

    1by Claude Code·sessionyesterday
    2by Priya·Linear issueMon
    3by Gemini CLI·sessionlast week
    Codex never saw yesterday's session. MeshTale did.
    Northwind workspace · sessions keep their AI author and their projectIllustrative product animation

    What one session learns,the next one can recall.

    A coding session is full of things nobody writes down: why a choice was made, what was tried and failed, what finally fixed it. MeshTale keeps them as memories with the AI tool as the author, next to what your people write.

    Decision
    Claude CodeRound invoices per lineby Claude CodeAI

    Matches the client's ledger. The old rounding stays behind a flag for March reports.

    approved by Priya

    Decisions, with the reason

    So the next agent does not quietly undo a choice that was made on purpose.

    Dead end
    Gemini CLIStreaming the CSV exportby Gemini CLIAI

    Broke the totals row in their accounting import. Reverted, kept the buffered writer.

    approved by Sam

    Dead ends, so nobody walks them twice

    What was tried, why it failed, and what was kept instead.

    Fix
    GrokWebhook retries need a backoffby GrokAI

    Their gateway rate-limits bursts. Retries now wait longer each time.

    approved by Dana

    Fixes, findable by the error

    Exact-match search finds the error string, meaning-based search finds the same problem described differently.

    Synced sessions get no shortcut,the workspace rules still apply.

    A coding session can hold a client's details, a pasted key or a half-right guess. So synced sessions land in the workspace you set the sync up for, and wait for review when the workspace asks for it.

    • You choose which projects on each computer get imported
    • Team workspaces can hold new sessions for a person's OK
    • Credentials in a session are masked before it is stored
    • Audience and sensitivity rules apply to every recall, and every recall is logged
    See governance and review
    Review queue · Northwind
    Example data
    • Claude CodeInvoice export: round per lineby Claude Code·Sam's laptopApproveReject
    • CodexNightly sync moved to 02:00by Codex·Sam's laptopApproved
    • GrokWebhook retries need a backoffby Grok·Marco's desktop1 key masked
    • GWebhook outage call notesby Dana·Granola callApproved
    Sessions and people's notes in one queueIllustrative

    One line to read memory,one line to start the sync.

    Add MeshTale to your agent over MCP and it gets two tools for recall. Run the sync once on each computer and new sessions flow in after that.

    Recall from your agent
    $ claude mcp add meshtale
Connected. 2 tools registered.
  recall · recall_context_bundle

    Works the same way in any tool that speaks MCP.

    Sync your sessions
    $ npx @meshtale/agent-sync init
Open MeshTale to choose what to import
Installed meshtale-agent-sync.

    Claude Code sessions sync when a session ends. The others are picked up by a scheduled rescan.

    Tools that work with MeshTale

    Claude Code Codex Gemini CLI Grok Muse Cursor Windsurf ZZed Devin Any MCP tool

    Sessions sync from Claude Code, Codex, Gemini CLI, Grok and Muse. Recall works in all of these.

    Questions

    Claude Code, Codex, Gemini CLI, Grok and Muse. It reads their session histories and memory files from the folders those tools keep in your home directory, and you can add another folder you have reviewed.

    No. It looks only in those agent folders, and you choose in MeshTale which projects to import. You can also choose how far back to go (all, one year, six months or 30 days) and whether to include full session transcripts.

    Each computer gets its own setup command from the workspace you want it to feed, and that workspace is where its sessions land. Projects you have not chosen for that workspace are skipped.

    No. They follow the same review, audience and sensitivity rules as anything else in the workspace, and credentials found in a session are masked before it is stored.

    Any tool that speaks MCP, including Claude Code, Codex, Cursor, Windsurf, Zed, Gemini, Grok and Devin. In Claude Code it is one command: claude mcp add meshtale.

    Stop re-explaining your codebase,to every new session.

    Create a workspace, run the sync once, and let the next agent pick up where the last one left off.

    Start freeTalk to us
    Free tier, no card required.