DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to share memory between Claude Code, Codex and Cursor with Agent Beacon

Capture sessions from every coding agent so a fix or correction learned in one is recalled by the next.

Short answer: Paste Read https://beacon.sh/start.md then set me up on Beacon into your coding agent, or on macOS run brew tap asymptote-labs/tap and brew install beacon; then run beacon endpoint install and pick Local to keep history on this machine, or confirm Beacon Cloud; let setup install the Beacon Skills into ~/.agents/skills and ~/.claude/skills, or add them later with beacon skills install. All steps.

Credentials. Beacon records prompts, responses, commands and file edits, so pasted API keys or secrets can end up in the trace. Interactive setup preselects Beacon Cloud, which forwards history to Asymptote Labs once you confirm; choose Local to keep everything on your machine.

Who it is forA developer who corrects the same mistake in Claude Code, then has to correct it again in Codex or Cursor.

The problemEach harness keeps its own memory, so a problem solved by one agent is learned from scratch by another.

The outcomeOne shared project memory that Claude Code, Codex, Cursor and OpenCode can recall through Agent Skills or MCP.

What you need first

  • macOS with Homebrew, Linux (Debian, Ubuntu, Fedora, RHEL, Rocky or Alma, as .deb or .rpm) or Windows x64 (MSI)
  • At least one supported harness, such as Claude Code, Codex CLI, Cursor or OpenCode
  • A beacon.sh sign-in only if you choose Beacon Cloud; Local needs no account
  • For forwarding: an existing destination such as Splunk HEC, Datadog, Elastic, Microsoft Sentinel or an S3 or GCS bucket

Steps

  1. Paste Read https://beacon.sh/start.md then set me up on Beacon into your coding agent, or on macOS run brew tap asymptote-labs/tap and brew install beacon
  2. Run beacon endpoint install and pick Local to keep history on this machine, or confirm Beacon Cloud
  3. Let setup install the Beacon Skills into ~/.agents/skills and ~/.claude/skills, or add them later with beacon skills install
  4. Use Claude Code, Codex or Cursor normally while Beacon captures session history in the background
  5. With Beacon Cloud, run beacon mcp connect to register the beacon-managed MCP server in Claude Code, Codex CLI, Cursor, VS Code, Gemini CLI and OpenCode; locally, beacon mcp serve never touches the network

Prompt for your agent

Set me up on Asymptote-Labs/agent-beacon using the Local destination, install the Beacon Skills, and confirm that a session in <harness A> shows up in `beacon traces`. Then, in <harness B>, recall what Beacon learned about <project task> and tell me which past session it came from.

Caveat. Knowledge goes through a review and approve step before agents reuse it, so expect to curate what Beacon extracts rather than get perfect memory on day one.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for Asymptote-Labs/agent-beacon and "Share memory between Claude Code, Codex and Cursor"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer