agent-beacon README

The project's README from github.com/Asymptote-Labs/agent-beacon. As one markdown file: README.md.

Beacon

GitHub release Homebrew GitHub Workflow Status MIT license Docs Discord

Website · Docs · Discord · Install · Commands

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:

🚀 Quick Start

Beacon is open source and local-first. Interactive endpoint setup signs in through beacon.sh and preselects Beacon Managed, 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. System, package, MDM, and CI installation paths remain noninteractive and account-free.

1. Install Beacon

macOS 
brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon

beacon endpoint install
Linux

Download the .deb or .rpm from the latest release.

sudo apt install ./beacon_<version>_linux_amd64.deb

or:

sudo dnf install ./beacon_<version>_linux_amd64.rpm
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 Managed option does: the wizard says so on the confirm screen, names what your chosen privacy mode sends, and connects the endpoint after the install succeeds. Choose Local to keep everything on this machine, and disconnect any time with beacon endpoint disconnect.

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:

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:

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.

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

Runtime Collection Session Prompt Tool Command File Approval MCP Tokens
Antigravity CLI Hooks ✅ ✅ ✅ ✅ ✅ – – –
Claude Code OTLP + hooks + poll ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Claude Cowork OTLP ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Cline Plugin + poll ✅ ✅ ✅ ✅ ✅ – ✅ ✅
Codex CLI OTLP + hooks + poll ✅ ✅ ✅ ✅ – ✅ – ✅
Codex Desktop OTLP ✅ ✅ ✅ ✅ – ✅ – ✅
Cursor Hooks + poll ✅ ✅ ✅ ✅ ✅ ✅ ✅ –
DeepSeek Harness Hooks + poll ✅ ✅ ✅ ✅ ✅ – ✅ ✅
Devin CLI Hooks ✅ ✅ ✅ ✅ ✅ ✅ ✅ –
Devin Desktop Hooks – ✅ ✅ ✅ ✅ – ✅ –
Factory Droid OTLP + hooks + poll ✅ ✅ ✅ – ✅ ✅ – –
fx (Vercel Labs) Poll ✅ ✅ ✅ ✅ ✅ – ✅ ✅
Gemini CLI OTLP – ✅ ✅ – ✅ ✅ ✅ –
GitHub Copilot CLI OTLP + poll ✅ ✅ ✅ ✅ ✅ ✅ – ✅
goose Adapter only; manual hooks/OTLP ✅ ✅ ✅ ✅ ✅ – ✅ ✅
Grok Build Hooks + poll ✅ ✅ ✅ ✅ ✅ ✅ – –
Hermes Agent Hooks + poll ✅ ✅ ✅ ✅ ✅ ✅ ✅ –
Kimi Code Hooks ✅ ✅ ✅ ✅ ✅ ✅ ✅ –
Kiro Hooks ✅ ✅ ✅ ✅ ✅ – ✅ –
Muse Code Hooks ✅ ✅ ✅ ✅ ✅ ✅ – –
Oh My Pi Extension ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
OpenClaw Gateway Plugin + OTLP + poll ✅ ✅ ✅ ✅ ✅ – ✅ ~
OpenCode Plugin + poll ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
OpenHands Hooks ✅ ✅ ✅ ✅ ✅ – ✅ –
Pi Extension + poll ✅ ✅ ✅ ✅ ✅ – ✅ ✅
Prime Agent Extension + poll ✅ ✅ ✅ ✅ ✅ – – ✅
Qwen Code Hooks ✅ ✅ ✅ ✅ ✅ ✅ – –
Senpi Extension ✅ ✅ ✅ ✅ ✅ – – ✅
VS Code OTLP + hooks ✅ ✅ ✅ ~ ~ – ~ –

Browser Chat

Site Collection Prompt Response Tool Tokens
Claude.ai Chromium + Firefox extension → local OTLP ✅ ✅ ✅ ~
ChatGPT Chromium + Firefox extension → local OTLP ✅ ✅ ✅ –

Cloud Agents

Runtime Collection Session Prompt Tool Command File Tokens
Claude Code Cloud Agents Sandbox hooks → GCS or S3 ✅ ✅ ✅ ✅ ✅ –
Cursor Cloud Agents Sandbox hooks → GCS or S3 – ✅ ✅ ✅ ✅ –
Devin Cloud Agents API poll → GCS ✅ ✅ – – – ✅
CI jobs beacon ci exec → temporary local collector ✅ ✅ ✅ ✅ ✅ ✅

SDK Instrumentation

SDK Surface Collection Captures
Anthropic OpenLLMetry through @asymptote/sdk Model call spans, errors, and OTel attributes
OpenAI OpenLLMetry through @asymptote/sdk Model call spans, errors, and OTel attributes
Claude Agent SDK Observe.wrapClaudeAgentQuery() Query root spans with Beacon-compatible prompt attributes
Vercel AI SDK experimental_telemetry tracer handoff Model 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

Destination Category Support Path
Local JSONL Local Default endpoint log and local dashboard source
Beacon Managed Hosted forwarding Signed-in device enrollment with Standard or Metadata-only privacy
CrowdStrike Falcon LogScale HEC SIEM Endpoint forwarding with LogScale ingest tokens
Microsoft Sentinel SIEM Azure Monitor Agent and Data Collection Rule content pack
Rapid7 InsightIDR SIEM Custom Logs webhook content pack
Splunk HEC SIEM Endpoint forwarding during install or repair
Sumo Logic SIEM HTTP Logs & Metrics Source content pack
Wazuh SIEM Localfile configuration and Beacon content pack
AWS CloudWatch Logs Log aggregation Vector content pack
Datadog Log aggregation Datadog Agent custom log collection
Elastic Log aggregation Filebeat or Elastic Agent
Customer-managed pipelines Log aggregation Forward directly from local Beacon JSONL
AWS S3 Object storage Vector, CI upload, or cloud-agent snapshots
Google Cloud Storage Object storage Vector, 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:

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

agent-beacon (Asymptote-Labs/agent-beacon)

Searching Database…

1.8K ·GitHub
Agent-beacon
What is this?An open-source memory layer for AI coding agents: it captures session history across Claude Code, Cursor, Codex, OpenCode and 20+ other harnesses, then turns useful workflows, corrections and debugging patterns into knowledge future agents can reuse.
So is it a plugin I add to every agent, or one thing installed on my machine?One install per machine. Beacon sits across the harness layer: it captures agent activity where it actually happens (hooks, OTLP, plugins or polling, depending on the tool) and normalizes it into one shared event model.
How do I get it running?Install a package from the latest release — .deb or .rpm on macOS/Linux, an x64 MSI on Windows — and just keep using your agents; Beacon captures history in the background. System, package, MDM and CI installs are noninteractive and account-free.
Which agents does it actually work with?20+ local harnesses including Claude Code, Cursor, Codex, OpenCode, Cline, Gemini CLI, GitHub Copilot CLI, goose, Devin, Kimi Code, Kiro, Qwen Code and Hermes Agent — plus Claude.ai and ChatGPT in the browser via extensions, cloud agents, CI jobs, and Anthropic, OpenAI, Claude Agent SDK and Vercel AI SDK instrumentation.
Does it capture every agent with the same level of detail?No — coverage is per-runtime. Claude Code captures the full set including approvals, MCP activity and tokens, but Codex CLI records no file or MCP activity, Gemini CLI no session or token data, and VS Code support is largely partial, so check the support table for your agent.
Does any of my session data leave my machine?By default everything stays local as JSONL and nothing is sent anywhere. Forwarding starts only after you sign in and explicitly confirm the Beacon Managed option; choosing Local keeps everything on-machine, and beacon endpoint disconnect cuts a connection any time.
Why not just use the memory built into Claude Code or Cursor?Most agent memory belongs to a single harness. Because Beacon normalizes history across tools, knowledge learned through Claude Code can improve Cursor or OpenCode — your history keeps compounding even as you switch tools, and it belongs to you, not the harness.
How do I browse what my agents actually did?A local terminal browser shows traces, event timelines and token usage, and there is also a local read-only web dashboard. The underlying JSONL stays directly accessible, so you are never dependent on the UI.
What exactly does one session trace contain?Prompts and responses, tool calls, commands, file activity, approvals, MCP interactions and token usage — captured where the agent runs and normalized into a common OpenTelemetry-based event model, so every harness produces the same dataset.
What are similar projects?okf-agent-memory, holaOS, lean-ctx, jevmem, OpenAPPA, Agentlas-OS, ai-memory, engram
Which topics is it in?session-replay, agent-security, jev, telemetry, agent-harness, browser-extension, agent-memory, memory, ci, knowledge-base, observability, cursor
Creator
Asymptote-Labs
Size
67.1 MB
Stars
1.8K
Updated
CommitOct 16Releasev1.3.42Oct 16
Age
5mo
Commits · 90 Days