claudeers.
// Uncategorized / Others

agent-beacon

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

// Uncategorized / Others[ cli ][ api ][ desktop ][ web ][ mobile ][ claude ]#claude#agent-ai-cli#agent-harnesses#agent-security#browser-extension#ci#claude-code#cloud#uncategorized◷ MIT$open-sourceupdated 25 days ago
Actively maintained
100/100
last commit 9 days ago
last release 10 days ago
releases 177
open issues 6

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up agent-beacon (claude-plugin project) into my current project.
Found on https://claudeers.com/agent-beacon
Repo: https://github.com/Asymptote-Labs/agent-beacon
Homepage/docs: https://beacon.sh
Detected install method: claude-plugin → /plugin install agent-beacon@Asymptote-Labs/agent-beacon
Category: uncategorized. Platforms: cli, api, desktop, web, mobile.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
active; community-verified: false. Confirm the source before running anything.
// or install directly (claude-plugin)
/plugin marketplace add Asymptote-Labs/agent-beacon
/plugin install agent-beacon@Asymptote-Labs/agent-beacon
// or clone
git clone https://github.com/Asymptote-Labs/agent-beacon

// compatibility

Platformscli, api, desktop, web, mobile
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguageGo

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

Beacon Beacon

Self‑improving memory for coding agents

Website · Docs · Discord · Install · Commands

GitHub Trending Repository of the Day

Beacon captures agent session history across Claude Code, Cursor, Codex, OpenCode, and 20+ other harnesses, then turns useful workflows, corrections, and debugging patterns into reusable knowledge for future agents.

A problem solved by one agent shouldn't need to be learned from scratch by another.


Beacon Overview

Beacon is an open-source memory layer for AI coding agents that learns from your work across Claude Code, Cursor, Codex, OpenCode, and 20+ other harnesses. It captures full session history, identifies useful workflows, corrections, and debugging patterns, and makes that knowledge reusable by future agents. Built for developers who want agent knowledge to compound across tools instead of disappearing when a session ends.

Key Capabilities:

  • Cross-harness history - sessions from Claude Code, Cursor, Codex, OpenCode, Cline, and 20+ harnesses in one place
  • Knowledge that compounds - workflows, corrections, debugging patterns, and repo conventions that survive beyond a single session
  • Shared agent memory - reviewed knowledge future agents can retrieve through MCP or Agent Skills
  • Exact session replay - prompts, responses, tools, commands, edits, approvals, MCP activity, and tokens in one trace
  • Local-first portability - durable JSONL, explicit destinations, and no harness lock-in

🎬 Demo

https://github.com/user-attachments/assets/38995612-84e9-4989-a905-0099f77955f0


🚀 Quick Start

Beacon is open source and local-first. Interactive endpoint setup signs in through beacon.sh and preselects Beacon Cloud, with an explicit Local opt-out. Signing in forwards nothing; confirming Managed installs Beacon and connects this machine in the same command, and the confirm screen says so before you accept. Setup then ends on a short summary and opens the hosted dashboard at beacon.sh/dashboard. System, package, MDM, and CI installation paths remain noninteractive and account-free.

1. Install Beacon

Copy & paste setup prompt into your coding agent

Read https://beacon.sh/start.md then set me up on Beacon
macOS
brew update
brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon

beacon endpoint install
Linux

Install the latest .deb or .rpm for your distribution and architecture (Debian, Ubuntu, Fedora, RHEL, Rocky, Alma):

curl -fsSL https://github.com/asymptote-labs/agent-beacon/releases/latest/download/install.sh | bash

The installer downloads the package for your architecture, verifies it against the release checksums.txt, and installs it with apt-get or dnf. Set BEACON_VERSION=<version> to install a specific release.

Prefer not to pipe a script into your shell? Either read the script before you run it:

curl -fsSLO https://github.com/asymptote-labs/agent-beacon/releases/latest/download/install.sh
less install.sh
bash install.sh

Or skip the script and run its steps yourself: pick a version, download the package and checksums.txt, verify the package, and install it with your package manager.

VERSION="$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/asymptote-labs/agent-beacon/releases/latest)"; VERSION="${VERSION##*/v}"
case "$(uname -m)" in x86_64) ARCH=amd64 ;; aarch64) ARCH=arm64 ;; esac
FORMAT=deb   # or rpm for Fedora, RHEL, Rocky, Alma
PKG="beacon_${VERSION}_linux_${ARCH}.${FORMAT}"
BASE="https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}"

# Download into a directory APT can read. A package in your home directory still
# installs, but APT ends with a harmless "Permission denied" notice.
DIR="$(mktemp -d /tmp/beacon-install.XXXXXXXX)" && chmod 0711 "$DIR" && cd "$DIR"
curl -fsSLO "${BASE}/${PKG}" && curl -fsSLO "${BASE}/checksums.txt" && chmod 0644 "${PKG}"
grep "  ${PKG}$" checksums.txt | sha256sum --check - && \
sudo apt install "./${PKG}"   # or: sudo dnf install "./${PKG}"

checksums.txt is published with the release, so it catches a corrupted or swapped download but does not prove who built the release. To check that, verify the package's build-provenance attestation, which shows it was built by this repository's release workflow: gh attestation verify "${PKG}" --repo asymptote-labs/agent-beacon. You can also pin VERSION to a release you have reviewed instead of following latest. To install without root, use the tarball in user mode (Linux install guide).

Windows

Download the x64 MSI from the latest release.

msiexec /i BeaconEndpointAgent-<version>-x64.msi

For silent installation:

msiexec /i BeaconEndpointAgent-<version>-x64.msi /qn

2. Use your agents normally

Open Claude Code, Cursor, Codex, or any other supported harness.

Beacon continuously captures your session history in the background

3. Explore your history

beacon traces

This opens a local terminal browser for traces, event timelines, token usage, and retained content. Nothing is sent anywhere. To use the local web view instead:

beacon endpoint dashboard

Or inspect the raw event stream:

~/.beacon/endpoint/logs/runtime.jsonl

[!NOTE] Signing in does not enable forwarding. Confirming the preselected Beacon Cloud option does: the confirm screen names the signed-in account, states that confirming installs Beacon and starts forwarding, names Asymptote Labs as the operator, the destination, and the capture mode, and connects the endpoint after the install succeeds. Choose Local to keep everything on this machine, and disconnect any time with beacon endpoint disconnect.

Whichever destination you choose, the wizard also installs the Beacon Skills into ~/.agents/skills and ~/.claude/skills unless you turn them off; redo or undo that with beacon skills install|uninstall.

If you choose Beacon Cloud, the wizard also registers Beacon Cloud MCP in your harnesses unless you turn it off, so your agents can search the forwarded history. To do it later, or for an endpoint connected another way:

beacon mcp connect

This registers the beacon-managed MCP server in Claude Code, Codex CLI, Cursor, VS Code, Gemini CLI, and OpenCode, and each harness signs in with OAuth the first time it connects. No token is written. beacon mcp disconnect removes exactly what it added. The local beacon MCP server (beacon mcp serve) is separate and never touches the network. See beacon mcp connect.

Inspect the account used during interactive setup:

beacon whoami

🧠 Turn Session History Into Memory

Every agent session contains potentially useful knowledge about your codebase.

Beacon creates a loop around that history:

Run agents
    ↓
Capture session history
    ↓
Evaluate what worked
    ↓
Extract useful knowledge
    ↓
Review + approve
    ↓
Reuse across future agents

That could be:

  • the right way to run a migration
  • a debugging path that finally fixed an obscure issue
  • a testing convention agents repeatedly get wrong
  • a repository-specific workflow
  • the right sequence of internal tools
  • a correction you've given multiple agents

Instead of disappearing into old sessions, that knowledge becomes reusable.


🔀 Cross-Harness by Design

Most agent memory belongs to a single harness.

Beacon sits across the harness layer.

Claude Code ─┐
Cursor ──────┤
Codex ───────┼──→ Beacon ──→ shared project knowledge
OpenCode ────┤
Cline ───────┘

Because Beacon captures and normalizes session history across tools, knowledge learned through Claude Code doesn't have to stay in Claude Code.

Your Cursor sessions can improve Codex.
Your Codex sessions can improve OpenCode.
Your history keeps compounding even as you switch tools.

Your agent session history belongs to you, not the harness.


🔎 One Trace Format for Every Agent

Beacon captures agent execution where it happens and normalizes it into a common OpenTelemetry-based event model.

That includes:

  • sessions
  • prompts and responses
  • tool calls
  • commands
  • file activity
  • approvals
  • MCP interactions
  • token usage

Instead of separate proprietary histories for every coding tool, you get one dataset you can inspect, search, learn from, and build on.


🖥️ Local Dashboard

Beacon ships with a local, read-only dashboard:

beacon endpoint dashboard

Use it to explore session history across harnesses and understand what your agents actually did.

Each session page can also show lenses: purpose-built views of one trace, such as files changed with their diffs, an itemized token bill, a security review grouped by risk, or the approval timeline. A lens is a single HTML file running in a sandboxed frame with no access to Beacon or the dashboard and no ordinary network APIs, so you can have your coding agent write your own (beacon lenses spec, lint, preview, add). The sandbox cannot block every way a browser can send data out, so install only lenses you trust with your traces. See Lenses.

The underlying JSONL remains directly accessible, so you're never dependent on the UI.


Supported Agents

Beacon supports local agents, browser agents, cloud agents, CI workflows, and agent SDKs.

Local Agent Coverage

RuntimeCollectionSessionPromptToolCommandFileApprovalMCPTokensSkills
Antigravity CLIHooks✅✅✅✅✅–––✅ skills CLI
Claude CodeOTLP + hooks + poll✅✅✅✅✅✅✅✅✅ Plugin
Claude CoworkOTLP✅✅✅✅✅✅✅✅✅ Plugin
ClinePlugin + poll✅✅✅✅✅–✅✅✅ .cline/skills
Codex CLIOTLP + hooks + poll✅✅✅✅–✅–✅✅ Plugin
Codex DesktopOTLP✅✅✅✅–✅–✅✅ Plugin
CursorHooks + poll✅✅✅✅✅✅✅–✅ Plugin
DeepSeek HarnessHooks + poll✅✅✅✅✅–✅✅✅ .agents/skills
Devin CLIHooks + poll✅✅✅✅✅✅✅✅✅ Plugin
Devin DesktopHooks–✅✅✅✅–✅–✅ via Devin CLI
Factory DroidOTLP + hooks + poll✅✅✅–✅✅––✅ Plugin
fx (Vercel Labs)Poll✅✅✅✅✅–✅✅✅ /skills install
Gemini CLIOTLP–✅✅–✅✅✅–✅ gemini skills install
GitHub Copilot CLIOTLP + poll✅✅✅✅✅✅–✅✅ Plugin
gooseAdapter only; manual hooks/OTLP✅✅✅✅✅–✅✅✅ skills CLI
Grok BuildHooks + poll✅✅✅✅✅✅––✅ Plugin
Hermes AgentHooks + poll✅✅✅✅✅✅✅–✅ hermes skills install
Kimi CodeHooks✅✅✅✅✅✅✅–✅ Plugin
KiroHooks✅✅✅✅✅–✅–✅ Power
Muse CodeHooks✅✅✅✅✅✅––✅ .agents/skills
Oh My PiExtension✅✅✅✅✅✅✅✅✅ Plugin
OpenClaw GatewayPlugin + OTLP + poll✅✅✅✅✅–✅~✅ Plugin
OpenCodePlugin + poll✅✅✅✅✅✅✅✅✅ skills CLI
OpenHandsHooks✅✅✅✅✅–✅–✅ skills CLI
PiExtension + poll✅✅✅✅✅–✅✅✅ Package
Prime AgentExtension + poll✅✅✅✅✅––✅✅ Package
Qwen CodeHooks✅✅✅✅✅✅––✅ Plugin
SenpiExtension✅✅✅✅✅––✅✅ .agents/skills
VS CodeOTLP + hooks✅✅✅~~–~–✅ Plugin

Skills shows how to install Beacon Skills, the Agent Skills that recall and distill project memory from these traces. Every runtime above loads Agent Skills:

  • Plugin: install the beacon plugin from this repository's marketplace, for example /plugin marketplace add asymptote-labs/agent-beacon in Claude Code.
  • Package (Pi, Prime Agent): pi install git:github.com/asymptote-labs/agent-beacon.
  • Power (Kiro): import https://github.com/asymptote-labs/agent-beacon/tree/main/agent-skills from the Powers panel.
  • skills CLI: npx skills add asymptote-labs/agent-beacon, optionally with -a <agent>.
  • A directory: copy agent-skills/skills/* into that project directory.

The Beacon Skills page has the exact command for each runtime.

Browser Chat

SiteCollectionPromptResponseToolTokens
Claude.aiChromium + Firefox extension → local OTLP✅✅✅~
ChatGPTChromium + Firefox extension → local OTLP✅✅✅–

Cloud Agents

RuntimeCollectionSessionPromptToolCommandFileTokens
Claude Code Cloud AgentsSandbox hooks → GCS or S3✅✅✅✅✅–
Cursor Cloud AgentsSandbox hooks → GCS or S3–✅✅✅✅–
Devin Cloud AgentsAPI poll → GCS✅✅–––✅
CI jobsbeacon ci exec → temporary local collector✅✅✅✅✅✅

SDK Instrumentation

SDK SurfaceCollectionCaptures
AnthropicOpenLLMetry through @asymptote/sdkModel call spans, errors, and OTel attributes
OpenAIOpenLLMetry through @asymptote/sdkModel call spans, errors, and OTel attributes
Claude Agent SDKObserve.wrapClaudeAgentQuery()Query root spans with Beacon-compatible prompt attributes
Vercel AI SDKexperimental_telemetry tracer handoffModel call and tool spans where telemetry is enabled

Output Destinations

Beacon writes endpoint telemetry to local JSONL by default.

You can also forward the same normalized session history into infrastructure you already use:

Splunk · Datadog · Elastic · Microsoft Sentinel · CrowdStrike Falcon LogScale · Sumo Logic · Wazuh · AWS S3 · GCS · CloudWatch

DestinationCategorySupport Path
Local JSONLLocalDefault endpoint log and local dashboard source
Beacon CloudHosted forwardingSigned-in device enrollment with Standard or Metadata-only privacy
CrowdStrike Falcon LogScale HECSIEMEndpoint forwarding with LogScale ingest tokens
Microsoft SentinelSIEMAzure Monitor Agent and Data Collection Rule content pack
Rapid7 InsightIDRSIEMCustom Logs webhook content pack
Splunk HECSIEMEndpoint forwarding during install or repair
Sumo LogicSIEMHTTP Logs & Metrics Source content pack
WazuhSIEMLocalfile configuration and Beacon content pack
AWS CloudWatch LogsLog aggregationVector content pack
DatadogLog aggregationDatadog Agent custom log collection
ElasticLog aggregationFilebeat or Elastic Agent
Customer-managed pipelinesLog aggregationForward directly from local Beacon JSONL
AWS S3Object storageVector, CI upload, or cloud-agent snapshots
Google Cloud StorageObject storageVector, CI upload, or cloud-agent snapshots

Architecture

Beacon captures activity where agents actually run and normalizes it into one shared event model.

Local agents ───────┐
Browser chat ───────┤
CI ─────────────────┼──→ Beacon ──→ unified session history
Cloud agents ───────┤                    │
Agent SDKs ─────────┘                    ├──→ local JSONL
                                         ├──→ reviewed memory
                                         ├──→ MCP / Agent Skills
                                         └──→ your own infrastructure

See the documentation for the full architecture breakdown.


Documentation

Read the docs for:

  • installation
  • supported runtimes
  • event schema
  • session history
  • memory
  • MCP
  • Agent Skills
  • forwarding
  • advanced configuration

Read the docs →


Contributing

Contributions are welcome.

Open an issue, submit a pull request, or join the Discord.


License

MIT

Star History

Star History Chart

// faq

What is agent-beacon?

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu. It is open-source on GitHub.

Is agent-beacon free to use?

agent-beacon is open-source under the MIT license, so it is free to use.

What category does agent-beacon belong to?

agent-beacon is listed under uncategorized in the Claudeers registry of Claude-compatible tools.

22 views
★ 3,406 stars
unclaimed
updated 25 days ago

// embed badge

agent-beacon on Claudeers
[![Claudeers](https://claudeers.com/api/badge/agent-beacon.svg)](https://claudeers.com/agent-beacon)

// retro hit counter

agent-beacon hit counter
[![Hits](https://claudeers.com/api/counter/agent-beacon.svg)](https://claudeers.com/agent-beacon)

// reviews

// guestbook

0/500

// related in Uncategorized / Others

🔓

Reverse engineer anything with agents, from app behavior down to native binaries.

// uncategorizedmorluto/⟨TypeScript⟩★ 423,040◷ MIT[ claude ]
🔓

Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.

// uncategorizedn8n-io/⟨TypeScript⟩★ 209,482◷ NOASSERTION[ claude ]
🔓

The agent engineering platform.

// uncategorizedlangchain-ai/⟨Python⟩★ 148,973◷ MIT[ claude ]
🔓

100+ AI Agent & RAG apps you can actually run — clone, customize, ship.

// uncategorizedShubhamsaboo/⟨Python⟩★ 144,747◷ Apache-2.0[ claude ]

// built by

2 of its contributors also build on official projects — claude-code, claude-cookbooks, claude-plugins-official, inspector

→ see how agent-beacon connects across the ecosystem