Skip to content

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

refresh docs

Justin D'Souza818b0a2cb10b
diff --git a/docs/architecture/architecture.mdx b/docs/architecture/architecture.mdx
index 16cb09e2..c9dfd3da 100644
--- a/docs/architecture/architecture.mdx
+++ b/docs/architecture/architecture.mdx
@@ -1,13 +1,13 @@
---
title: "Open Source Architecture"
-description: "How Agent Beacon collects, normalizes, stores, correlates, and detects agent telemetry across every surface agents run on"
+description: "How Beacon collects, normalizes, stores, correlates, and detects agent telemetry across every surface agents run on"
---
## Overview
-Agent Beacon is the open-source telemetry layer for AI agents wherever they run: on laptops, in the browser, inside application code, in [CI](/concepts/core-concepts#ci-telemetry), and in [provider-managed cloud sandboxes](/concepts/core-concepts#cloud-agent-telemetry). Each surface reports activity differently, so Beacon extends OpenTelemetry where a runtime emits it and instruments custom hooks, plugins, and adapters where it does not, then normalizes what it captures into a single [event model](/telemetry-schema/event-schema).
+Beacon is the open-source telemetry layer for AI agents wherever they run: on laptops, in the browser, inside application code, in [CI](/concepts/core-concepts#ci-telemetry), and in [provider-managed cloud sandboxes](/concepts/core-concepts#cloud-agent-telemetry). Each surface reports activity differently, so Beacon extends OpenTelemetry where a runtime emits it and instruments custom hooks, plugins, and adapters where it does not, then normalizes what it captures into a single [event model](/telemetry-schema/event-schema).
-<img src="/images/beacon-architecture.png" alt="Agent Beacon architecture. Six source surfaces (local agents, browser, agents in code, CI pipelines, cloud agents, and third-party AI SaaS) feed a Beacon layer that collects, normalizes, stores, correlates, and detects. The resulting unified AI telemetry flows to observability, SIEM, search, data platform, object storage, and security platform destinations." />
+<img src="/images/beacon-architecture.png" alt="Beacon architecture. Six source surfaces (local agents, browser, agents in code, CI pipelines, cloud agents, and third-party AI SaaS) feed a Beacon layer that collects, normalizes, stores, correlates, and detects. The resulting unified AI telemetry flows to observability, SIEM, search, data platform, object storage, and security platform destinations." />
The diagram reads top to bottom in three bands:
@@ -41,7 +41,7 @@ Chat activity on supported sites is collected by an optional Chrome extension th
### Agents in code
-Agent applications, services, workers, and serverless functions are instrumented with the [Asymptote Observe SDK](/sdk), which emits Beacon-compatible OpenTelemetry spans for model calls, tool calls, and agent steps. There is no endpoint agent in this path: the SDK exports to a customer-managed collector or to hosted Observe. See [SDK integrations](/sdk/integrations).
+Agent applications, services, workers, and serverless functions are instrumented with the [Beacon Observe SDK](/sdk), which emits Beacon-compatible OpenTelemetry spans for model calls, tool calls, and agent steps. There is no endpoint agent in this path: the SDK exports to a customer-managed collector or to hosted Observe. See [SDK integrations](/sdk/integrations).
### CI pipelines
@@ -158,7 +158,7 @@ Beacon collects agent runtime telemetry and local endpoint configuration context
<Card title="Detections" icon="radar" href="/detections">
Run threat rules over local telemetry and review findings.
</Card>
- <Card title="Managed architecture" icon="cloud" href="/architecture/managed-architecture">
- See how Asymptote Managed centralizes telemetry, policy, detections, and investigations.
+ <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ Review managed ingest, governance, investigations, and rollout support.
</Card>
</Columns>
diff --git a/docs/architecture/managed-architecture.mdx b/docs/architecture/managed-architecture.mdx
deleted file mode 100644
index 136133f4..00000000
--- a/docs/architecture/managed-architecture.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: "Managed Architecture"
-description: "How Asymptote Managed centralizes agent telemetry, policy, detections, and investigations"
----
-
-## Overview
-
-Asymptote Managed builds on the open-source Agent Beacon foundation with hosted ingest, retention, search, detections, policy controls, identity mapping, approvals, and investigation workflows.
-
-Use this architecture when agent activity needs to be visible across teams, endpoints, cloud agent applications, and security workflows from one managed control plane.
-
-<img src="/images/asymptote-platform-diagram.png" alt="Asymptote platform architecture showing agent activity flowing into managed visibility, policy, and investigation workflows." />
-
-## System architecture
-
-1. **Agent activity sources:** Endpoint agent harnesses, cloud-hosted agent applications, services, workers, serverless functions, and other execution environments produce runtime telemetry.
-2. **Collection paths:** Agent Beacon collects local endpoint activity, while the Asymptote Observe SDK instruments cloud-hosted agent applications.
-3. **Managed ingest:** Asymptote centralizes telemetry for managed retention, search, detections, and fleet-wide visibility.
-4. **Governance layer:** Policy controls, identity mapping, approvals, SSO, RBAC, and audit trails connect runtime activity to users, teams, and security workflows.
-5. **Investigation workflows:** Timelines and case workflows organize prompts, tool calls, file access, command execution, and related context for review.
-
-## How endpoint telemetry reaches Asymptote
-
-Beacon on the endpoint stays a local JSONL producer. `beacon endpoint connect` adds the managed path:
-
-1. **Approval.** The CLI registers the machine's hostname, OS and Beacon version and opens the dashboard's approval page. A member of the organization signs in with Clerk, picks the organization, and clicks Approve. Only organizations Asymptote has enabled for managed ingest can approve devices.
-2. **Device key.** The CLI redeems a one-time code with a PKCE verifier and receives a key for this one device. The key is stored in a `0600` secrets file and read only by Vector; it is never in Beacon's config or the process environment. Revoking the device, or removing the approving user from the organization, invalidates it within about a minute.
-3. **Forwarding.** A Vector service tails `runtime.jsonl` (from the point of approval) and `inventory_state.jsonl` and POSTs gzip NDJSON batches to Asymptote's ingest service with the device key. A disk buffer covers offline periods.
-4. **Ingest.** The service verifies the key, the approver's membership and the organization's enablement, validates each line, stamps a `tenant` block (organization, device, approving user, receive time) server-side, and writes one object per batch under `orgs/<organization>/<stream>/date=…/` in Asymptote's bucket.
-5. **Per-organization tables.** Each object triggers a notification; the organization's own ClickPipe loads it into that organization's ClickHouse tables. The dashboard resolves an organization to its tables through a mapping row, so tenant isolation is a table boundary, and duplicates from retried batches collapse on Beacon's deterministic event id.
-
-## Managed capabilities
-
-| Capability | Purpose |
-| --- | --- |
-| Managed ingest and retention | Centralize runtime telemetry and preserve it according to managed retention policy |
-| Fleet-wide visibility | Track agent harnesses, endpoints, users, teams, and cloud execution environments |
-| Search and detections | Find risky activity and surface detection signals across the managed dataset |
-| Policy and approvals | Govern agent actions and connect approvals back to identity and workflow context |
-| Investigation timelines | Reconstruct agent sessions from prompts, tool calls, files, commands, and outcomes |
-| Access control | Use SSO, RBAC, and audit trails for enterprise access governance |
-
-## Related
-
-<Columns cols={2}>
- <Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">
- Review the local-first Agent Beacon architecture.
- </Card>
- <Card title="Asymptote Managed" icon="key" href="/deployment/managed">
- Review managed ingest, governance, investigations, and rollout support.
- </Card>
- <Card title="Asymptote Observe SDK" icon="code" href="/sdk/quickstart">
- Instrument cloud-hosted agent applications with Asymptote telemetry.
- </Card>
- <Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
- Compare Open Source, Managed, and Private Deployment paths.
- </Card>
-</Columns>
diff --git a/docs/architecture/system-architecture.mdx b/docs/architecture/system-architecture.mdx
index 016d3e77..dd949cc8 100644
--- a/docs/architecture/system-architecture.mdx
+++ b/docs/architecture/system-architecture.mdx
@@ -1,16 +1,16 @@
---
title: "System Architecture"
-description: "Compare the open-source Agent Beacon architecture with the managed Asymptote platform architecture"
+description: "Compare the open-source Agent Beacon architecture with the managed Beacon platform architecture"
---
-Asymptote supports two architecture paths: the open-source [Agent Beacon](/concepts/core-concepts#agent-beacon) architecture, which collects local, browser, in-code, [CI](/concepts/core-concepts#ci-telemetry), and [cloud telemetry](/concepts/core-concepts#cloud-agent-telemetry) on customer-controlled infrastructure, and the [Asymptote Managed](/concepts/core-concepts#asymptote-managed) architecture for centralized visibility, governance, detections, and investigations.
+Beacon supports two architecture paths: the open-source [Agent Beacon](/concepts/core-concepts#agent-beacon) architecture, which collects local, browser, in-code, [CI](/concepts/core-concepts#ci-telemetry), and [cloud telemetry](/concepts/core-concepts#cloud-agent-telemetry) on customer-controlled infrastructure, and the [Beacon Managed](/concepts/core-concepts#beacon-managed) architecture for centralized visibility, governance, detections, and investigations.
<Columns cols={2}>
<Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">
See how Agent Beacon collects, normalizes, stores, correlates, and detects agent telemetry across every supported surface.
</Card>
- <Card title="Managed Architecture" icon="cloud" href="/architecture/managed-architecture">
- See how Asymptote Managed centralizes telemetry, policy, detections, and investigation workflows.
+ <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ Review managed ingest, governance, investigations, and rollout support.
</Card>
</Columns>
@@ -18,8 +18,8 @@ Asymptote supports two architecture paths: the open-source [Agent Beacon](/conce
| Architecture | Use when |
| --- | --- |
-| Open Source Architecture | You want [open-source telemetry](/concepts/core-concepts#asymptote-open-source) for supported local, CI, and cloud agent surfaces, with customer-controlled records and forwarding. |
-| Managed Architecture | You want [managed ingest](/concepts/core-concepts#asymptote-managed), retention, search, detections, fleet visibility, policy controls, identity mapping, approvals, SSO, RBAC, audit trails, and investigation workflows. |
+| Open Source Architecture | You want [open-source telemetry](/concepts/core-concepts#beacon) for supported local, CI, and cloud agent surfaces, with customer-controlled records and forwarding. |
+| Managed Architecture | You want [managed ingest](/concepts/core-concepts#beacon-managed), retention, search, detections, fleet visibility, identity mapping, approval visibility, SSO, RBAC, audit trails, and investigation workflows. |
## Related
@@ -28,6 +28,6 @@ Asymptote supports two architecture paths: the open-source [Agent Beacon](/conce
Choose between Open Source, Managed, and Private Deployment paths.
</Card>
<Card title="Core Concepts" icon="book-open" href="/concepts/core-concepts">
- Review the concepts used across Asymptote and Agent Beacon docs.
+ Review the concepts used across Beacon and Agent Beacon docs.
</Card>
</Columns>
diff --git a/docs/blog/asymptote-achieves-soc-2-type-ii-compliance.mdx b/docs/blog/asymptote-achieves-soc-2-type-ii-compliance.mdx
index 7ddf2997..4fe87237 100644
--- a/docs/blog/asymptote-achieves-soc-2-type-ii-compliance.mdx
+++ b/docs/blog/asymptote-achieves-soc-2-type-ii-compliance.mdx
@@ -1,4 +1,4 @@
---
-title: "Asymptote Achieves SOC 2 Type II Compliance"
+title: "Beacon Achieves SOC 2 Type II Compliance"
url: "https://asymptotelabs.ai/blog/asymptote-achieves-soc-2-type-ii-compliance"
---
diff --git a/docs/blog/index.mdx b/docs/blog/index.mdx
index d87adbd1..87ede24d 100644
--- a/docs/blog/index.mdx
+++ b/docs/blog/index.mdx
@@ -1,21 +1,21 @@
---
-title: "Asymptote Blog"
-description: "Writing from the Asymptote team on building secure, observable AI systems."
+title: "Beacon Blog"
+description: "Writing from the Beacon team on building secure, observable AI systems."
---
-Every Asymptote post, newest first. Articles open on
+Every Beacon post, newest first. Articles open on
[asymptotelabs.ai/blog](https://asymptotelabs.ai/blog) or Substack.
## Company and perspectives
<CardGroup cols={2}>
<Card
- title="Asymptote Achieves SOC 2 Type II Compliance"
+ title="Beacon Achieves SOC 2 Type II Compliance"
icon="shield-check"
img="https://asymptotelabs.ai/soc2_compliance_badge.png"
href="https://asymptotelabs.ai/blog/asymptote-achieves-soc-2-type-ii-compliance"
>
- Our SOC 2 Type II attestation validates that Asymptote security controls are operating effectively over time.
+ Our SOC 2 Type II attestation validates that Beacon security controls are operating effectively over time.
</Card>
<Card
title="Agent Visibility Beyond the Endpoint"
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdx
index 4b71dd78..58cb6ffa 100644
--- a/docs/changelog/cli.mdx
+++ b/docs/changelog/cli.mdx
@@ -133,7 +133,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
### v1.3.9 · September 9, 2026
-- **Cloud agents can send telemetry to Asymptote Managed** · Claude Code cloud sandboxes had two upload targets, a GCS or S3 bucket you own. `BEACON_CLOUD_UPLOAD=asymptote` with `BEACON_CLOUD_INGEST_URL` and a `BEACON_CLOUD_DEVICE_KEY` minted for the environment now posts the sandbox log to managed ingest, the same endpoint the laptop forwarder uses, so cloud-agent sessions appear in the dashboard beside endpoint sessions. New lines are sent on every Stop, in batches under the ingest limits; a revoked key is reported, never retried past the offset. See [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents).
+- **Cloud agents can send telemetry to Beacon Managed** · Claude Code cloud sandboxes had two upload targets, a GCS or S3 bucket you own. `BEACON_CLOUD_UPLOAD=asymptote` with `BEACON_CLOUD_INGEST_URL` and a `BEACON_CLOUD_DEVICE_KEY` minted for the environment now posts the sandbox log to managed ingest, the same endpoint the laptop forwarder uses, so cloud-agent sessions appear in the dashboard beside endpoint sessions. New lines are sent on every Stop, in batches under the ingest limits; a revoked key is reported, never retried past the offset. See [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents).
### v1.3.8 · September 7, 2026
@@ -216,29 +216,29 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
- **Onboarding asks where telemetry should go** · The first-run prompt ends with
an arrow-key question: keep telemetry on this machine (default), forward it to
your own infrastructure (a SIEM, observability platform, or an S3/GCS bucket you
- own, with a pointer to the log forwarding docs), or forward it to Asymptote
+ own, with a pointer to the log forwarding docs), or forward it to Beacon
Managed, which runs `beacon endpoint connect` after the install. Question titles
and the selected row use the Beacon purple. `beacon endpoint install --connect`
- skips the question and connects, `BEACON_MANAGED_INGEST=0` hides the Asymptote
+ skips the question and connects, `BEACON_MANAGED_INGEST=0` hides the Beacon
answer, the answer stays local and is shown by `beacon endpoint onboarding`; the
- Asymptote answer is recorded only once the machine is connected. The Homebrew
+ Beacon answer is recorded only once the machine is connected. The Homebrew
formula now depends on `vector` so a Homebrew install can connect without a
second step.
- **`beacon endpoint connect` and `disconnect`** · Connect an endpoint to
- Asymptote managed ingest from the CLI: it finds Vector (0.56+), opens the
+ Beacon managed ingest from the CLI: it finds Vector (0.56+), opens the
dashboard's device approval page, receives a per-device key through a
loopback PKCE exchange, stores it in a `0600` secrets file, renders and
validates the forwarder config, and starts `com.beacon.endpoint.asymptote-forwarder`
(launchd) or `beacon-asymptote-forwarder.service` (systemd) in user or system
- mode. `beacon endpoint status` gains an "Asymptote managed ingest" line and a
+ mode. `beacon endpoint status` gains an "Beacon managed ingest" line and a
`managed_ingest` JSON object with forwarder state and a live credential check;
`config.json` gains a non-secret `managed_ingest` block; uninstall removes the
forwarder and credentials. Re-running connect rotates the key in place.
-- **Asymptote Managed forwarding pack** · `beacon endpoint asymptote` generates a
+- **Beacon Managed forwarding pack** · `beacon endpoint asymptote` generates a
Vector `http` forwarder that posts the runtime and inventory JSONL to
- Asymptote's ingest service with a per-device key read from a `0600` secrets
+ Beacon's ingest service with a per-device key read from a `0600` secrets
file, plus a credential smoke test and sample events. It is the first Beacon
- destination that sends events to an Asymptote-run service; forwarding is
+ destination that sends events to a Beacon-run service; forwarding is
opt-in per device, starts only after browser approval, and is revocable from
the dashboard. `beacon endpoint connect` (coming next) runs enrollment and the
forwarder as a service using the same template.
@@ -247,7 +247,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
to and `beacon login` saved credentials nothing consumed. `beacon endpoint
status` no longer prints an "Endpoint ingest" line and its JSON output drops
`managed_upload`; a `managed_upload` block in `config.json` is ignored.
- Forwarding to Asymptote returns as an explicit, revocable Vector destination
+ Forwarding to Beacon returns as an explicit, revocable Vector destination
set up by `beacon endpoint connect` in an upcoming release.
## August 2026
@@ -524,7 +524,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
- **Windows install documentation** · How to install the endpoint on Windows and how
to verify it afterwards.
- **Verification that can actually fail** · The sandbox harness gained a Windows
- guest lane, uninstall assertions that ask the operating system rather than Beacon
+ guest lane, uninstall assertions that ask the operating system rather tha Beacon
whether a service is gone, and fixes to several checks that could not fail and so
read as coverage without providing any.
@@ -855,19 +855,19 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
### v0.0.59 · June 13, 2026
-- **Managed ingest commands** · Added `beacon ingest` commands for checking managed ingest status and uploading endpoint telemetry to configured Asymptote Managed destinations.
+- **Managed ingest commands** · Added `beacon ingest` commands for checking managed ingest status and uploading endpoint telemetry to configured Beacon Managed destinations.
- **Endpoint token reporting** · Added `beacon endpoint tokens` for local token, cost, model, session, run, harness, and repository attribution from Beacon runtime logs.
- **Token attribution fixes** · Improved token usage normalization for Claude Code telemetry, cumulative metric batches, composite run IDs, and SDK session attributes.
### v0.0.58 · June 13, 2026
- **Token usage foundation** · Added token usage aggregation, dashboard token views, and trace identity fields so endpoint activity can report usage and cost consistently.
-- **Managed ingest support** · Added the endpoint ingest plumbing that lets authenticated Beacon clients upload endpoint telemetry to Asymptote Managed when configured.
+- **Managed ingest support** · Added the endpoint ingest plumbing that lets authenticated Beacon clients upload endpoint telemetry to Beacon Managed when configured.
- **Telemetry schema updates** · Added trace identity, usage cost, and int64 token count fields while preserving local runtime log workflows.
### v0.0.57 · June 11, 2026
-- **Beacon dashboard login** · Added `beacon login` so the Beacon CLI can authenticate with the Asymptote dashboard through a browser-based flow.
+- **Beacon dashboard login** · Added `beacon login` so the Beacon CLI can authenticate with the Beacon dashboard through a browser-based flow.
- **Credential replacement controls** · `beacon login --force` lets operators replace saved credentials when switching users or organizations.
- **Dashboard URL configuration** · Login can target a custom dashboard URL with `--dashboard-url` or `BEACON_DASHBOARD_URL`, while endpoint telemetry remains local-only unless cloud features are explicitly used.
@@ -920,7 +920,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
### v0.0.48 · June 8, 2026
- **OpenTelemetry GenAI schema support** · Beacon now preserves standard `gen_ai` request, response, usage, tool, retrieval, evaluation, message, provider, workflow, and system-instruction metadata in endpoint events.
-- **Observe package rename** · Renamed the shared schema package from Asymptote Trace to Asymptote Observe while preserving the public Beacon event schema version.
+- **Observe package rename** · Renamed the shared schema package from Beacon Trace to Beacon Observe while preserving the public Beacon event schema version.
- **Content handling fixes** · Improved prompt detection for empty GenAI input messages and kept `content.retention` validation backward compatible while using `content.truncated` for truncation display where available.
### v0.0.47 · June 8, 2026
diff --git a/docs/changelog/sdk.mdx b/docs/changelog/sdk.mdx
index d2c153e3..ab527b84 100644
--- a/docs/changelog/sdk.mdx
+++ b/docs/changelog/sdk.mdx
@@ -1,11 +1,11 @@
---
-title: Asymptote SDK Release Notes
-description: Latest updates and improvements to the Asymptote Observe SDK
+title: Beacon SDK Release Notes
+description: Latest updates and improvements to the Beacon Observe SDK
---
## Latest updates
-Stay up to date with the latest changes to the Asymptote Observe SDK.
+Stay up to date with the latest changes to the Beacon Observe SDK.
---
@@ -14,7 +14,7 @@ Stay up to date with the latest changes to the Asymptote Observe SDK.
### v0.1.0 · June 10, 2026
- **Initial TypeScript SDK release** · Published `@asymptote/sdk` for instrumenting cloud-hosted agent applications with OpenTelemetry spans compatible with Beacon's normalized event model.
-- **Hosted and customer-managed export** · Added hosted Asymptote Observe export through `ASYMPTOTE_API_KEY` and customer-managed OTLP export through `OTEL_EXPORTER_OTLP_ENDPOINT` or `Observe.initialize({ otlpEndpoint })`.
+- **Hosted and customer-managed export** · Added hosted Beacon Observe export through `ASYMPTOTE_API_KEY` and customer-managed OTLP export through `OTEL_EXPORTER_OTLP_ENDPOINT` or `Observe.initialize({ otlpEndpoint })`.
- **AI SDK instrumentation** · Enabled OpenAI and Anthropic OpenLLMetry instrumentation by default, with configuration hooks for disabling or tuning provider instrumentation.
- **Agent integration helpers** · Added `Observe.observe()`, `Observe.getTracer()`, `Observe.wrapClaudeAgentQuery()`, `Observe.flush()`, and `Observe.shutdown()` for custom agent steps, Vercel AI SDK telemetry, Claude Agent SDK query wrapping, and process lifecycle handling.
- **Beacon compatibility attributes** · Exported constants for Beacon-compatible fields such as `beacon.origin`, `beacon.harness.name`, `beacon.event.action`, and `beacon.prompt.text`.
diff --git a/docs/cli/asymptote.mdx b/docs/cli/asymptote.mdx
index a2cd25bd..5a182fd6 100644
--- a/docs/cli/asymptote.mdx
+++ b/docs/cli/asymptote.mdx
@@ -1,13 +1,13 @@
---
title: "beacon endpoint asymptote"
-description: "Generate the Vector forwarding pack that sends Beacon endpoint events to Asymptote's managed ingest service, and write validation events."
+description: "Generate the Vector forwarding pack that sends Beacon endpoint events to Beacon's managed ingest service, and write validation events."
---
## Forwarding command
-Use `beacon endpoint asymptote` to generate the content pack that forwards Beacon endpoint events to Asymptote's managed ingest service. The pack keeps Beacon as a local JSONL producer: Vector tails the runtime and inventory logs and POSTs gzip-compressed NDJSON batches over HTTPS with a per-device key.
+Use `beacon endpoint asymptote` to generate the content pack that forwards Beacon endpoint events to Beacon's managed ingest service. The pack keeps Beacon as a local JSONL producer: Vector tails the runtime and inventory logs and POSTs gzip-compressed NDJSON batches over HTTPS with a per-device key.
-This is the one destination that sends telemetry to an Asymptote-run endpoint. It is opt-in and revocable: nothing is forwarded until a member of your Asymptote organization has approved the device in the browser and Vector has been started with the resulting key. `beacon endpoint connect` performs that enrollment and runs the forwarder as a service; the commands on this page generate the same files for running or inspecting the forwarder by hand.
+This is the one destination that sends telemetry to a Beacon-run endpoint. It is opt-in and revocable: nothing is forwarded until a member of your Beacon organization has approved the device in the browser and Vector has been started with the resulting key. `beacon endpoint connect` performs that enrollment and runs the forwarder as a service; the commands on this page generate the same files for running or inspecting the forwarder by hand.
Beacon does not store the device key in its own configuration. The key lives in a `0600` JSON secrets file that Vector reads through its secret backend, so it appears in neither `vector.toml` nor the process environment.
@@ -25,7 +25,7 @@ beacon endpoint asymptote [command]
Write the forwarding pack to a directory.
</Card>
<Card title="beacon endpoint asymptote validate" icon="check" href="#beacon-endpoint-asymptote-validate">
- Write and describe a Beacon Asymptote validation event.
+ Write and describe a Beacon validation event.
</Card>
</Columns>
@@ -113,7 +113,7 @@ vector --config ./beacon-asymptote-pack/vector.toml
beacon endpoint asymptote validate
```
-The command writes the local event only. If the forwarder is running, the event reaches the ingest service within its batch window (60 seconds) and appears on the dashboard telemetry page a minute or so later. Search for the message `Beacon endpoint Asymptote validation event`.
+The command writes the local event only. If the forwarder is running, the event reaches the ingest service within its batch window (60 seconds) and appears on the dashboard telemetry page a minute or so later. Search for the message `Beacon endpoint Beacon validation event`.
Expected validation fields:
@@ -141,7 +141,7 @@ curl -sS -o /dev/null -w '%{http_code}\n' "$BEACON_ASYMPTOTE_INGEST_URL/v1/inges
## Related
<Columns cols={2}>
- <Card title="Asymptote managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
+ <Card title="Beacon managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
Wire contract, what leaves the machine, revocation, and offline behavior.
</Card>
<Card title="Log forwarding" icon="tower-broadcast" href="/log-forwarding">
diff --git a/docs/cli/ci.mdx b/docs/cli/ci.mdx
index 14dcf9a4..e09a589e 100644
--- a/docs/cli/ci.mdx
+++ b/docs/cli/ci.mdx
@@ -62,7 +62,7 @@ Some workflows call a third-party action that launches the agent internally. In
artifact-name: beacon-claude-security-review-runtime-log
```
-See the [Claude Code Security Review session workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/claude-security-review-session.yml) for the full GitHub Actions example.
+See the [Claude Code Security Review session workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/claude-security-review-session.yml) for the full GitHub Actions example.
## Commands
diff --git a/docs/cli/cloud-gcs-setup.mdx b/docs/cli/cloud-gcs-setup.mdx
index f35f29b9..b3692c30 100644
--- a/docs/cli/cloud-gcs-setup.mdx
+++ b/docs/cli/cloud-gcs-setup.mdx
@@ -14,7 +14,7 @@ beacon cloud gcs setup
The helper creates or validates a bucket, creates a dedicated uploader service account, grants object upload access, creates a service-account key, and prints the `BEACON_CLOUD_GCS_*` environment variables for cloud agents.
<Warning>
- This self-serve flow passes a scoped Google service-account key into the provider-managed cloud agent environment. Use it for proof-of-concept testing and prototyping. For production enterprise deployments, use [Asymptote Managed](/deployment/managed) or contact Asymptote about secure forwarding in customer-managed infrastructure.
+ This self-serve flow passes a scoped Google service-account key into the provider-managed cloud agent environment. Use it for proof-of-concept testing and prototyping. For production enterprise deployments, use [Beacon Managed](/deployment/managed) or contact Beacon about secure forwarding in customer-managed infrastructure.
</Warning>
## Examples
diff --git a/docs/cli/cloud-s3-setup.mdx b/docs/cli/cloud-s3-setup.mdx
index b6fb89a8..31d7211a 100644
--- a/docs/cli/cloud-s3-setup.mdx
+++ b/docs/cli/cloud-s3-setup.mdx
@@ -21,8 +21,8 @@ and prints `BEACON_CLOUD_UPLOAD=s3`, `BEACON_CLOUD_S3_BUCKET`,
<Warning>
This self-serve flow passes scoped AWS access keys into the provider-managed
cloud agent environment. Use it for proof-of-concept testing and prototyping.
- For production enterprise deployments, use [Asymptote Managed](/deployment/managed)
- or contact Asymptote about secure forwarding in customer-managed infrastructure.
+ For production enterprise deployments, use [Beacon Managed](/deployment/managed)
+ or contact Beacon about secure forwarding in customer-managed infrastructure.
</Warning>
## Examples
diff --git a/docs/cli/cloud.mdx b/docs/cli/cloud.mdx
index 4349129b..2586a795 100644
--- a/docs/cli/cloud.mdx
+++ b/docs/cli/cloud.mdx
@@ -56,7 +56,7 @@ prints the `BEACON_CLOUD_S3_*` and AWS credential variables.
These self-serve flows pass a scoped Google service-account key or AWS access
key into the provider-managed cloud agent environment. Use them for
proof-of-concept testing and prototyping. For production enterprise deployments, use
- [Asymptote Managed](/deployment/managed) or contact Asymptote about secure
+ [Beacon Managed](/deployment/managed) or contact Beacon about secure
forwarding in customer-managed infrastructure.
</Warning>
diff --git a/docs/cli/endpoint-config.mdx b/docs/cli/endpoint-config.mdx
index 97eb2baf..123f0a76 100644
--- a/docs/cli/endpoint-config.mdx
+++ b/docs/cli/endpoint-config.mdx
@@ -82,13 +82,13 @@ sudo beacon endpoint config validate --system
## Managed ingest block
-When the endpoint is connected to Asymptote managed ingest, `config.json` carries a non-secret `managed_ingest` block:
+When the endpoint is connected to Beacon managed ingest, `config.json` carries a non-secret `managed_ingest` block:
| Field | Meaning |
|-------|---------|
| `enabled` | `true` while the endpoint is connected |
| `ingest_url` | The `https://` ingest URL returned by enrollment |
-| `device_id` | This device's id in the Asymptote dashboard |
+| `device_id` | This device's id in the Beacon dashboard |
| `organization_id` | The organization that approved the device |
[`beacon endpoint connect`](/cli/endpoint-connect) writes the block and `beacon endpoint disconnect` clears it. It never holds the device key, which lives only in `asymptote/vector-secrets.json`, and it survives re-running `beacon endpoint install`.
diff --git a/docs/cli/endpoint-connect.mdx b/docs/cli/endpoint-connect.mdx
index 5de1616b..2592796b 100644
--- a/docs/cli/endpoint-connect.mdx
+++ b/docs/cli/endpoint-connect.mdx
@@ -1,11 +1,11 @@
---
title: "beacon endpoint connect"
-description: "Connect a Beacon endpoint to Asymptote managed ingest, or disconnect it, and understand what the forwarder stores and sends."
+description: "Connect a Beacon endpoint to Beacon managed ingest, or disconnect it, and understand what the forwarder stores and sends."
---
## Command overview
-`beacon endpoint connect` forwards this endpoint's telemetry to Asymptote so it appears on the Asymptote dashboard. It opens the dashboard in your browser, where a member of your organization approves this specific device; the CLI then receives a key for this device, stores it in a private secrets file, and starts a Vector forwarder that ships the runtime and inventory JSONL over HTTPS.
+`beacon endpoint connect` forwards this endpoint's telemetry to Beacon so it appears on the Beacon dashboard. It opens the dashboard in your browser, where a member of your organization approves this specific device; the CLI then receives a key for this device, stores it in a private secrets file, and starts a Vector forwarder that ships the runtime and inventory JSONL over HTTPS.
Forwarding is opt-in and revocable. Beacon's default stays local-only, nothing recorded before the approval is sent, and revoking the device from the dashboard stops ingestion within about a minute. `beacon endpoint disconnect` stops the forwarder and removes the local credentials.
@@ -18,14 +18,14 @@ beacon endpoint disconnect [flags]
- Beacon endpoint installed (`beacon endpoint install`) and writing local JSONL.
- Vector 0.50 or newer on the machine (Apple Silicon gets 0.58 from Homebrew or the package; Intel Macs get 0.50.0, the last x86_64 build Vector published). The signed macOS package installs it at `/opt/beacon/bin/vector`; on macOS Homebrew installs it with Beacon, as the tap's `beacon-vector` keg (named that rather than `vector` so it coexists with a Vector from `vectordotdev/brew`, and kept in `libexec` so it stays off your PATH); on Linux install the `vector` package from [vector.dev](https://vector.dev). `connect` stops before opening a browser if no usable Vector is found.
-- A browser where you can sign in to the Asymptote dashboard as a member of an organization that has managed ingest enabled.
+- A browser where you can sign in to the Beacon dashboard as a member of an organization that has managed ingest enabled.
## What connect does
1. Locates Vector: `--vector-bin`, then `BEACON_VECTOR_BIN`, then `/opt/beacon/bin/vector`, the `beacon-vector` keg in each Homebrew prefix, a linked `vector` in each Homebrew prefix, then `PATH`. The `beacon-vector` keg is tried ahead of any other Homebrew Vector because it is the copy the tap pins at a supported version.
2. Registers this machine's hostname, operating system, architecture, Beacon version and install mode with the dashboard, and opens `/cli/enroll` in your browser. The approval page shows those details; nothing is minted until someone clicks **Approve this device**.
3. Receives the device key through a loopback callback and a PKCE exchange. The key is written once to `asymptote/vector-secrets.json` with mode `0600` and is never printed.
-4. Renders `asymptote/vector.toml` from the [Asymptote pack](/cli/asymptote) template with the ingest URL returned by enrollment, runs `vector validate`, installs a service unit and starts it.
+4. Renders `asymptote/vector.toml` from the [Beacon pack](/cli/asymptote) template with the ingest URL returned by enrollment, runs `vector validate`, installs a service unit and starts it.
5. Records the non-secret enrollment (device id, organization, ingest URL) in `asymptote/enrollment.json` and `config.json`'s `managed_ingest` block.
A connect that fails at `vector validate` or at loading the service saves no enrollment record, so the endpoint is not connected: `beacon endpoint status` says so, the next interactive install offers the destination question again, and `beacon endpoint disconnect` cleans up what was written. After `disconnect --keep-credentials`, status reports not connected and names the kept device id.
@@ -49,7 +49,7 @@ The directory is `0700`. The device key appears only in the secrets file, which
| Flag | Description |
|------|-------------|
-| `--dashboard-url <url>` | Asymptote dashboard URL. Defaults to `https://asymptotelabs.ai` or `BEACON_DASHBOARD_URL`. Must be `https://` |
+| `--dashboard-url <url>` | Beacon dashboard URL. Use `https://beacon.sh` for Beacon Managed. Defaults to `https://asymptotelabs.ai` or `BEACON_DASHBOARD_URL`. Must be `https://` |
| `--no-browser` | Print the approval URL instead of opening a browser |
| `--vector-bin <path>` | Vector binary to run |
| `--user` | Use per-user endpoint paths. Enabled by default |
@@ -62,15 +62,15 @@ The directory is `0700`. The device key appears only in the secrets file, which
## Examples
```bash title="Connect the default per-user install"
-beacon endpoint connect
+beacon endpoint connect --dashboard-url https://beacon.sh
```
```bash title="Connect a system-mode install from the signed package"
-sudo /opt/beacon/bin/beacon endpoint connect --system
+sudo /opt/beacon/bin/beacon endpoint connect --system --dashboard-url https://beacon.sh
```
```bash title="Connect from a machine without a browser"
-beacon endpoint connect --no-browser
+beacon endpoint connect --no-browser --dashboard-url https://beacon.sh
# open the printed URL in a browser where you are signed in
```
@@ -83,10 +83,10 @@ beacon endpoint disconnect
`beacon endpoint status` prints one line for managed ingest: whether this endpoint is connected, to which organization, the device id, whether the forwarder service is loaded and running, whether the credential is still valid (it asks the ingest service, with a 3-second timeout), and the size of the disk buffer. `--json` exposes the same under `managed_ingest`.
```text
-Asymptote managed ingest: connected to Asymptote Test as device 807c6a11-…; forwarder loaded=true running=true; credential valid
+Beacon managed ingest: connected to Beacon Test as device 807c6a11-…; forwarder loaded=true running=true; credential valid
```
-`credential revoked` means the key was revoked or expired, or the approving user is no longer a member of the organization; Vector is logging 401s and dropping batches. Run `beacon endpoint connect` again to re-enroll.
+`credential revoked` means the key was revoked or expired, or the approving user is no longer a member of the organization; Vector is logging 401s and dropping batches. Run `beacon endpoint connect --dashboard-url https://beacon.sh` again to re-enroll.
## Revocation and disconnect
@@ -99,7 +99,7 @@ Vector keeps reading into an on-disk buffer (512 MiB for runtime, 256 MiB for in
## Related
<Columns cols={2}>
- <Card title="Asymptote Managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
+ <Card title="Beacon Managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
Wire contract, what leaves the machine, revocation, and offline behavior.
</Card>
<Card title="beacon endpoint asymptote" icon="terminal" href="/cli/asymptote">
diff --git a/docs/cli/endpoint-install.mdx b/docs/cli/endpoint-install.mdx
index 6d186733..eb0208b7 100644
--- a/docs/cli/endpoint-install.mdx
+++ b/docs/cli/endpoint-install.mdx
@@ -45,7 +45,7 @@ By default, Beacon configures Claude Code and Codex CLI telemetry for local or c
| `--falcon-sourcetype <type>` | Optional Falcon LogScale parser or sourcetype |
| `--falcon-insecure-skip-verify` | Skip Falcon LogScale HEC TLS certificate verification |
| `--falcon-ca-file <path>` | Optional CA certificate path for Falcon LogScale HEC TLS verification |
-| `--connect` | After a successful install, connect this endpoint to Asymptote managed ingest: opens the dashboard to approve the device and starts the Vector forwarder. Same as running [`beacon endpoint connect`](/cli/endpoint-connect) afterwards |
+| `--connect` | After a successful install, connect this endpoint to Beacon managed ingest: opens the dashboard to approve the device and starts the Vector forwarder. Same as running [`beacon endpoint connect`](/cli/endpoint-connect) afterwards |
## Telemetry destination question
@@ -55,9 +55,9 @@ On a first interactive install the [onboarding prompt](/cli/endpoint-onboarding)
|--------|--------------|
| Keep it on this machine (default) | Nothing is forwarded. Enter picks this, so forwarding is never a side effect. |
| Forward to your own infrastructure | A SIEM, observability platform, or an S3/GCS bucket you own. The prompt prints the [log forwarding docs](/log-forwarding) and the pack commands; the install stays local until you set one up. |
-| Forward to Asymptote Managed | Runs the [connect flow](/cli/endpoint-connect) after the install completes. A failed connect is reported with the retry command and never fails the install. |
+| Forward to Beacon Managed | Runs the [connect flow](/cli/endpoint-connect) after the install completes. A failed connect is reported with the retry command and never fails the install. |
-`--connect` is already the answer, so it skips the question. `BEACON_MANAGED_INGEST=0` hides the Asymptote answer; the question is never shown non-interactively. The answer is stored in the local onboarding profile and never sent. Local and own-infrastructure answers are recorded at once and the question is not asked again. The Asymptote answer is recorded only once the machine is connected, so if the install or the connection fails, the next interactive install asks again.
+`--connect` is already the answer, so it skips the question. `BEACON_MANAGED_INGEST=0` hides the Beacon answer; the question is never shown non-interactively. The answer is stored in the local onboarding profile and never sent. Local and own-infrastructure answers are recorded at once and the question is not asked again. The Beacon answer is recorded only once the machine is connected, so if the install or the connection fails, the next interactive install asks again.
## Examples
@@ -180,12 +180,12 @@ beacon endpoint hooks install --harness grok --level project
```
<Note>
- System-mode install (`--system`) is supported on macOS and on Linux distributions that use systemd. Omit `--system` for the default non-root local install. GitHub Copilot CLI and Factory Droid OTLP use launch-environment settings rather than Beacon-managed shell-profile edits.
+ System-mode install (`--system`) is supported on macOS and on Linux distributions that use systemd. Omit `--system` for the default non-root local install. GitHub Copilot CLI and Factory Droid OTLP use launch-environment settings rather tha Beacon-managed shell-profile edits.
</Note>
## Known limitations
-A user-mode collector cannot run beside a system-mode one on the same machine. The collector health-check port (`127.0.0.1:13133`) is fixed, so the second collector cannot bind it; the install fails with `Collector ports are not listening` and rolls back the endpoint files it wrote. Either write the user-mode files without starting the service (`beacon endpoint install --user --no-start`) or uninstall the system endpoint first (`sudo beacon endpoint uninstall --system`). Tracked as [GitHub issue #447](https://github.com/Asymptote-Labs/agent-beacon/issues/447).
+A user-mode collector cannot run beside a system-mode one on the same machine. The collector health-check port (`127.0.0.1:13133`) is fixed, so the second collector cannot bind it; the install fails with `Collector ports are not listening` and rolls back the endpoint files it wrote. Either write the user-mode files without starting the service (`beacon endpoint install --user --no-start`) or uninstall the system endpoint first (`sudo beacon endpoint uninstall --system`). Tracked as [GitHub issue #447](https://github.com/asymptote-labs/agent-beacon/issues/447).
## Related
diff --git a/docs/cli/endpoint-onboarding.mdx b/docs/cli/endpoint-onboarding.mdx
index ad8b384e..97403372 100644
--- a/docs/cli/endpoint-onboarding.mdx
+++ b/docs/cli/endpoint-onboarding.mdx
@@ -15,12 +15,12 @@ beacon endpoint onboarding [flags]
The record lives in `~/.beacon/profile.json`. It survives uninstall, so reinstalling
Beacon never asks the email and usage questions again. The destination question is
asked again on the next interactive install until a destination is recorded; an
-Asymptote answer is recorded only once the connect succeeds.
+Beacon answer is recorded only once the connect succeeds.
## First-run onboarding
-The first interactive `beacon endpoint install` asks two questions, how you are using Beacon and your email, then sends the answers to Asymptote once. This is how we decide
-which agent runtimes and integrations to build next. It then asks a third question, where this machine's telemetry should go: keep it on the machine, forward it to your own infrastructure (a SIEM, observability platform, or an S3/GCS bucket you own, with a pointer to the [log forwarding docs](/log-forwarding)), or forward it to Asymptote Managed, which runs [`beacon endpoint connect`](/cli/endpoint-connect) after the install. That answer stays local and is never sent.
+The first interactive `beacon endpoint install` asks two questions, how you are using Beacon and your email, then sends the answers to Beacon once. This is how we decide
+which agent runtimes and integrations to build next. It then asks a third question, where this machine's telemetry should go: keep it on the machine, forward it to your own infrastructure (a SIEM, observability platform, or an S3/GCS bucket you own, with a pointer to the [log forwarding docs](/log-forwarding)), or forward it to Beacon Managed, which runs [`beacon endpoint connect`](/cli/endpoint-connect) after the install. That answer stays local and is never sent.
What is sent, and nothing else:
@@ -40,7 +40,7 @@ not an ongoing channel.
The prompt never appears non-interactively. Package postinstall scripts, MDM
deployments, `--system` installs, CI, `--dry-run`, and any piped or redirected stdin
skip it silently. The destination question is also skipped on an endpoint already
-connected to Asymptote. A machine onboarded before the question existed is asked it
+connected to Beacon. A machine onboarded before the question existed is asked it
once, on its next interactive install.
## Flags
@@ -57,7 +57,7 @@ once, on its next interactive install.
Set `BEACON_ONBOARDING=0` to suppress the prompt on an install that would otherwise be
interactive. There is no CLI flag for this: it exists for unattended CI and MDM
-workflows. `BEACON_MANAGED_INGEST=0` hides only the Asymptote Managed answer from the
+workflows. `BEACON_MANAGED_INGEST=0` hides only the Beacon Managed answer from the
destination question; `beacon endpoint install --connect` still connects when asked explicitly.
```bash title="Suppress the prompt"
@@ -78,8 +78,8 @@ is reported on stderr and ignored rather than failing the install.
## Examples
Show what was recorded, including the answer to the destination question
-(`Telemetry destination: local only …`, `own infrastructure …` or `Asymptote Managed`; absent
-when it has not been asked, or when an Asymptote answer has not yet been carried through to a
+(`Telemetry destination: local only …`, `own infrastructure …` or `Beacon Managed`; absent
+when it has not been asked, or when a Beacon answer has not yet been carried through to a
connected machine):
```bash title="Show the onboarding record"
@@ -93,7 +93,7 @@ one of three values; `--json` exposes it as `destination`:
|-------|------------|
| `local` | local only (nothing forwarded) |
| `own_infra` | own infrastructure (forwarding pack) |
-| `asymptote` | Asymptote Managed |
+| `asymptote` | Beacon Managed |
Clear it so the next install asks again:
@@ -101,7 +101,7 @@ Clear it so the next install asks again:
beacon endpoint onboarding --reset
```
-Retry a submission that could not reach Asymptote. A failed submission never fails an
+Retry a submission that could not reach Beacon. A failed submission never fails an
install; the payload is kept and retried automatically on the next install or repair.
```bash title="Resend a queued signup"
diff --git a/docs/cli/endpoint-paths.mdx b/docs/cli/endpoint-paths.mdx
index 748face6..b4e937e1 100644
--- a/docs/cli/endpoint-paths.mdx
+++ b/docs/cli/endpoint-paths.mdx
@@ -34,7 +34,7 @@ The collector runs under whichever service manager the host provides. On Linux,
| Windows | Service Control Manager | `BeaconCollector` service, defined at `HKLM\SYSTEM\CurrentControlSet\Services\BeaconCollector` | Supervised, because Windows has no per-user service manager |
| Containers, no init | supervised | `/etc/beacon/endpoint/collector.pid` | `~/.beacon/endpoint/collector.pid` |
-The Asymptote forwarder started by `beacon endpoint connect` is a second, resident service that runs Vector: `/Library/LaunchDaemons/com.beacon.endpoint.asymptote-forwarder.plist` or `~/Library/LaunchAgents/com.beacon.endpoint.asymptote-forwarder.plist` on macOS, `/etc/systemd/system/beacon-asymptote-forwarder.service` or `~/.config/systemd/user/beacon-asymptote-forwarder.service` on Linux. It is not offered in supervised mode, because nothing would restart it; run the [Asymptote pack](/cli/asymptote) under your own supervisor there.
+The Beacon forwarder started by `beacon endpoint connect` is a second, resident service that runs Vector: `/Library/LaunchDaemons/com.beacon.endpoint.asymptote-forwarder.plist` or `~/Library/LaunchAgents/com.beacon.endpoint.asymptote-forwarder.plist` on macOS, `/etc/systemd/system/beacon-asymptote-forwarder.service` or `~/.config/systemd/user/beacon-asymptote-forwarder.service` on Linux. It is not offered in supervised mode, because nothing would restart it; run the [Beacon pack](/cli/asymptote) under your own supervisor there.
The scheduled inventory job is a third, one-shot unit that `beacon endpoint install` writes in both modes and the package postinstall reconciles on every upgrade: `/Library/LaunchDaemons/com.beacon.endpoint.inventory.plist` or `~/Library/LaunchAgents/com.beacon.endpoint.inventory.plist` on macOS, `beacon-inventory.timer` plus `beacon-inventory.service` under `/etc/systemd/system` or `~/.config/systemd/user` on Linux. It writes `inventory_state.jsonl` and its `inventory-state.json` state file beside the runtime log. Like the forwarder it is not offered in supervised mode; run `beacon endpoint inventory heartbeat --scheduled` from your own scheduler there.
diff --git a/docs/cli/endpoint-status.mdx b/docs/cli/endpoint-status.mdx
index 7d955230..644cb627 100644
--- a/docs/cli/endpoint-status.mdx
+++ b/docs/cli/endpoint-status.mdx
@@ -61,7 +61,7 @@ Status includes:
- Endpoint diagnostics
- Destination configuration in JSON output, including Splunk HEC or Falcon LogScale HEC endpoint, index, source, and sourcetype when configured
- Last Beacon event in the runtime log, when present
-- Asymptote managed ingest: whether this endpoint is connected, the organization and device id, forwarder service state, whether the device key is still accepted by the ingest service (`valid`, `revoked`, or `unknown` when offline), and the disk buffer size. In `--json` this is the `managed_ingest` object; the device key itself is never included. The line reports the connection for the install mode you asked about (`--user` or `--system`), even when the collector view switches to the system install because it holds the OTLP ports.
+- Beacon managed ingest: whether this endpoint is connected, the organization and device id, forwarder service state, whether the device key is still accepted by the ingest service (`valid`, `revoked`, or `unknown` when offline), and the disk buffer size. In `--json` this is the `managed_ingest` object; the device key itself is never included. The line reports the connection for the install mode you asked about (`--user` or `--system`), even when the collector view switches to the system install because it holds the OTLP ports.
- Inventory heartbeat: whether the scheduled inventory job is enabled and loaded, its interval, and when it last wrote. In `--json` this is the `inventory_heartbeat` object (`enabled`, `scheduled`, `interval`, `job`, `last_emitted_at`, `log_path`), reported for the requested install mode like managed ingest.
When Splunk HEC is configured, `--json` includes a `destinations.splunk_hec` object with `configured: true` and the non-secret destination settings. When Falcon LogScale HEC is configured, `--json` includes `destinations.falcon_hec` with the same non-secret fields. HEC tokens are not printed. File-based destinations such as Wazuh, Elastic, Datadog, Sumo Logic, Rapid7, Microsoft Sentinel, and AWS S3 validate against the configured runtime log path and their generated shipper configuration.
diff --git a/docs/cli/endpoint-uninstall.mdx b/docs/cli/endpoint-uninstall.mdx
index 9e78cb08..a25c1bd7 100644
--- a/docs/cli/endpoint-uninstall.mdx
+++ b/docs/cli/endpoint-uninstall.mdx
@@ -59,7 +59,7 @@ sudo beacon endpoint uninstall --system --keep-logs
Beacon removes files listed in its install manifest, including managed config, collector config, and service files. Unless `--keep-logs` is set, it also removes the configured runtime JSONL log.
-If the endpoint was connected to Asymptote managed ingest, uninstall also stops and removes the `com.beacon.endpoint.asymptote-forwarder` service (or `beacon-asymptote-forwarder.service`) and the `asymptote/` directory holding the Vector config, buffer, enrollment record and device key; `--keep-config` keeps the enrollment record and key. The device stays registered server-side until it is revoked from the dashboard's Beacon Endpoints page.
+If the endpoint was connected to Beacon managed ingest, uninstall also stops and removes the `com.beacon.endpoint.asymptote-forwarder` service (or `beacon-asymptote-forwarder.service`) and the `asymptote/` directory holding the Vector config, buffer, enrollment record and device key; `--keep-config` keeps the enrollment record and key. The device stays registered server-side until it is revoked from the dashboard's Beacon Endpoints page.
## Related
diff --git a/docs/cli/endpoint.mdx b/docs/cli/endpoint.mdx
index efe9d4b2..1ccb65f8 100644
--- a/docs/cli/endpoint.mdx
+++ b/docs/cli/endpoint.mdx
@@ -38,10 +38,10 @@ beacon endpoint [command]
Show collector, service, harness, diagnostic, and runtime log status.
</Card>
<Card title="beacon endpoint connect" icon="link" href="/cli/endpoint-connect">
- Approve this device in the Asymptote dashboard and start the Vector forwarder.
+ Approve this device in the Beacon dashboard and start the Vector forwarder.
</Card>
<Card title="beacon endpoint disconnect" icon="link-slash" href="/cli/endpoint-connect">
- Stop the Asymptote forwarder and remove the local device key.
+ Stop the Beacon forwarder and remove the local device key.
</Card>
<Card title="beacon endpoint doctor" icon="stethoscope" href="/cli/endpoint-doctor">
Run local endpoint health checks with pass/fail exit behavior.
@@ -65,7 +65,7 @@ beacon endpoint [command]
Index, list, search, and show local traces from runtime logs.
</Card>
<Card title="beacon endpoint asymptote" icon="tower-broadcast" href="/cli/asymptote">
- Generate the Asymptote forwarding pack for running Vector by hand.
+ Generate the Beacon forwarding pack for running Vector by hand.
</Card>
<Card title="beacon scan" icon="magnifying-glass" href="/cli/scan">
Run threat-detection rules over local endpoint telemetry.
diff --git a/docs/cli/index.mdx b/docs/cli/index.mdx
index f0673813..f5a20b95 100644
--- a/docs/cli/index.mdx
+++ b/docs/cli/index.mdx
@@ -144,9 +144,9 @@ Manage the local endpoint agent and inspect supported agent harness telemetry.
| Command | Description |
|---------|-------------|
| [`beacon endpoint install`](/cli/endpoint-install) | Install or update the local endpoint collector, runtime telemetry configuration, and optional Splunk HEC or Falcon LogScale HEC forwarding. |
-| [`beacon endpoint status`](/cli/endpoint-status) | Inspect collector health, runtime log state, configured harnesses, diagnostics, forwarding readiness, and the Asymptote managed-ingest connection. |
-| [`beacon endpoint connect`](/cli/endpoint-connect) | Approve this device in the Asymptote dashboard and start the Vector forwarder to managed ingest. |
-| [`beacon endpoint disconnect`](/cli/endpoint-connect) | Stop the Asymptote forwarder and remove the local device key. |
+| [`beacon endpoint status`](/cli/endpoint-status) | Inspect collector health, runtime log state, configured harnesses, diagnostics, forwarding readiness, and the Beacon managed-ingest connection. |
+| [`beacon endpoint connect`](/cli/endpoint-connect) | Approve this device in the Beacon dashboard and start the Vector forwarder to managed ingest. |
+| [`beacon endpoint disconnect`](/cli/endpoint-connect) | Stop the Beacon forwarder and remove the local device key. |
| [`beacon endpoint doctor`](/cli/endpoint-doctor) | Run local endpoint health checks with pass/fail exit behavior and optional safe remediation. |
| [`beacon endpoint inventory`](/cli/endpoint-inventory) | Show configured, detected, hook, and observed endpoint inventory. |
| [`beacon endpoint discover`](/cli/endpoint-discover) | Discover supported local [agent harnesses](/runtimes) and their telemetry configuration state. |
@@ -168,7 +168,7 @@ Manage the local endpoint agent and inspect supported agent harness telemetry.
| [`beacon endpoint cloudwatch`](/cli/cloudwatch) | Generate AWS CloudWatch Logs forwarding content for Beacon endpoint events. |
| [`beacon endpoint s3`](/cli/s3) | Generate AWS S3 forwarding content for Beacon endpoint events. |
| [`beacon endpoint gcs`](/cli/gcs) | Generate Google Cloud Storage forwarding content for Beacon endpoint events. |
-| [`beacon endpoint asymptote`](/cli/asymptote) | Generate the Vector forwarding pack for Asymptote managed ingest and write validation events. |
+| [`beacon endpoint asymptote`](/cli/asymptote) | Generate the Vector forwarding pack for Beacon managed ingest and write validation events. |
| [`beacon endpoint hooks`](/cli/hooks) | Manage supported hook-based endpoint telemetry. |
| [`beacon endpoint opencode`](/cli/endpoint-opencode) | Collect endpoint telemetry from OpenCode session records on this machine. |
| [`beacon endpoint pi`](/cli/endpoint-pi) | Collect endpoint telemetry from Pi session records on this machine. |
@@ -322,13 +322,13 @@ Generate Google Cloud Storage forwarding content and validation events for Beaco
beacon endpoint asymptote [command]
```
-Generate the Vector forwarding pack that sends Beacon endpoint events to Asymptote managed ingest, and write validation events.
+Generate the Vector forwarding pack that sends Beacon endpoint events to Beacon managed ingest, and write validation events.
| Command | Description |
|---------|-------------|
| [`beacon endpoint asymptote print-config`](/cli/asymptote#beacon-endpoint-asymptote-print-config) | Print the Vector forwarding config for the configured runtime log. |
-| [`beacon endpoint asymptote install-pack`](/cli/asymptote#beacon-endpoint-asymptote-install-pack) | Write the Asymptote forwarding pack to a directory. |
-| [`beacon endpoint asymptote validate`](/cli/asymptote#beacon-endpoint-asymptote-validate) | Write and describe a known-good Beacon Asymptote validation event. |
+| [`beacon endpoint asymptote install-pack`](/cli/asymptote#beacon-endpoint-asymptote-install-pack) | Write the Beacon forwarding pack to a directory. |
+| [`beacon endpoint asymptote validate`](/cli/asymptote#beacon-endpoint-asymptote-validate) | Write and describe a known-good Beacon validation event. |
## beacon endpoint hooks
diff --git a/docs/cli/install.mdx b/docs/cli/install.mdx
index 785ebe0a..0335f097 100644
--- a/docs/cli/install.mdx
+++ b/docs/cli/install.mdx
@@ -30,7 +30,7 @@ beacon version
`brew trust` is a one-time step for newer Homebrew releases before loading
third-party formulae from the tap.
-On macOS the formula also depends on `asymptote-labs/tap/beacon-vector`, the tap's mirror of Vector's releases (Vector is not in homebrew-core), which runs the optional [Asymptote Managed forwarder](/cli/endpoint-connect); Homebrew installs it alongside Beacon so no second step is needed.
+On macOS the formula also depends on `asymptote-labs/tap/beacon-vector`, the tap's mirror of Vector's releases (Vector is not in homebrew-core), which runs the optional [Beacon Managed forwarder](/cli/endpoint-connect); Homebrew installs it alongside Beacon so no second step is needed.
The mirror is named `beacon-vector` rather than `vector` on purpose. Homebrew allows exactly one keg named `vector` no matter which tap it came from, so a mirror by that name could not be installed at all on a machine that already had Vector from `vectordotdev/brew`. Under its own name it coexists with any Vector you already run, and because it keeps its binary in `libexec` — which Homebrew never links — it stays off your PATH and never shadows one. Beacon finds it by path; you do not need to configure anything.
diff --git a/docs/cli/manual-install.mdx b/docs/cli/manual-install.mdx
index 850b84f5..7dbd615d 100644
--- a/docs/cli/manual-install.mdx
+++ b/docs/cli/manual-install.mdx
@@ -63,7 +63,7 @@ per-user CLI installs.
To build the CLI directly from the Beacon repository:
```bash title="Build Beacon from source"
-git clone https://github.com/Asymptote-Labs/agent-beacon.git
+git clone https://github.com/asymptote-labs/agent-beacon.git
cd agent-beacon/cli/beacon
make build
```
diff --git a/docs/cli/rules-pull.mdx b/docs/cli/rules-pull.mdx
index f98969c5..30e2aea9 100644
--- a/docs/cli/rules-pull.mdx
+++ b/docs/cli/rules-pull.mdx
@@ -11,7 +11,7 @@ description: "Fetch an explicit Beacon threat-rule pack into the local store"
beacon rules pull <url> [flags]
```
-This is the only `beacon rules` command that reaches the network, and only when you run it. Beacon never fetches rules on its own. The full Asymptote threat-rule pack is published as a versioned `threat-rules.tar.gz` asset on each Agent Beacon GitHub release.
+This is the only `beacon rules` command that reaches the network, and only when you run it. Beacon never fetches rules on its own. The full Beacon threat-rule pack is published as a versioned `threat-rules.tar.gz` asset on each Agent Beacon GitHub release.
## Supported inputs
diff --git a/docs/cli/token-usage.mdx b/docs/cli/token-usage.mdx
index a5cca997..c51cb5fc 100644
--- a/docs/cli/token-usage.mdx
+++ b/docs/cli/token-usage.mdx
@@ -30,7 +30,7 @@ A few rules shape how the numbers read:
### Per-runtime coverage
-Token coverage is not uniform, and the reason is almost always the runtime rather than Beacon: most agent runtimes do not report usage on the surface Beacon collects from. A turn with no token attribution is a turn whose runtime never reported any.
+Token coverage is not uniform, and the reason is almost always the runtime rather tha Beacon: most agent runtimes do not report usage on the surface Beacon collects from. A turn with no token attribution is a turn whose runtime never reported any.
**Collected and verified against captured payloads:**
@@ -48,7 +48,7 @@ Token coverage is not uniform, and the reason is almost always the runtime rathe
| fx (Vercel Labs) | input, output, cache read, cache creation | Reported (`cost_usd`) | Yes | Yes |
| OpenClaw Gateway | input, output, cache read, cache creation | Not reported on the hook | Yes, per model response | Yes |
-OpenClaw reports usage on its `llm_output` hook, which is a *conversation* hook -- OpenClaw withholds those from every non-bundled plugin until `plugins.entries.beacon-endpoint.hooks.allowConversationAccess` is set in its config. An OpenClaw endpoint collecting prompts, tools, commands and files while reporting no tokens at all is almost always that key, and `beacon endpoint hooks status --harness openclaw` says so. OpenClaw does compute a per-turn price, from an operator-configured cost table rather than from a provider report, so Asymptote does not record it as a reported cost. See [OpenClaw Gateway](/runtimes/openclaw-gateway).
+OpenClaw reports usage on its `llm_output` hook, which is a *conversation* hook -- OpenClaw withholds those from every non-bundled plugin until `plugins.entries.beacon-endpoint.hooks.allowConversationAccess` is set in its config. An OpenClaw endpoint collecting prompts, tools, commands and files while reporting no tokens at all is almost always that key, and `beacon endpoint hooks status --harness openclaw` says so. OpenClaw does compute a per-turn price, from an operator-configured cost table rather than from a provider report, so Beacon does not record it as a reported cost. See [OpenClaw Gateway](/runtimes/openclaw-gateway).
Cline reports usage once per task rather than per model call, because Beacon's rollups sum `gen_ai.usage` across events and reporting at both granularities would count every token twice. fx reports cumulative totals, which Beacon differences into per-turn deltas for the same reason.
@@ -60,8 +60,8 @@ Cline reports usage once per task rather than per model call, because Beacon's r
| GitHub Copilot CLI | As above |
| VS Code Copilot | As above |
| Factory Droid | As above |
-| Grok Bot | Reaches Asymptote only through Cursor's server-side OpenTelemetry export, so usage arrives only if that export carries the semconv names |
-| goose | goose's `chat` spans carry the full `gen_ai.usage.*` set, cache reads and writes included, under the exact semconv names -- that much is read out of the runtime rather than hoped for. What is conditional is whether it arrives: usage reaches Asymptote only over OTLP, so a goose endpoint with hooks installed and `beacon endpoint install --harness goose` never run is correctly silent rather than faulty. goose reports no cost. See [goose](/runtimes/goose) |
+| Grok Bot | Reaches Beacon only through Cursor's server-side OpenTelemetry export, so usage arrives only if that export carries the semconv names |
+| goose | goose's `chat` spans carry the full `gen_ai.usage.*` set, cache reads and writes included, under the exact semconv names -- that much is read out of the runtime rather than hoped for. What is conditional is whether it arrives: usage reaches Beacon only over OTLP, so a goose endpoint with hooks installed and `beacon endpoint install --harness goose` never run is correctly silent rather than faulty. goose reports no cost. See [goose](/runtimes/goose) |
This table records what Beacon is built to read, not what your machine actually produced. A runtime can be listed here and still contribute nothing, because it was never run, or because its build reports no usage.
@@ -125,12 +125,12 @@ The status column is the report:
|--------|---------|
| `covered` | The runtime reported usage in the window. Nothing to do |
| `silent` | The runtime produced events but no usage, and Beacon is built to read usage from it. **This is the one to investigate** — a stale runtime build, a hook that stopped firing, or an OTLP export that is no longer configured |
-| `inactive` | Asymptote configured this runtime, but it produced no events at all in the window. Usually means it was not used; can also mean its hooks or OTLP export stopped firing |
+| `inactive` | Beacon configured this runtime, but it produced no events at all in the window. Usually means it was not used; can also mean its hooks or OTLP export stopped firing |
| `not_instrumented` | The runtime ran, and Beacon cannot read token usage from it. Expected, not a fault. The note column says why |
The `not_instrumented` distinction is what makes the report worth reading. Without it Cursor would appear as a problem on every run, and a column that always shows a problem is a column people stop reading.
-The `INSTALLED` column means "Asymptote configured this runtime", not "this product is on the machine". Only configuration Asymptote wrote counts — a hook command, a managed plugin marker, or a local OTLP endpoint it set. That is the population where silence is informative: Asymptote wired it up, so it should be reporting. A runtime present but configured by hand would not be reporting through Asymptote either way, so it appears only if it actually emits events.
+The `INSTALLED` column means "Beacon configured this runtime", not "this product is on the machine". Only configuration Beacon wrote counts — a hook command, a managed plugin marker, or a local OTLP endpoint it set. That is the population where silence is informative: Beacon wired it up, so it should be reporting. A runtime present but configured by hand would not be reporting through Beacon either way, so it appears only if it actually emits events.
Coverage applies the `--since`, `--until` and `--harness` scopes, and deliberately ignores `--session`, `--model`, `--repository` and `--run-id`. Those filters select usage-bearing events almost by definition — an event carries no model unless it carried a model call — so a coverage report computed over them would find every runtime covered and prove nothing.
diff --git a/docs/cli/upgrade.mdx b/docs/cli/upgrade.mdx
index dbfd6b57..fab7d491 100644
--- a/docs/cli/upgrade.mdx
+++ b/docs/cli/upgrade.mdx
@@ -18,6 +18,7 @@ When an update is available, Beacon prints the latest version, the installed ver
Upgrade Beacon with the standard Homebrew flow:
```bash title="Upgrade Beacon"
+brew trust asymptote-labs/tap
brew update
brew upgrade beacon
beacon version
diff --git a/docs/cli/version.mdx b/docs/cli/version.mdx
index cc8a0ecc..1722ca8b 100644
--- a/docs/cli/version.mdx
+++ b/docs/cli/version.mdx
@@ -35,7 +35,7 @@ $ beacon version check
Beacon v0.0.95 is available. Current version: v0.0.94
If installed with Homebrew: brew upgrade beacon
-Download: https://github.com/Asymptote-Labs/agent-beacon/releases/tag/v0.0.95
+Download: https://github.com/asymptote-labs/agent-beacon/releases/tag/v0.0.95
```
</Accordion>
@@ -54,6 +54,7 @@ Use `beacon version check` before upgrading to confirm whether a newer release i
```bash title="Use beacon version check before upgrading to confirm whether a newer release is available"
beacon version check
+brew trust asymptote-labs/tap
brew update
brew upgrade beacon
```
diff --git a/docs/concepts/core-concepts.mdx b/docs/concepts/core-concepts.mdx
index b4d907d6..dd8a8de0 100644
--- a/docs/concepts/core-concepts.mdx
+++ b/docs/concepts/core-concepts.mdx
@@ -1,27 +1,19 @@
---
title: "Core Concepts"
-description: "Core concepts for Asymptote, Agent Beacon, and agent runtime telemetry"
+description: "Core concepts for Beacon, Agent Beacon, and agent runtime telemetry"
---
-Asymptote observes AI agent runtime activity across supported local endpoints, CI jobs, cloud-agent sandboxes, and SDK-instrumented applications. Agent Beacon is the open-source foundation for local-first collection and customer-controlled forwarding. Asymptote Managed builds on that foundation with hosted ingest, retention, search, detections, governance, and investigations.
+Beacon observes AI agent runtime activity across supported local endpoints, CI jobs, cloud-agent sandboxes, and SDK-instrumented applications. Agent Beacon is the open-source foundation for local-first collection and customer-controlled forwarding. Beacon Managed builds on that foundation with hosted ingest, retention, search, detections, governance, and investigations.
-Use this page as a quick reference for terms used across Asymptote and Agent Beacon docs.
+Use this page as a quick reference for terms used across Beacon and Agent Beacon docs.
-## Asymptote Open Source
+## Beacon
-**Asymptote Open Source** is the open-source telemetry path built on Agent Beacon. It collects supported agent activity across local endpoints, CI jobs, and cloud-agent surfaces, normalizes that activity into Beacon-compatible records, and leaves storage and forwarding under customer control. See [Open Source deployment](/deployment/open-source).
+**Beacon** is the open-source, local-first telemetry system for supported AI agent activity. It collects events from local endpoints, CI jobs, and cloud-agent surfaces, normalizes them into consistent records, writes local JSONL, serves a local dashboard, and supports customer-managed forwarding. See [Open Source deployment](/deployment/open-source).
-## Agent Beacon
+## Beacon Managed
-**Agent Beacon** is the local-first endpoint telemetry agent in the `agent-beacon` repository. Beacon configures supported agent harnesses, receives OTLP or hook telemetry, writes local JSONL, serves the local dashboard, and can generate forwarding content for customer-managed destinations.
-
-## Asymptote Managed
-
-**Asymptote Managed** is the hosted Asymptote operating model for centralized ingest, retention, search, detections, fleet visibility, policy controls, identity mapping, approvals, SSO, RBAC, audit trails, and investigation workflows. See [Managed deployment](/deployment/managed).
-
-## Private deployment
-
-**Private Deployment** applies managed capabilities with stronger infrastructure ownership, data isolation, residency, or custom retention requirements. See [Hosting Options](/deployment/hosting-options).
+**Beacon Managed** is the hosted Beacon operating model for centralized ingest, retention, search, detections, fleet visibility, identity mapping, approval visibility, SSO, RBAC, audit trails, and investigation workflows. See [Managed deployment](/deployment/managed).
## Endpoint agent
@@ -50,7 +42,7 @@ environment becomes available, so early bootstrap turns may precede telemetry.
## Observe SDK
-The **Observe SDK** is the `@asymptote/sdk` TypeScript package for instrumenting cloud-hosted agent applications, services, workers, serverless functions, and agent SDK integrations. It can export to Asymptote Managed hosted Observe or to a customer-managed OTLP collector. See [Asymptote Observe SDK](/sdk).
+The **Observe SDK** is the `@asymptote/sdk` TypeScript package for instrumenting cloud-hosted agent applications, services, workers, serverless functions, and agent SDK integrations. It can export to Beacon Managed hosted Observe or to a customer-managed OTLP collector. See [Beacon Observe SDK](/sdk).
## Local collector
@@ -156,7 +148,7 @@ The **dashboard** is a loopback-only local view over Beacon runtime logs. It inc
<Columns cols={2}>
<Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
- Compare Asymptote Open Source, Managed, and Private Deployment paths.
+ Compare Beacon, Managed, and Private Deployment paths.
</Card>
<Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">
See how runtime telemetry flows through collection, normalization, and local outputs.
@@ -176,7 +168,7 @@ The **dashboard** is a loopback-only local view over Beacon runtime logs. It inc
<Card title="Log forwarding" icon="tower-broadcast" href="/log-forwarding">
Forward Beacon events into Wazuh, Splunk HEC, Falcon LogScale, Elastic, Datadog, Sumo Logic, Rapid7 InsightIDR, Microsoft Sentinel, AWS S3, Google Cloud Storage, or customer-managed pipelines.
</Card>
- <Card title="Asymptote Observe SDK" icon="code" href="/sdk">
+ <Card title="Beacon Observe SDK" icon="code" href="/sdk">
Instrument cloud-hosted agent applications with hosted or customer-managed export.
</Card>
</Columns>
diff --git a/docs/concepts/faq.mdx b/docs/concepts/faq.mdx
index 1c9b3517..0539d6b4 100644
--- a/docs/concepts/faq.mdx
+++ b/docs/concepts/faq.mdx
@@ -1,13 +1,13 @@
---
title: "FAQ"
-description: "Clear answers about Agent Beacon open source telemetry and Asymptote Managed architecture"
+description: "Clear answers about Agent Beacon open source telemetry and Beacon Managed architecture"
---
This FAQ answers common architecture, telemetry, and deployment questions about
-Asymptote and the open-source [Agent Beacon](https://github.com/Asymptote-Labs/agent-beacon)
+Beacon and the open-source [Agent Beacon](https://github.com/asymptote-labs/agent-beacon)
project.
-## Asymptote Open Source: Agent Beacon
+## Beacon and Agent Beacon
Agent Beacon is the local-first, open-source telemetry path. It collects
supported agent runtime activity, writes normalized local JSONL, and supports
@@ -30,7 +30,7 @@ Coverage depends on the runtime surface. See the [agent harness integration
model](/runtimes/integration-model) and [data inventory](/security/data-inventory)
for runtime-specific details.
-### Can Beacon see the agent's full context window?
+### Ca Beacon see the agent's full context window?
Only when the runtime exposes context-bearing telemetry. Beacon can retain
prompt text, tool results, command output, file activity, and related content
@@ -41,7 +41,7 @@ For cloud-agent surfaces, context coverage is often narrower than local endpoint
coverage because the cloud provider controls which hooks or telemetry events are
available.
-### Can Beacon detect unexpected data entering the agent context?
+### Ca Beacon detect unexpected data entering the agent context?
Beacon can help investigate this when the data appears in emitted prompts, tool
results, command output, file activity, or retained content. That can make it
@@ -101,7 +101,7 @@ S3](/guides/fleet-s3-mdm).
For provider-managed cloud-agent proof-of-concept flows, the current self-serve
path uses Google Cloud Storage. Production cloud-agent ingest is handled through
-Asymptote Managed or a customer-approved forwarding design.
+Beacon Managed or a customer-approved forwarding design.
### Can open-source Beacon forward logs to Datadog or a SIEM?
@@ -139,46 +139,46 @@ For Vector-based paths, Vector owns checkpointing, batching, retries, and
destination delivery. Beacon's responsibility is to keep writing normalized
events to the local handoff file.
-### Does open-source Beacon require a hosted Asymptote backend?
+### Does open-source Beacon require a hosted Beacon backend?
No. The open-source endpoint path is local-first. Normal local hook execution,
local collection, local JSONL, the local dashboard, local scans, and
-customer-managed forwarding do not require a hosted Asymptote account.
+customer-managed forwarding do not require a hosted Beacon account.
-## Asymptote Managed
+## Beacon Managed
-Asymptote Managed adds centralized ingest, retention, search, detections,
+Beacon Managed adds centralized ingest, retention, search, detections,
governance, identity, approvals, access control, and investigation workflows on
top of the open-source Beacon foundation.
-### Does Asymptote Managed provide a central console?
+### Does Beacon Managed provide a central console?
-Yes. Asymptote Managed provides the centralized operating layer for fleet-wide
+Yes. Beacon Managed provides the centralized operating layer for fleet-wide
visibility, search, detections, investigations, policy workflows, identity
mapping, approvals, SSO, RBAC, and audit trails.
Use Managed when local JSONL and customer-managed forwarding are not enough for
company-wide operations.
-### Should telemetry point to Asymptote or directly to the SIEM?
+### Should telemetry point to Beacon or directly to the SIEM?
Both patterns are valid.
With Agent Beacon open source, telemetry can go directly from local JSONL into
-customer-controlled SIEM, log, or object-storage destinations. With Asymptote
-Managed, telemetry is sent to Asymptote for centralized search, detections,
+customer-controlled SIEM, log, or object-storage destinations. With Beacon
+Managed, telemetry is sent to Beacon for centralized search, detections,
governance, and investigations, with downstream forwarding available as part of
the deployment design.
-### Does Asymptote Managed replace the SIEM?
+### Does Beacon Managed replace the SIEM?
-No. Asymptote is focused on agent-specific visibility, governance, and
+No. Beacon is focused on agent-specific visibility, governance, and
investigation workflows. SIEMs and log platforms remain important downstream
destinations for broader security operations, retention, and correlation.
-### How does Asymptote capture telemetry from cloud-hosted agent apps?
+### How does Beacon capture telemetry from cloud-hosted agent apps?
-Cloud-hosted agent applications use the Asymptote Observe SDK and managed
+Cloud-hosted agent applications use the Beacon Observe SDK and managed
ingest. The SDK instruments services, workers, serverless functions, and agent
SDK integrations so agent activity can be captured from application code.
@@ -186,10 +186,10 @@ Provider-managed cloud agents use surface-specific setup paths where supported.
Those paths depend on the hooks, setup scripts, storage exports, or OTLP
surfaces the provider exposes.
-### How does Asymptote collect Claude Cowork telemetry?
+### How does Beacon collect Claude Cowork telemetry?
Claude Cowork is configured in the Claude organization admin settings. Anthropic's
-service exports OTLP telemetry to a durable collector endpoint, and Asymptote
+service exports OTLP telemetry to a durable collector endpoint, and Beacon
normalizes the received events through the same Claude event pipeline used for
Claude Code. Supported source attributes become canonical prompts, assistant
responses, approvals, commands, files, MCP activity, model usage, token counts,
@@ -204,7 +204,7 @@ identify the Beacon collector machine.
### Where should a cloud AI tenant send OTLP telemetry?
In a Managed deployment, the cloud service or tenant can export OTLP to an
-Asymptote-managed collector endpoint when that runtime supports it.
+Beacon-managed collector endpoint when that runtime supports it.
In a private or customer-managed design, the OTLP endpoint may instead point to a
customer-controlled collector or forwarding layer. The right target depends on
@@ -212,9 +212,9 @@ the deployment model, data-boundary requirements, and destination architecture.
### Does managed require a customer-hosted management server?
-Not necessarily. In Asymptote Managed, Asymptote operates the managed ingest and
+Not necessarily. In Beacon Managed, Beacon operates the managed ingest and
control-plane services. For private deployments or stricter infrastructure
-requirements, Asymptote can work with the customer on dedicated or
+requirements, Beacon can work with the customer on dedicated or
customer-controlled deployment boundaries.
Open-source Beacon does not require a management server. It can write local JSONL
@@ -228,20 +228,20 @@ investigations can then reconstruct what the agent did, which tools it used, wha
content was retained, and which user or workflow it maps to.
If a cloud or non-engineering surface does not expose the relevant context,
-Asymptote cannot infer it from outside the platform. The value comes from the
+Beacon cannot infer it from outside the platform. The value comes from the
runtime signals the platform or instrumented application emits.
## Related
<Columns cols={2}>
<Card title="System Architecture" icon="diagram-project" href="/architecture/system-architecture">
- Compare the open-source Agent Beacon architecture with Asymptote Managed.
+ Compare the open-source Agent Beacon architecture with Beacon Managed.
</Card>
<Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">
Review local collection, normalization, storage, and forwarding.
</Card>
- <Card title="Managed Architecture" icon="cloud" href="/architecture/managed-architecture">
- Review centralized ingest, governance, detections, and investigations.
+ <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ Review managed ingest, governance, investigations, and rollout support.
</Card>
<Card title="Log Forwarding" icon="tower-broadcast" href="/log-forwarding">
Forward Beacon events into SIEMs, log platforms, object storage, or custom pipelines.
diff --git a/docs/concepts/vector-forwarding.mdx b/docs/concepts/vector-forwarding.mdx
index 5cd7daac..73e03734 100644
--- a/docs/concepts/vector-forwarding.mdx
+++ b/docs/concepts/vector-forwarding.mdx
@@ -5,7 +5,7 @@ description: "How customer-managed Vector pipelines forward Beacon endpoint even
```mermaid
flowchart LR
- subgraph openSourcePath [Asymptote Open Source]
+ subgraph openSourcePath [Beacon]
agentHarnesses["Agent harnesses"] -->|"OTLP or hooks"| beaconEndpoint["Beacon endpoint"]
beaconEndpoint -->|"normalizes events"| runtimeLog["runtime.jsonl"]
runtimeLog -->|"file source tails log"| vectorAgent["Vector host agent"]
@@ -14,8 +14,8 @@ flowchart LR
vectorPipeline -->|"other sinks"| customerDestinations["GCS, CloudWatch, Sumo, Rapid7, Falcon"]
end
- subgraph managedPath [Asymptote Managed]
- managedSources["Endpoint, CI, cloud, and SDK telemetry"] -->|"managed ingest"| managedIngest["Asymptote ingest"]
+ subgraph managedPath [Beacon Managed]
+ managedSources["Endpoint, CI, cloud, and SDK telemetry"] -->|"managed ingest"| managedIngest["Beacon ingest"]
managedIngest --> managedPlatform["Hosted search, detections, governance, investigations"]
end
@@ -32,7 +32,7 @@ platform.
## Open source and managed
-In **Asymptote Open Source**, Agent Beacon is local-first. It configures supported agent harnesses, receives OTLP or hook telemetry, normalizes events, writes local runtime and inventory JSONL, and can generate forwarding content packs. Destination credentials, bucket policies, IAM roles, lifecycle rules, retention, encryption, and remote ingestion settings stay outside Beacon endpoint configuration.
+In **Beacon**, Agent Beacon is local-first. It configures supported agent harnesses, receives OTLP or hook telemetry, normalizes events, writes local runtime and inventory JSONL, and can generate forwarding content packs. Destination credentials, bucket policies, IAM roles, lifecycle rules, retention, encryption, and remote ingestion settings stay outside Beacon endpoint configuration.
That is where Vector fits. For open-source deployments, Vector is an optional customer-managed forwarder. You install and operate Vector through MDM, endpoint management, launchd, systemd, Kubernetes, or your normal host-agent tooling. Beacon can generate a destination-specific `vector.toml`, but Vector owns:
@@ -44,7 +44,7 @@ That is where Vector fits. For open-source deployments, Vector is an optional cu
- Retrying transient failures.
- Holding destination URLs, tokens, IAM roles, cloud credentials, and destination-specific settings.
-In **Asymptote Managed**, the main path is different. Managed deployments use Asymptote-hosted ingest, retention, search, detections, governance, identity mapping, and investigation workflows. Vector is not the required managed-ingest architecture. You might still use a customer-managed Vector pipeline for an additional archive or downstream copy, but the core managed product provides the central pipeline and operational surface.
+In **Beacon Managed**, the main path is different. Managed deployments use Beacon-hosted ingest, retention, search, detections, governance, identity mapping, and investigation workflows. Vector is not the required managed-ingest architecture. You might still use a customer-managed Vector pipeline for an additional archive or downstream copy, but the core managed product provides the central pipeline and operational surface.
## Why the handoff is local
@@ -300,7 +300,7 @@ Use the official Vector docs when adapting generated templates:
See how Agent Beacon runs local-first with customer-controlled storage and forwarding.
</Card>
<Card title="Managed deployment" icon="cloud" href="/deployment/managed">
- Understand the hosted Asymptote ingest, retention, search, detections, governance, and investigation model.
+ Understand the hosted Beacon ingest, retention, search, detections, governance, and investigation model.
</Card>
<Card title="Endpoint event schema" icon="code" href="/telemetry-schema/event-schema">
Review normalized Beacon JSONL fields and example events.
diff --git a/docs/deployment/hosting-options.mdx b/docs/deployment/hosting-options.mdx
index 18aa7581..720529d3 100644
--- a/docs/deployment/hosting-options.mdx
+++ b/docs/deployment/hosting-options.mdx
@@ -1,30 +1,75 @@
---
title: "Hosting Options"
-description: "Choose between Open Source, Managed, and Private Deployment paths"
+description: "Choose between local Beacon and Beacon Managed"
---
-Asymptote can start local-first with the open-source [Agent Beacon](/concepts/core-concepts#agent-beacon) [endpoint agent](/concepts/core-concepts#endpoint-agent), run as [Asymptote Managed](/concepts/core-concepts#asymptote-managed), or deploy privately for teams with stricter infrastructure requirements.
-
-| Hosting Option | Use it when | Data and operations model |
-| -------------- | ----------- | ------------------------- |
-| [Asymptote Open Source](/concepts/core-concepts#asymptote-open-source) | You want endpoint telemetry, local JSONL, and customer-managed forwarding. | Beacon runs on the endpoint and writes local logs by default. |
-| [Asymptote Managed](/concepts/core-concepts#asymptote-managed) | You need centralized visibility, policy controls, investigations, SSO/RBAC, audit trails, and rollout support. | Asymptote provides managed ingest, retention, search, detections, and enterprise operations. |
-| [Asymptote Private Deployment](/concepts/core-concepts#private-deployment) | You want Managed capabilities with stronger isolation, residency, or infrastructure ownership requirements. | Asymptote works with you on dedicated infrastructure and custom deployment boundaries. |
-
-## Asymptote Open Source
-
-Use the open-source local path when you want endpoint telemetry without a hosted Asymptote backend. Agent Beacon runs on the endpoint, writes normalized events to local JSONL, and can forward events into customer-managed security workflows.
-
-```bash title="Install Beacon"
-brew tap asymptote-labs/tap
-brew install beacon
-beacon version
-```
-
-```bash title="Configure local endpoint telemetry"
-beacon endpoint install
-beacon endpoint status
-```
+Both options are free. Run Beacon locally with full control of your data, or use [Beacon Managed](/concepts/core-concepts#beacon-managed) for hosted storage, search, analytics, and unlimited retention.
+
+| Capability | Local | Beacon Managed |
+| --- | --- | --- |
+| Cross-harness agent telemetry | ✓ | ✓ |
+| Local, CI & cloud collection | ✓ | ✓ |
+| Unified agent session history | ✓ | ✓ |
+| Store data locally | ✓ | ✓ |
+| Forward to your own data stack | ✓ | ✓ |
+| Hosted ingest & storage | — | ✓ |
+| Search & analytics | — | ✓ |
+| Identity mapping | — | ✓ |
+| **Agent Session Retention** | **You manage** | **Unlimited** |
+| SSO & RBAC | — | ✓ |
+
+## Local
+
+Use the open-source local path when you want endpoint telemetry without a hosted Beacon backend. Agent Beacon runs on the endpoint, writes normalized events to local JSONL, and can forward events into customer-managed security workflows.
+
+<Tabs>
+ <Tab title="macOS">
+ Install Beacon with Homebrew:
+
+ ```bash
+ brew trust asymptote-labs/tap
+ brew tap asymptote-labs/tap
+ brew install beacon
+ beacon version
+ ```
+
+ Then configure local endpoint telemetry:
+
+ ```bash
+ beacon endpoint install
+ beacon endpoint status
+ ```
+
+ See the [macOS install guide](/platforms/macos) for package and fleet deployment options.
+ </Tab>
+ <Tab title="Windows">
+ Download `BeaconEndpointAgent-<version>-x64.msi` from the [latest release](https://github.com/asymptote-labs/agent-beacon/releases/latest), then run PowerShell as an administrator:
+
+ ```powershell
+ msiexec /i BeaconEndpointAgent-<version>-x64.msi
+ & "$env:ProgramFiles\Beacon\bin\beacon.exe" endpoint status --system
+ ```
+
+ The MSI installs and starts the endpoint service. See the [Windows install guide](/platforms/windows) for silent installation and checksum verification.
+ </Tab>
+ <Tab title="Linux">
+ Download the `.deb` or `.rpm` for your architecture from the [latest release](https://github.com/asymptote-labs/agent-beacon/releases/latest):
+
+ <CodeGroup>
+ ```bash title="Debian, Ubuntu"
+ sudo apt install ./beacon_<version>_linux_amd64.deb
+ beacon endpoint status --system
+ ```
+
+ ```bash title="Fedora, RHEL, Rocky, Alma"
+ sudo dnf install ./beacon_<version>_linux_amd64.rpm
+ beacon endpoint status --system
+ ```
+ </CodeGroup>
+
+ Replace `amd64` with `arm64` on ARM systems. See the [Linux install guide](/platforms/linux) for rootless and tarball installation.
+ </Tab>
+</Tabs>
Open the local dashboard to inspect runtime inventory, timelines, filters, and event details:
@@ -34,20 +79,22 @@ beacon endpoint dashboard --open
The local path preserves `runtime.jsonl` on the endpoint and supports optional forwarding to supported SIEM, observability, object-storage, local JSONL, and customer-managed destinations.
-See [Asymptote Open Source](/deployment/open-source) for setup details and [Security & IT Rollout Guide](/security) for managed endpoint deployment.
+See [Local](/deployment/open-source) for setup details and [Security & IT Rollout Guide](/security) for managed endpoint deployment.
-## Asymptote Managed
+## Beacon Managed
Use Managed when you want hosted visibility, governance, and enterprise rollout support for agent activity.
-1. Request access at [asymptotelabs.ai/contact](https://asymptotelabs.ai/contact).
-2. Configure your workspace with the runtimes and teams you want to observe.
-3. Use the Asymptote Observe SDK for cloud-hosted agents, services, workers, and serverless functions.
-4. Deploy Agent Beacon on endpoints and run [`beacon endpoint connect`](/cli/endpoint-connect) on each so their telemetry reaches the dashboard.
+1. [Create a Beacon account](https://beacon.sh/sign-up).
+2. Connect each endpoint to your account:
-Managed adds centralized ingest, retention, search, detections, fleet-wide visibility, policy controls, identity mapping, approvals, investigation workflows, SSO, RBAC, audit trails, and enterprise onboarding on top of the open-source Agent Beacon foundation.
+```bash
+beacon endpoint connect --dashboard-url https://beacon.sh
+```
+
+Beacon Managed gives you the open-source Agent Beacon experience without having to run the backend yourself.
-For cloud-hosted agent applications, install the [Observe SDK](/concepts/core-concepts#observe-sdk) and initialize hosted export with an Asymptote API key:
+For cloud-hosted agent applications, install the [Observe SDK](/concepts/core-concepts#observe-sdk) and initialize hosted export with a Beacon API key:
```bash title="Set the hosted Observe API key"
export ASYMPTOTE_API_KEY=...
@@ -61,33 +108,25 @@ Observe.initialize({
});
```
-See [Asymptote Managed](/deployment/managed) for managed platform capabilities and [SDK Quickstart](/sdk/quickstart) for cloud instrumentation details.
-
-## Asymptote Private Deployment
-
-Use Private Deployment when Managed is the right operating model, but your organization needs dedicated infrastructure, stricter data boundaries, custom retention, or residency requirements.
-
-Private Deployment can include customer-controlled or private-cloud deployment options, custom forwarding architecture, coverage across endpoints and execution environments, and dedicated deployment engineering.
-
-[Contact us](https://asymptotelabs.ai/contact) to discuss Managed or Private Deployment requirements.
+See [Beacon Managed](/deployment/managed) for managed platform capabilities and [SDK Quickstart](/sdk/quickstart) for cloud instrumentation details.
## Related
<Columns cols={2}>
- <Card title="Asymptote Managed" icon="key" href="/deployment/managed">
+ <Card title="Beacon Managed" icon="key" href="/deployment/managed">
Review managed ingest, governance, investigations, access control, and rollout support.
</Card>
- <Card title="Asymptote Open Source" icon="download" href="/deployment/open-source">
+ <Card title="Local" icon="download" href="/deployment/open-source">
Install Beacon, configure endpoint telemetry, and keep the CLI up to date.
</Card>
<Card title="Quickstart" icon="rocket" href="/get-started/quickstart">
- Choose the right path for a local, managed, or private rollout.
+ Choose the right path for a local or managed rollout.
</Card>
- <Card title="Asymptote Observe SDK" icon="code" href="/sdk/quickstart">
+ <Card title="Beacon Observe SDK" icon="code" href="/sdk/quickstart">
Instrument cloud-hosted agent applications with hosted or customer-managed export.
</Card>
- <Card title="Asymptote Overview" icon="diagram-project" href="/get-started/overview">
- See how the open-source Beacon foundation fits into managed and private deployment paths.
+ <Card title="Beacon Overview" icon="diagram-project" href="/get-started/overview">
+ See how local Beacon fits with Beacon Managed.
</Card>
<Card title="Log Forwarding" icon="tower-broadcast" href="/log-forwarding">
Forward local Beacon events into security and observability platforms.
diff --git a/docs/deployment/managed.mdx b/docs/deployment/managed.mdx
index 1ecfa7a7..663e4450 100644
--- a/docs/deployment/managed.mdx
+++ b/docs/deployment/managed.mdx
@@ -1,80 +1,40 @@
---
-title: "Asymptote Managed"
-description: "Managed visibility, governance, and investigations for agent activity at scale"
-tag: "Enterprise"
+title: "Beacon Managed"
+description: "Hosted storage, search, and long-term history for your agent sessions"
---
-Asymptote Managed builds on the open-source Agent Beacon foundation for teams that need centralized operations, policy controls, and investigation workflows across a fleet.
+The easiest way to use Beacon without running your own backend.
-Use this path when local JSONL and customer-managed forwarding are not enough on their own, or when agent adoption has moved beyond a small local pilot.
+Beacon Managed gives individual developers hosted storage, search, and long-term history for their agent sessions.
-## What managed adds
+Install Beacon, connect your account, and your traces are automatically available in one place across the agents you use.
-Asymptote Managed includes the open-source capture and forwarding paths, then adds the managed services needed to operate agent security at company scale.
+## What Beacon Managed gives you
-| Capability | What managed adds beyond open source |
+| Capability | Beacon Managed |
| --- | --- |
-| Managed ingest and retention | Centralized collection, retention, search, and detections for agent activity |
-| Fleet-wide visibility | Inventory across endpoints, agent harnesses, users, and teams |
-| Policy controls | Policy enforcement workflows, identity mapping, and approval visibility |
-| Investigations | Timelines and case workflows for reviewing prompts, tools, file access, and agent actions |
-| Access control | SSO, role-based access control, and audit trails |
-| Operations support | Priority support, onboarding, and rollout guidance |
+| Hosted ingest | Send Beacon traces to a managed backend |
+| Unlimited retention | Keep your agent history over time |
+| Search | Find past sessions, prompts, commands, and tool calls |
+| Cross-harness history | See activity from Claude Code, Cursor, Codex, and more in one place |
+| Analytics | Understand usage, tokens, workflows, and runtime behavior |
+| Knowledge | Surface recurring workflows, corrections, and useful patterns |
+| No backend to run | Asymptote handles storage and infrastructure |
-## Core managed workflows
+## One place for all your agent history
-### Centralize runtime visibility
+Your agent history is usually split across different tools and local session files.
-Managed ingest turns endpoint and cloud-agent telemetry into searchable fleet-wide visibility. Security teams can review which agents are running, which tools they use, and what sensitive files or data are involved in agent activity.
+Beacon Managed brings those traces together into one searchable timeline, so you can quickly find past work, revisit how you solved something, and compare sessions across harnesses.
-Endpoints join with [`beacon endpoint connect`](/cli/endpoint-connect): the CLI opens the dashboard, a member of the organization approves the specific device, and a Vector forwarder ships the machine's runtime and inventory JSONL with a per-device key that the dashboard's Beacon Endpoints page can revoke at any time. The first interactive `beacon endpoint install` offers the same step. Enrollment is interactive per device today; headless enrollment for MDM fleets is a planned follow-up.
+## Keep what your agents learn
-For provider-managed cloud agents, Managed avoids proof-of-concept patterns such
-as placing storage service-account keys directly into cloud sandbox environment
-variables. Asymptote can operate the secure ingest and retention layer for you,
-or work with your team on a production-grade forwarding design in
-customer-managed infrastructure.
+The more you use agents, the more useful history you create.
-### Govern agent activity
+Beacon Managed keeps that history over time so successful workflows, debugging patterns, repeated corrections, and repository knowledge do not disappear when a session ends.
-Policy, identity mapping, and approvals help teams connect runtime actions back to users and workflows. Use this when you need governance beyond a local audit log or SIEM-forwarded event stream.
+## Start in minutes
-### Investigate agent behavior
+Install Beacon, connect to Beacon Managed, and keep using your existing agents.
-Investigation timelines and case workflows organize prompts, tool calls, file access, command execution, and related context so security teams can reconstruct what happened during an agent session.
-
-### Support enterprise rollout
-
-Managed deployments include rollout planning, onboarding, and support for teams deploying across endpoints and execution environments.
-
-## Private deployment
-
-For regulated teams that need dedicated infrastructure or stricter data boundaries, Asymptote supports private cloud or customer-controlled deployment options.
-
-Private deployment can include:
-
-- complete data isolation and residency options
-- custom retention and forwarding architecture
-- coverage across endpoints and execution environments
-- dedicated deployment engineering and rollout planning
-
-## Get access
-
-Request access or discuss deployment requirements at [asymptotelabs.ai/contact](https://asymptotelabs.ai/contact). For plan details, see [Asymptote pricing](https://asymptotelabs.ai/pricing).
-
-## Related
-
-<Columns cols={2}>
- <Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
- Compare Open Source, Managed, and Private Deployment paths.
- </Card>
- <Card title="Asymptote Open Source" icon="download" href="/deployment/open-source">
- Install Beacon locally and configure endpoint telemetry.
- </Card>
- <Card title="Security & IT Rollout Guide" icon="building-shield" href="/security">
- Plan endpoint inventory, MDM rollout, validation, retention, and forwarding.
- </Card>
- <Card title="Asymptote Observe SDK" icon="code" href="/sdk/quickstart">
- Instrument cloud-hosted agent applications with Asymptote telemetry.
- </Card>
-</Columns>
+No database, storage bucket, or indexing infrastructure required.
diff --git a/docs/deployment/open-source.mdx b/docs/deployment/open-source.mdx
index f43fe151..4c82de70 100644
--- a/docs/deployment/open-source.mdx
+++ b/docs/deployment/open-source.mdx
@@ -1,26 +1,53 @@
---
-title: "Asymptote Open Source"
-description: "Install Beacon, configure open-source telemetry, and keep the CLI up to date"
+title: "Local"
+description: "Install Beacon locally, configure telemetry, and keep the CLI up to date"
---
-Install Beacon with Homebrew, configure the local endpoint telemetry path, and use the repair workflow when you need to reapply configuration after an upgrade. For CI, cloud-agent, and SDK setup paths, see [Agent harness integrations](/runtimes).
-
-<Frame>
- <iframe
- src="https://www.loom.com/embed/b39038879dc24b10af9e603ad4e03fb6?t=0s"
- title="Asymptote Open Source installation walkthrough"
- allowFullScreen
- style={{ aspectRatio: "16 / 9", width: "100%", border: 0 }}
- />
-</Frame>
+Install Beacon on macOS, Windows, or Linux, configure the local endpoint telemetry path, and use the repair workflow when you need to reapply configuration after an upgrade. For CI, cloud-agent, and SDK setup paths, see [Agent harness integrations](/runtimes).
## Install Beacon
-```bash title="Install Beacon"
-brew tap asymptote-labs/tap
-brew install beacon
-beacon version
-```
+<Tabs>
+ <Tab title="macOS">
+ Install Beacon with Homebrew:
+
+ ```bash
+ brew trust asymptote-labs/tap
+ brew tap asymptote-labs/tap
+ brew install beacon
+ beacon version
+ ```
+
+ See the [macOS install guide](/platforms/macos) to configure endpoint telemetry or deploy the signed package to a fleet.
+ </Tab>
+ <Tab title="Windows">
+ Download `BeaconEndpointAgent-<version>-x64.msi` from the [latest release](https://github.com/asymptote-labs/agent-beacon/releases/latest), then run PowerShell as an administrator:
+
+ ```powershell
+ msiexec /i BeaconEndpointAgent-<version>-x64.msi
+ & "$env:ProgramFiles\Beacon\bin\beacon.exe" version
+ ```
+
+ See the [Windows install guide](/platforms/windows) for silent installation, checksum verification, and service management.
+ </Tab>
+ <Tab title="Linux">
+ Download the `.deb` or `.rpm` for your architecture from the [latest release](https://github.com/asymptote-labs/agent-beacon/releases/latest):
+
+ <CodeGroup>
+ ```bash title="Debian, Ubuntu"
+ sudo apt install ./beacon_<version>_linux_amd64.deb
+ beacon version
+ ```
+
+ ```bash title="Fedora, RHEL, Rocky, Alma"
+ sudo dnf install ./beacon_<version>_linux_amd64.rpm
+ beacon version
+ ```
+ </CodeGroup>
+
+ Replace `amd64` with `arm64` on ARM systems. See the [Linux install guide](/platforms/linux) for rootless and tarball installation.
+ </Tab>
+</Tabs>
<Accordion title="Example output">
```bash title="beacon version output"
@@ -34,16 +61,19 @@ beacon version 0.0.48
Setting up the endpoint differs by operating system. Start with your platform if you want the
packages, service management, and fleet deployment for it:
-<Columns cols={2}>
+<Columns cols={3}>
<Card title="macOS" icon="apple" href="/platforms/macos">
Homebrew, or the signed `.pkg` for MDM. launchd.
</Card>
+ <Card title="Windows" icon="windows" href="/platforms/windows">
+ `.msi` for x64. Windows service.
+ </Card>
<Card title="Linux" icon="linux" href="/platforms/linux">
`.deb` and `.rpm` packages. systemd.
</Card>
</Columns>
-The per-user install below works the same on both, and is the quickest way to try it on one machine:
+The Windows MSI and Linux packages configure a system endpoint during installation. For a Homebrew, tarball, or other CLI-only install, configure a per-user endpoint:
```bash title="Configure endpoint telemetry"
beacon endpoint install
@@ -57,7 +87,7 @@ beacon endpoint install --harness claude,codex,gemini
```
<Note>
- System-mode install (`--system`) is supported on macOS and on Linux distributions that use systemd. The default mode uses per-user paths; use `--system` as root for package or MDM deployments. On Linux, installing the `.deb` or `.rpm` does the system install for you. See [Linux](/platforms/linux).
+ System-mode install (`--system`) is supported on macOS, Linux distributions that use systemd, and Windows. The default mode uses per-user paths; package installers configure system mode for you.
</Note>
Beacon records supported prompt, tool, command, file, approval, policy, and runtime context when the source runtime emits it. Before events are written to `runtime.jsonl` or sent through configured destinations, Beacon applies redaction, sanitization, truncation, and event-size limits.
@@ -70,6 +100,7 @@ Use the standard Homebrew upgrade flow, then reapply endpoint configuration if n
```bash title="Upgrade Beacon"
beacon version check
+brew trust asymptote-labs/tap
brew update
brew upgrade beacon
beacon endpoint repair
@@ -81,7 +112,7 @@ beacon endpoint repair
<Columns cols={2}>
<Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
- Choose between Asymptote Cloud and the open-source Agent Beacon path.
+ Choose between Beacon Cloud and the open-source Agent Beacon path.
</Card>
<Card title="Endpoint paths and ports" icon="folder-tree" href="/cli/endpoint-paths">
Review files, logs, collector config, ports, and hook locations.
diff --git a/docs/detections/index.mdx b/docs/detections/index.mdx
index b476dd9f..cff0a7f7 100644
--- a/docs/detections/index.mdx
+++ b/docs/detections/index.mdx
@@ -12,7 +12,7 @@ Use detections when you want to review local agent activity for risky commands,
The detection format is open and lives in the Agent Beacon repository. Rules are YAML documents with CEL match expressions, metadata, and embedded test fixtures. The detection engine ships with the Beacon CLI, while rule packs are external data that can be installed, updated, and linted separately from the binary.
<Note>
- Local scanning is read-only and offline. `beacon scan` does not fetch rule packs, send telemetry to Asymptote, mutate endpoint configuration, or change the runtime log.
+ Local scanning is read-only and offline. `beacon scan` does not fetch rule packs, send telemetry to Beacon, mutate endpoint configuration, or change the runtime log.
</Note>
## Quickstart
@@ -198,7 +198,7 @@ Use the [Detection YAML Schema](/detections/yaml-schema) page for the rule docum
## Managed detections
-The open-source Beacon flow runs detections locally over endpoint JSONL. [Asymptote Managed](/deployment/managed) builds on the same telemetry foundation with centralized ingest, retention, search, detections, fleet-wide visibility, policy workflows, identity mapping, SSO/RBAC, and investigation workflows.
+The open-source Beacon flow runs detections locally over endpoint JSONL. [Beacon Managed](/deployment/managed) builds on the same telemetry foundation with centralized ingest, retention, search, detections, fleet-wide visibility, policy workflows, identity mapping, SSO/RBAC, and investigation workflows.
Use local Beacon detections when you need offline endpoint checks or customer-controlled forwarding. Use Managed when you need centralized review across a fleet or organization.
diff --git a/docs/docs.json b/docs/docs.json
index c05c760c..fef82f51 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -10,7 +10,7 @@
"fonts": {
"family": "Familjen Grotesk"
},
- "favicon": "/images/favicon.ico",
+ "favicon": "/images/beacon-favicon.svg",
"navigation": {
"style": "sidebar",
"global": {
@@ -29,7 +29,7 @@
"anchor": "GitHub",
"icon": "github",
"iconType": "brands",
- "href": "https://github.com/Asymptote-Labs/agent-beacon",
+ "href": "https://github.com/asymptote-labs/agent-beacon",
"color": {
"light": "#24292F",
"dark": "#FFFFFF"
@@ -48,27 +48,20 @@
"pages": [
"index",
"get-started/overview",
- {
- "group": "Quickstart",
- "root": "get-started/quickstart",
- "pages": [
- "get-started/quickstart-security-it",
- "get-started/quickstart-developers"
- ]
- }
+ "get-started/quickstart"
]
},
{
- "group": "Deploy Asymptote",
+ "group": "Deploy Beacon",
"icon": "cloud-arrow-up",
"pages": [
"deployment/hosting-options",
- "deployment/managed",
- "deployment/open-source"
+ "deployment/open-source",
+ "deployment/managed"
]
},
{
- "group": "How Asymptote Works",
+ "group": "How Beacon Works",
"icon": "book-open",
"pages": [
"concepts/core-concepts",
@@ -77,7 +70,6 @@
"root": "architecture/system-architecture",
"pages": [
"architecture/architecture",
- "architecture/managed-architecture",
"concepts/vector-forwarding"
]
},
@@ -94,19 +86,9 @@
]
},
{
- "group": "Manage Asymptote",
+ "group": "Manage Beacon",
"icon": "sliders",
"pages": [
- {
- "group": "Onboarding",
- "root": "manage/onboarding",
- "tag": "Enterprise",
- "pages": [
- "manage/configure-s3-data-connector",
- "manage/connect-okta",
- "manage/connect-slack"
- ]
- },
{
"group": "Inventory",
"root": "guides/inventory",
@@ -209,97 +191,15 @@
]
},
{
- "group": "For Security & IT Teams",
- "icon": "building-shield",
+ "group": "Security Overview",
+ "icon": "shield-check",
+ "root": "security/review",
"pages": [
- "security/index",
- {
- "group": "Security Overview",
- "root": "security/review",
- "pages": [
- "security/data-flow-threat-model",
- "security/data-inventory",
- "security/retention-redaction",
- "security/endpoint-operations",
- "security/policy"
- ]
- },
- {
- "group": "MDM Deployment",
- "root": "mdm/index",
- "pages": [
- {
- "group": "Jamf",
- "root": "mdm/jamf",
- "pages": [
- "mdm/jamf/claude",
- "guides/jamf-anthropic-openai-cursor-mdm",
- "guides/jamf-gcs-mdm",
- "guides/jamf-s3-mdm",
- "guides/jamf-falcon-mdm"
- ]
- },
- {
- "group": "Rippling",
- "root": "mdm/rippling",
- "pages": [
- "guides/rippling-gcs-mdm"
- ]
- },
- {
- "group": "Fleet",
- "root": "mdm/fleet",
- "pages": [
- "guides/fleet-s3-mdm"
- ]
- }
- ]
- },
- {
- "group": "Log Forwarding",
- "root": "log-forwarding/index",
- "pages": [
- "log-forwarding/ci-telemetry-exports",
- {
- "group": "Asymptote Managed",
- "pages": [
- "log-forwarding/asymptote"
- ]
- },
- {
- "group": "Security Information and Event Management (SIEM)",
- "pages": [
- "log-forwarding/falcon",
- "log-forwarding/microsoft-sentinel",
- "log-forwarding/rapid7",
- "log-forwarding/splunk",
- "log-forwarding/sumo",
- "log-forwarding/wazuh"
- ]
- },
- {
- "group": "Log Aggregation",
- "pages": [
- "log-forwarding/cloudwatch",
- "log-forwarding/customer-managed",
- "log-forwarding/datadog",
- "log-forwarding/elastic"
- ]
- },
- {
- "group": "Object Storage",
- "pages": [
- "guides/macos-object-storage-system"
- ]
- },
- {
- "group": "Local",
- "pages": [
- "log-forwarding/local-jsonl"
- ]
- }
- ]
- }
+ "security/data-flow-threat-model",
+ "security/data-inventory",
+ "security/retention-redaction",
+ "security/endpoint-operations",
+ "security/policy"
]
},
{
@@ -457,7 +357,7 @@
"icon": "code",
"groups": [
{
- "group": "Asymptote Observe SDK",
+ "group": "Beacon Observe SDK",
"icon": "code",
"pages": [
"sdk/index",
@@ -507,6 +407,7 @@
"pages": [
{
"group": "Validate Endpoint Telemetry",
+ "expanded": true,
"root": "guides/local-testing/endpoint-validation",
"pages": [
"guides/local-testing/health",
@@ -519,12 +420,64 @@
]
},
{
- "group": "MDM Deployments",
+ "group": "Log Forwarding",
+ "icon": "tower-broadcast",
+ "root": "log-forwarding/index",
+ "pages": [
+ "log-forwarding/ci-telemetry-exports",
+ {
+ "group": "Beacon Managed",
+ "expanded": true,
+ "pages": [
+ "log-forwarding/asymptote"
+ ]
+ },
+ {
+ "group": "Security Information and Event Management (SIEM)",
+ "expanded": true,
+ "pages": [
+ "log-forwarding/falcon",
+ "log-forwarding/microsoft-sentinel",
+ "log-forwarding/rapid7",
+ "log-forwarding/splunk",
+ "log-forwarding/sumo",
+ "log-forwarding/wazuh"
+ ]
+ },
+ {
+ "group": "Log Aggregation",
+ "expanded": true,
+ "pages": [
+ "log-forwarding/cloudwatch",
+ "log-forwarding/customer-managed",
+ "log-forwarding/datadog",
+ "log-forwarding/elastic"
+ ]
+ },
+ {
+ "group": "Object Storage",
+ "expanded": true,
+ "pages": [
+ "guides/macos-object-storage-system"
+ ]
+ },
+ {
+ "group": "Local",
+ "expanded": true,
+ "pages": [
+ "log-forwarding/local-jsonl"
+ ]
+ }
+ ]
+ },
+ {
+ "group": "MDM Deployment",
"icon": "building-shield",
"root": "mdm/index",
"pages": [
{
"group": "Jamf",
+ "expanded": true,
"root": "mdm/jamf",
"pages": [
"mdm/jamf/claude",
@@ -536,6 +489,7 @@
},
{
"group": "Rippling",
+ "expanded": true,
"root": "mdm/rippling",
"pages": [
"guides/rippling-gcs-mdm"
@@ -543,6 +497,7 @@
},
{
"group": "Fleet",
+ "expanded": true,
"root": "mdm/fleet",
"pages": [
"guides/fleet-s3-mdm"
@@ -553,7 +508,7 @@
]
},
{
- "tab": "Asymptote Blog",
+ "tab": "Beacon Blog",
"icon": "newspaper",
"groups": [
{
@@ -649,8 +604,8 @@
"href": "https://trust.asymptotelabs.ai/"
},
{
- "label": "Book Demo",
- "href": "https://asymptotelabs.ai/contact"
+ "label": "Enterprise",
+ "href": "https://asymptotelabs.ai/"
}
],
"primary": {
@@ -850,11 +805,19 @@
},
{
"source": "/cli/quickstart-developers",
- "destination": "/get-started/quickstart-developers"
+ "destination": "/get-started/quickstart"
},
{
"source": "/cli/quickstart-security-it",
- "destination": "/get-started/quickstart-security-it"
+ "destination": "/get-started/quickstart"
+ },
+ {
+ "source": "/get-started/quickstart-developers",
+ "destination": "/get-started/quickstart"
+ },
+ {
+ "source": "/get-started/quickstart-security-it",
+ "destination": "/get-started/quickstart"
},
{
"source": "/cli/security-it-teams",
@@ -1250,7 +1213,11 @@
},
{
"source": "/managed-architecture",
- "destination": "/architecture/managed-architecture"
+ "destination": "/deployment/managed"
+ },
+ {
+ "source": "/architecture/managed-architecture",
+ "destination": "/deployment/managed"
},
{
"source": "/mdm-deployment",
@@ -1262,11 +1229,11 @@
},
{
"source": "/quickstart-developers",
- "destination": "/get-started/quickstart-developers"
+ "destination": "/get-started/quickstart"
},
{
"source": "/quickstart-security-it",
- "destination": "/get-started/quickstart-security-it"
+ "destination": "/get-started/quickstart"
},
{
"source": "/sdk-changelog",
@@ -1464,7 +1431,7 @@
"footer": {
"socials": {
"x": "https://x.com/asymptotelabs",
- "github": "https://github.com/Asymptote-Labs",
+ "github": "https://github.com/asymptote-labs",
"linkedin": "https://www.linkedin.com/company/asymptotelabs/"
},
"links": [
@@ -1528,7 +1495,7 @@
]
}
],
- "content": "© 2025 Asymptote Labs Inc. All rights reserved."
+ "content": "© 2025 Beacon Labs Inc. All rights reserved."
},
"appearance": {
"hidePoweredBy": true
diff --git a/docs/get-started/overview.mdx b/docs/get-started/overview.mdx
index 6670cc0f..c4d5421b 100644
--- a/docs/get-started/overview.mdx
+++ b/docs/get-started/overview.mdx
@@ -1,78 +1,53 @@
---
-title: "Asymptote Overview"
-description: "Why AI agent security needs a new control layer, and how Asymptote moves teams from local visibility to enterprise control"
+title: "Beacon Overview"
+description: "Beacon is the open-source self-improving memory layer for AI agents."
---
-Asymptote helps security and IT teams understand what AI agents are doing at runtime and add controls as adoption grows.
+Beacon captures activity across agent harnesses and turns it into a shared history you can search, debug, analyze, and learn from.
-You can start with open-source telemetry across the agent surfaces you already run, then move into centralized visibility, policy controls, and investigations when a small pilot turns into a broader rollout.
+Run Beacon locally with full control of your data, or use Beacon Managed for hosted storage, search, analytics, and unlimited retention.
-## Why teams need this
+## Why Beacon
-AI agents create a visibility gap that most security tools do not cover well. Traditional endpoint and application logs can usually tell you that something happened, but not enough about the agent session that caused it.
+Agent history is fragmented across tools.
-In practice, teams usually run into a few problems:
+Prompts, tool calls, commands, file edits, and model interactions are often trapped inside individual harnesses and session formats. Beacon normalizes that activity into one consistent record across agents.
-### Unknown agents, unknown risk
+That shared history makes it easier to:
-- Teams often do not have a reliable inventory of which agent tools are in use.
-- Ownership is unclear once agents spread across individual laptops and teams.
-- It becomes hard to answer basic questions such as which harness is running, what it can access, and where activity should be monitored.
+- debug failed workflows
+- understand how agents are being used
+- analyze runtime behavior
+- compare activity across harnesses
+- surface recurring workflows and corrections
+- turn past agent runs into reusable knowledge
-### Runtime moves faster than review
+## From traces to shared knowledge
-- Agents can read files, call tools, write code, and trigger actions very quickly.
-- Manual review works for a small pilot, but it does not scale once many users or teams depend on agents.
-- Security teams need a way to observe and govern activity while it is happening, not only after the fact.
+Every agent session contains useful context: debugging paths, repository conventions, repeated corrections, commands, and tool sequences.
-### Logs without runtime context
+Beacon captures that history so it can be reused across future runs and across different harnesses.
-- Standard logs may show a process, file write, or network connection.
-- They usually do not show the prompt, tool call, file context, or session flow behind that action.
-- That makes investigations harder and weakens policy decisions.
+Every run adds to the knowledge base.
-## How Asymptote fits together
+| Capability | Local | Beacon Managed |
+| --- | --- | --- |
+| Cross-harness agent telemetry | ✓ | ✓ |
+| Local, CI & cloud collection | ✓ | ✓ |
+| Unified agent session history | ✓ | ✓ |
+| Store data locally | ✓ | ✓ |
+| Forward to your own data stack | ✓ | ✓ |
+| Hosted ingest & storage | — | ✓ |
+| Search & analytics | — | ✓ |
+| Identity mapping | — | ✓ |
+| **Agent Session Retention** | **You manage** | **Unlimited** |
+| SSO & RBAC | — | ✓ |
-Asymptote is built as a progression rather than a single all-or-nothing product.
+## Beacon
-- **[Asymptote Open Source](/concepts/core-concepts#asymptote-open-source)** is the open-source foundation, built on [Agent Beacon](/concepts/core-concepts#agent-beacon). It captures supported agent activity across local endpoints, CI jobs, and cloud-agent surfaces, then normalizes prompts, tool calls, file edits, commands, and related session events into records teams can inspect or forward into their own security tools.
-- **[Asymptote Managed](/concepts/core-concepts#asymptote-managed)** builds on that foundation with centralized ingest, retention, detections, fleet-wide visibility, policy controls, identity mapping, approvals, and investigation workflows.
-- **[Private Deployment](/concepts/core-concepts#private-deployment)** is for teams that need dedicated infrastructure, tighter data boundaries, or residency controls.
+Beacon is built on the [`agent-beacon`](https://github.com/asymptote-labs/agent-beacon) repository.
-That gives teams a practical path:
-
-- start with open-source telemetry on the surfaces you already run
-- validate what agents are doing across local, CI, and cloud paths
-- centralize and govern that activity as usage expands
-- move into private deployment when compliance or infrastructure requirements demand it
-
-## Choosing a deployment path
-
-Use these rules of thumb:
-
-- Choose **Asymptote Open Source** if you want open-source telemetry across supported local, [CI](/concepts/core-concepts#ci-telemetry), and [cloud agent](/concepts/core-concepts#cloud-agent-telemetry) surfaces, normalized records you control, and [customer-managed forwarding](/concepts/core-concepts#customer-managed-forwarding) into your SIEM or observability stack.
-- Choose **Asymptote Managed** if you need centralized operations across endpoints, users, and teams.
-- Choose **Private Deployment** if managed capabilities are right, but you need stronger infrastructure ownership or data-isolation requirements.
-
-| Capability | Asymptote Open Source | Asymptote Managed | Private Deployment |
-| --- | --- | --- | --- |
-| Open-source runtime telemetry | ✓ | ✓ | ✓ |
-| Capture from supported local agent harnesses | ✓ | ✓ | ✓ |
-| Capture from supported CI jobs and cloud-agent surfaces | ✓ | ✓ | ✓ |
-| Customer-managed SIEM forwarding | ✓ | ✓ | ✓ |
-| MDM-friendly endpoint rollout | ✓ | ✓ | ✓ |
-| Managed ingest, retention, search, and detections | - | ✓ | ✓ |
-| Fleet-wide inventory and centralized visibility | - | ✓ | ✓ |
-| Policy controls, identity mapping, and approvals | - | ✓ | ✓ |
-| Investigation timelines and case workflows | - | ✓ | ✓ |
-| SSO, RBAC, and audit trails | - | ✓ | ✓ |
-| Dedicated deployment and data isolation options | - | - | ✓ |
-
-## Asymptote Open Source
-
-Asymptote Open Source is built on the `agent-beacon` repository.
-
-<a href="https://github.com/Asymptote-Labs/agent-beacon">
+<a href="https://github.com/asymptote-labs/agent-beacon">
<img
src="https://api.star-history.com/svg?repos=asymptote-labs/agent-beacon&type=Date"
alt="Agent Beacon GitHub star growth"
@@ -80,7 +55,7 @@ Asymptote Open Source is built on the `agent-beacon` repository.
/>
</a>
-If you are starting with Asymptote Open Source, these pages are the most useful next steps:
+If you are starting with Beacon, these pages are the most useful next steps:
<Columns cols={2}>
<Card title="Quickstart" icon="rocket" href="/get-started/quickstart">
@@ -96,7 +71,7 @@ If you are starting with Asymptote Open Source, these pages are the most useful
See supported agent harnesses, deployment modes, destinations, and boundaries.
</Card>
<Card title="Endpoint event schema" icon="code" href="/telemetry-schema/event-schema">
- Review Asymptote Open Source JSONL fields, normalization behavior, and example events.
+ Review Beacon JSONL fields, normalization behavior, and example events.
</Card>
<Card title="Security & IT Rollout Guide" icon="building-shield" href="/security">
Plan endpoint inventory, MDM rollout, retention policy, validation, and log forwarding.
@@ -108,11 +83,11 @@ Additional references: [Core Concepts](/concepts/core-concepts), [Command refere
## Related
<Columns cols={2}>
- <Card title="Asymptote Open Source" icon="download" href="/deployment/open-source">
+ <Card title="Beacon" icon="download" href="/deployment/open-source">
Install the open-source CLI and configure Agent Beacon telemetry.
</Card>
- <Card title="Asymptote Managed" icon="key" href="/deployment/managed">
- Review managed visibility, policy controls, investigations, and rollout support.
+ <Card title="Beacon Managed" icon="key" href="/deployment/managed">
+ Review managed visibility, investigations, and rollout support.
</Card>
<Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
Compare the open-source local path with managed and enterprise deployment options.
diff --git a/docs/get-started/quickstart-developers.mdx b/docs/get-started/quickstart-developers.mdx
deleted file mode 100644
index 52302181..00000000
--- a/docs/get-started/quickstart-developers.mdx
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: "For Individual Developers"
-description: "Install Beacon on your machine, see what your AI coding agents are doing, and, if your team uses Asymptote, forward that telemetry to your team's dashboard in one step"
----
-
-Ten minutes, no admin rights. Beacon installs a small local collector under your user account,
-records what Claude Code, Codex, Cursor and other supported agents do into a JSONL log on your
-machine, and shows it to you in a local dashboard. If your team uses Asymptote Managed, the same
-setup connects your machine to the team dashboard after a one-click approval in your browser.
-
-Nothing leaves your machine unless you choose to forward it; see [what leaves your machine](#what-leaves-your-machine).
-
-## 1. Install Beacon
-
-<CodeGroup>
-```bash title="macOS"
-brew install asymptote-labs/tap/beacon
-```
-
-```bash title="Linux"
-LATEST_URL="$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/asymptote-labs/agent-beacon/releases/latest)"
-VERSION="${LATEST_URL##*/v}"
-
-case "$(uname -m)" in
- x86_64) ARCH=amd64 ;;
- aarch64|arm64) ARCH=arm64 ;;
- *) echo "Beacon publishes Linux archives for amd64 and arm64, not $(uname -m)" >&2; exit 1 ;;
-esac
-
-ARCHIVE="beacon_${VERSION}_linux_${ARCH}.tar.gz"
-BASE="https://github.com/asymptote-labs/agent-beacon/releases/download/v${VERSION}"
-curl -fsSLO "${BASE}/${ARCHIVE}"
-curl -fsSLO "${BASE}/checksums.txt"
-
-grep " ${ARCHIVE}$" checksums.txt | sha256sum --check -
-
-tar -xzf "${ARCHIVE}"
-mkdir -p ~/.local/bin && mv beacon beacon-hooks beacon-otelcol ~/.local/bin/
-```
-</CodeGroup>
-
-Homebrew also installs [Vector](https://vector.dev), which Beacon uses to forward telemetry when you
-ask it to. On Linux, install Vector 0.50 or newer from vector.dev if you plan to forward.
-
-<Note>
- The Linux tab uses the tarball on purpose. This page is a per-user setup; the `.deb`/`.rpm`
- packages install a **system-mode** endpoint managed by systemd that writes to
- `/var/log/beacon-agent/runtime.jsonl`, so the commands below would report on the wrong log. For
- the system-mode package, follow [Linux](/platforms/linux) instead.
-</Note>
-
-## 2. Set up the endpoint
-
-```bash
-beacon endpoint install --harness claude,codex,cursor
-```
-
-This starts the local collector, points Claude Code and Codex at it, and installs the Cursor hooks.
-Drop `cursor` from the list if you do not use it; add other hook runtimes the same way (see
-[Runtime hooks](/cli/hooks) for the names).
-
-The first install asks three questions in the terminal:
-
-1. **How are you using Beacon?** Work, personal, or evaluating.
-2. **Your email.** Used once, for attribution, so we know which agent runtimes to support next.
-3. **Where should this machine's agent telemetry go?** Pick with the arrow keys:
-
-| Choice | What happens |
-|--------|--------------|
-| **Keep it on this machine** (default) | Nothing is sent anywhere. You get the local log and the local dashboard. Change your mind any time with `beacon endpoint connect` or a forwarding pack. |
-| **Forward to your own infrastructure** | A SIEM, observability platform, or an S3/GCS bucket you own. Beacon prints the [log forwarding](/log-forwarding) guide and the pack commands; the install stays local until you set one up. |
-| **Forward to Asymptote Managed** | Your browser opens the Asymptote dashboard; a member of your organization approves this device; a Vector forwarder starts shipping the log to your team's dashboard. Only events recorded after the approval are sent. |
-
-The answers stay on your machine and are asked once per machine. The one exception: if you chose
-Asymptote Managed and the connection did not finish, the destination question comes back next time.
-
-## 3. If you chose Asymptote Managed
-
-You need to be a member of your organization in Asymptote; ask an admin for an invite if signing in
-shows no organization. After the install finishes:
-
-1. The browser opens `asymptotelabs.ai/cli/enroll`. Sign in if asked.
-2. The page shows your machine's name, OS and Beacon version. Click **Approve this device**.
-3. Back in the terminal you see `Connected to Asymptote as device … for <your org>` and
- `Forwarder: … running=true`. The per-device key is stored in a file only you can read; it is
- never printed.
-
-Skipped the question or your browser did not open? Run it any time:
-
-```bash
-beacon endpoint connect
-```
-
-## 4. See your first events
-
-Start a new Claude Code or Codex session, or restart Cursor so it loads the hooks, and do a few
-turns. Then:
-
-```bash
-beacon endpoint status # collector running, each harness telemetry=enabled
-beacon endpoint dashboard --open # local dashboard over your own log
-```
-
-If you connected to Asymptote Managed, your machine appears on the team dashboard's **Endpoints**
-page within a minute or two, and the session shows up under **Telemetry**. The `status` output
-also has an `Asymptote managed ingest` line with the connection, the forwarder state, and whether
-the device key is still accepted.
-
-## Everyday commands
-
-| Task | Command |
-|------|---------|
-| Check health and the managed connection | `beacon endpoint status` |
-| Local dashboard | `beacon endpoint dashboard --open` |
-| Connect to Asymptote Managed later, or re-connect after a revoke | `beacon endpoint connect` |
-| Stop forwarding and remove the local key | `beacon endpoint disconnect`, then revoke the device on the dashboard |
-| See what you answered at setup | `beacon endpoint onboarding` |
-| Hook status for a runtime | `beacon endpoint hooks status --harness cursor` |
-| Upgrade | `brew upgrade beacon && beacon endpoint install --harness claude,codex,cursor` (the forwarder keeps running) |
-| Remove everything, keep your logs | `beacon endpoint uninstall --keep-logs` |
-
-## What leaves your machine
-
-- **By default, nothing.** Hooks and the collector never touch the network.
-- **Once, at setup:** your email, your work/personal answer, and install context (OS, architecture,
- Beacon version, install method, detected runtime names, a random install id). Never prompt text,
- commands, file contents, or events. `BEACON_ONBOARDING=0` skips it entirely.
-- **Only if you connected to Asymptote Managed:** the runtime and inventory logs, exactly as written
- locally, sent by Vector with your device key. Revoking the device on the dashboard stops it within
- about a minute; `beacon endpoint disconnect` stops it locally.
-
-## If something looks off
-
-- **No events after a session:** Claude Code and Codex read their telemetry settings at startup, and
- Cursor loads hooks at startup, so start a fresh session or restart the app.
-- **`status` says the credential is revoked:** someone revoked this device, or you left the
- organization. `beacon endpoint connect` re-enrolls.
-- **The approval page says "not provisioned" or "not enabled":** you are not yet a member of an
- organization that has managed ingest, or none is enabled. Ask your admin.
-- **`Collector ports are not listening` during install:** a system-mode Beacon is already installed on
- this machine (`/opt/beacon`); the two cannot run together. Use that install instead, or remove it
- first. See [troubleshooting](/support/troubleshooting).
-
-## Related
-
-<Columns cols={2}>
- <Card title="beacon endpoint connect" icon="link" href="/cli/endpoint-connect">
- Everything about connecting, disconnecting, and what the forwarder stores.
- </Card>
- <Card title="Asymptote Managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
- The wire contract, what is sent, and how revocation works.
- </Card>
- <Card title="Runtime hooks" icon="plug" href="/cli/hooks">
- Install, check, and remove hook-based telemetry for each runtime.
- </Card>
- <Card title="Log forwarding" icon="share-nodes" href="/log-forwarding">
- Send the local log to your own SIEM, observability platform, or bucket.
- </Card>
-</Columns>
diff --git a/docs/get-started/quickstart-security-it.mdx b/docs/get-started/quickstart-security-it.mdx
deleted file mode 100644
index a871eccc..00000000
--- a/docs/get-started/quickstart-security-it.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: "For Security & IT Teams"
-description: "Choose a rollout path for open-source telemetry, managed visibility, or private deployment"
----
-
-Use this path when you are evaluating Asymptote for a security operations, IT, or endpoint-management rollout.
-
-## 1. Choose your path
-
-Start with the deployment model that matches your review and operating needs.
-
-| Hosting Option | Best for | Where to go |
-| -------------- | -------- | ----------- |
-| Asymptote Open Source | Small pilots across supported local, CI, and cloud-agent surfaces, with local JSONL and customer-managed forwarding where applicable. | Continue below. |
-| Asymptote Managed | Centralized visibility, policy controls, investigations, SSO/RBAC, and rollout support. | See [Asymptote Managed](/deployment/managed). |
-| Asymptote Private Deployment | Managed capabilities with stricter data isolation, residency, or infrastructure ownership requirements. | [Contact us](https://asymptotelabs.ai/contact). |
-
-For the full comparison, see [Hosting Options](/deployment/hosting-options).
-
-## 2. Run a small open-source pilot
-
-If you are starting local-first, pilot Beacon on a small group before broad deployment. The fleet
-story differs by platform, so read the one you are rolling out to first:
-[macOS](/platforms/macos) ships MDM assets for Jamf, Fleet, and Rippling;
-[Windows](/platforms/windows) ships an MSI for Intune or SCCM;
-[Linux](/platforms/linux) ships `.deb` and `.rpm` packages that install and start the endpoint
-themselves.
-
-Decide three things up front:
-
-- which [agent harnesses](/runtimes) are in scope
-- whether events should stay local at first or forward into a security workflow
-- which MDM group will receive the first system-mode package rollout
-
-Beacon is local-only by default. It writes normalized endpoint events to JSONL and does not require a Beacon-hosted account, remote policy fetch, or external network dependency during normal collection.
-
-## 3. Deploy and validate
-
-```bash
-sudo beacon endpoint install --system
-beacon endpoint status
-```
-
-After deployment, confirm collector health, runtime log freshness, harness scope, and forwarding readiness.
-
-```bash
-beacon endpoint status --json
-beacon endpoint discover --json
-beacon scan --min-severity high
-```
-
-For package rollout details, see [MDM Deployment](/mdm), [Jamf](/mdm/jamf), and [Fleet](/mdm/fleet). For the deeper operational checklist, see the [Security & IT Rollout Guide](/security).
-
-## 4. Expand or centralize
-
-If the pilot is healthy, expand through MDM and add forwarding only where it matches your security workflow. Beacon preserves local JSONL even when you forward events downstream.
-
-Use [Log Forwarding](/log-forwarding) for Wazuh, Splunk HEC, Falcon LogScale HEC, Elastic, Datadog, Sumo Logic, Rapid7 InsightIDR, Microsoft Sentinel, object storage, local JSONL, and customer-managed pipelines.
-
-Use [`beacon scan`](/cli/scan) and [`beacon rules`](/cli/rules) when you want local threat-detection checks over endpoint telemetry before or alongside downstream forwarding.
-
-Move to [Asymptote Managed](/deployment/managed) when you need centralized retention, search, detections, fleet-wide visibility, governance, investigations, SSO/RBAC, audit trails, or rollout support. Once your organization is provisioned, endpoints join it one at a time: a developer runs [`beacon endpoint connect`](/cli/endpoint-connect) (or picks Asymptote Managed during the first install) and approves the device in the browser; on package or MDM installs an admin runs `sudo beacon endpoint connect --system` on the machine. Headless enrollment for fleets is a planned follow-up.
-
-[Contact us](https://asymptotelabs.ai/contact) if you want Managed or Private Deployment guidance.
-
-## Related
-
-<Columns cols={2}>
- <Card title="MDM Deployment" icon="laptop-mobile" href="/mdm">
- Plan managed macOS rollout with the packaged system agent.
- </Card>
- <Card title="Log Forwarding" icon="tower-broadcast" href="/log-forwarding">
- Forward Beacon events into security and observability platforms.
- </Card>
- <Card title="Security Review" icon="shield-halved" href="/security/review">
- Review local collection, data inventory, content handling, endpoint behavior, and disclosure policy.
- </Card>
- <Card title="Asymptote Managed" icon="key" href="/deployment/managed">
- Review managed visibility, policy controls, investigations, and rollout support.
- </Card>
-</Columns>
diff --git a/docs/get-started/quickstart.mdx b/docs/get-started/quickstart.mdx
index 59a363fe..626e6f30 100644
--- a/docs/get-started/quickstart.mdx
+++ b/docs/get-started/quickstart.mdx
@@ -1,86 +1,108 @@
---
title: "Quickstart"
-description: "Choose the right Asymptote path for a local, managed, or private rollout"
+description: "Install Beacon, choose where your data lives, and capture your first agent session"
---
-Start here if you are deciding how to introduce Asymptote across a team. Asymptote can begin as open-source Agent Beacon telemetry across supported local, CI, and cloud surfaces, move into managed visibility and governance, or run in a private deployment for stricter infrastructure requirements.
+## 1. Install Beacon
-## Choose a deployment path
+<Tabs>
+ <Tab title="macOS">
+ ```bash
+ brew trust asymptote-labs/tap
+ brew install asymptote-labs/tap/beacon
+ ```
+ </Tab>
+ <Tab title="Windows">
+ Download `BeaconEndpointAgent-<version>-x64.msi` from the [latest release](https://github.com/asymptote-labs/agent-beacon/releases/latest), then run PowerShell as an administrator:
-| Hosting Option | Use it when | Next step |
-| -------------- | ----------- | --------- |
-| Asymptote Open Source | You want open-source telemetry across supported agent surfaces, local JSONL where applicable, and customer-managed forwarding into your SIEM or observability stack. | Start with the [Security & IT quickstart](/get-started/quickstart-security-it) or [developer quickstart](/get-started/quickstart-developers). |
-| Asymptote Managed | You need centralized ingest, fleet-wide visibility, policy controls, investigations, SSO/RBAC, audit trails, and rollout support. | Review [Asymptote Managed](/deployment/managed) or [contact us](https://asymptotelabs.ai/contact). |
-| Asymptote Private Deployment | You want managed capabilities with dedicated infrastructure, stricter data boundaries, or residency requirements. | [Contact us](https://asymptotelabs.ai/contact) to discuss deployment requirements. |
+ ```powershell
+ msiexec /i BeaconEndpointAgent-<version>-x64.msi
+ ```
-See [Hosting Options](/deployment/hosting-options) for the full comparison.
+ See the [Windows install guide](/platforms/windows) for more options.
+ </Tab>
+ <Tab title="Linux">
+ Install Beacon using the package for your environment:
-## Open source rollout strategy
+ <CodeGroup>
+ ```bash title="Debian, Ubuntu"
+ sudo apt install ./beacon_<version>_linux_amd64.deb
+ ```
-For most Security and IT teams, the safest open-source path is staged. Local endpoint collection is usually the first evaluation path, then teams can add CI and cloud-agent surfaces where those agents run:
+ ```bash title="Fedora, RHEL, Rocky, Alma"
+ sudo dnf install ./beacon_<version>_linux_amd64.rpm
+ ```
+ </CodeGroup>
-1. **Evaluate locally** with a small pilot group using supported [agent harnesses](/runtimes).
-2. **Validate health and visibility** with endpoint status, runtime log freshness, and expected event coverage.
-3. **Add CI or cloud surfaces** with the relevant Beacon setup paths when agent activity also runs in build jobs or hosted sandboxes.
-4. **Decide where events should live**: local JSONL only, Wazuh localfile, a supported SIEM/log destination, object storage, or a customer-managed pipeline.
-5. **Expand through MDM** once install coverage, collector health, and forwarding checks are stable.
+ Replace `amd64` with `arm64` on ARM systems. See the [Linux install guide](/platforms/linux) for more options.
+ </Tab>
+</Tabs>
-The open-source path is local-only by default. The endpoint agent does not require a Beacon-hosted account, remote policy fetch, or external network dependency during normal collection.
+Then configure the agents you use:
-## Managed or private path
+```bash
+beacon endpoint install --harness claude,codex,cursor
+```
-Move to Managed when a small pilot becomes an operating program: multiple teams, centralized search, governance, investigations, access control, and rollout support.
+## 2. Choose where your data lives
-Connecting an endpoint is one command once your organization is provisioned: `beacon endpoint connect` opens the dashboard, a member of your organization approves the device, and the machine's telemetry starts appearing on the dashboard. The first interactive `beacon endpoint install` offers the same step. See [`beacon endpoint connect`](/cli/endpoint-connect).
+Beacon supports two modes.
-Private Deployment is the path for regulated teams that need managed capabilities with dedicated infrastructure, stronger isolation, custom retention, or residency requirements.
+### Local
-[Contact us](https://asymptotelabs.ai/contact) to discuss Managed or Private Deployment.
+Keep your agent history on your machine.
-## Pick your quickstart
+Beacon writes telemetry locally and gives you a local dashboard. Nothing is forwarded unless you explicitly configure it.
-<Columns cols={2}>
- <Card title="For Security & IT Teams" icon="building-shield" href="/get-started/quickstart-security-it">
- Plan an open-source pilot, validate endpoint telemetry, and decide when to centralize or move to Managed.
- </Card>
- <Card title="For Individual Developers" icon="user" href="/get-started/quickstart-developers">
- Install Beacon locally, confirm collection health, and inspect agent activity on your machine.
- </Card>
-</Columns>
+### Beacon Managed
-### Then pick your platform
+Send your Beacon telemetry to the hosted service for:
-Both paths install the endpoint agent locally, and that part differs by operating system. The
-package, the service manager, and how a fleet is deployed are not the same on each:
+- unlimited retention
+- search across past sessions
+- cross-harness history
+- analytics
+- access from anywhere
-<Columns cols={2}>
- <Card title="macOS" icon="apple" href="/platforms/macos">
- Homebrew for one machine, or the signed `.pkg` with Jamf, Fleet, or Rippling for a fleet. launchd.
- </Card>
- <Card title="Linux" icon="linux" href="/platforms/linux">
- A `.deb` or `.rpm` that installs and starts the endpoint for you. systemd.
- </Card>
- <Card title="Windows" icon="windows" href="/platforms/windows">
- An MSI that installs and starts the endpoint for you. Windows Service Control Manager.
- </Card>
-</Columns>
+[Sign up for Beacon Managed](https://beacon.sh/sign-up), then connect your endpoint:
-Capturing from CI jobs, cloud agents, or your own applications through the SDK needs none of this.
-See [agent harness integrations](/runtimes).
+```bash
+beacon endpoint connect --dashboard-url https://beacon.sh
+```
-## Deeper guides
+Your browser will open so you can sign in and approve the device.
-<Columns cols={2}>
- <Card title="Asymptote Open Source" icon="download" href="/deployment/open-source">
- Install Beacon and configure the open-source telemetry path.
- </Card>
- <Card title="Security & IT Rollout Guide" icon="building-shield" href="/security">
- Expand from pilot to managed endpoint rollout, validation, and forwarding.
- </Card>
- <Card title="Asymptote Managed" icon="key" href="/deployment/managed">
- Review managed visibility, policy controls, investigations, and rollout support.
- </Card>
- <Card title="Agent harness integrations" icon="list-check" href="/runtimes">
- See supported runtimes, deployment modes, destinations, and boundaries.
- </Card>
-</Columns>
+## 3. Run an agent
+
+Start a new Claude Code, Codex, Cursor, or other supported agent session and use it normally.
+
+Beacon captures the session automatically.
+
+## 4. View your sessions
+
+For the local dashboard:
+
+```bash
+beacon endpoint dashboard --open
+```
+
+If you're using Beacon Managed, your sessions will also appear in the hosted dashboard.
+
+## Check your setup
+
+```bash
+beacon endpoint status
+```
+
+This shows which harnesses are connected, whether the collector is running, and whether Beacon Managed is enabled.
+
+## Useful commands
+
+| Task | Command |
+| --- | --- |
+| Check status | `beacon endpoint status` |
+| Open local dashboard | `beacon endpoint dashboard --open` |
+| Connect to Beacon Managed | `beacon endpoint connect --dashboard-url https://beacon.sh` |
+| Disconnect from Managed | `beacon endpoint disconnect` |
+| Upgrade | `brew upgrade beacon` |
+| Uninstall | `beacon endpoint uninstall --keep-logs` |
diff --git a/docs/guides/fleet-s3-mdm.mdx b/docs/guides/fleet-s3-mdm.mdx
index 354f088c..06465224 100644
--- a/docs/guides/fleet-s3-mdm.mdx
+++ b/docs/guides/fleet-s3-mdm.mdx
@@ -95,7 +95,7 @@ Download it from the repo:
```bash
curl -fsSL -o configure-beacon-macos-s3.sh \
- https://raw.githubusercontent.com/Asymptote-Labs/agent-beacon/main/examples/fleet/configure-beacon-macos-s3.sh
+ https://raw.githubusercontent.com/asymptote-labs/agent-beacon/main/examples/fleet/configure-beacon-macos-s3.sh
chmod +x configure-beacon-macos-s3.sh
```
diff --git a/docs/guides/inventory.mdx b/docs/guides/inventory.mdx
index dda04d1f..d6b0d54c 100644
--- a/docs/guides/inventory.mdx
+++ b/docs/guides/inventory.mdx
@@ -105,7 +105,7 @@ beacon endpoint inventory --json
- Which supported agent runtimes are installed or configured on this machine?
- Which local agent skills are present under supported skill roots?
- Which MCP servers are referenced by local agent configuration?
-- Which runtime config files can Beacon inspect locally?
+- Which runtime config files ca Beacon inspect locally?
- Which hooks, OTLP settings, or launch environment entries are present?
- Which detected runtimes have recently produced Beacon events?
diff --git a/docs/guides/macos-object-storage-system.mdx b/docs/guides/macos-object-storage-system.mdx
index 174aab12..1e101044 100644
--- a/docs/guides/macos-object-storage-system.mdx
+++ b/docs/guides/macos-object-storage-system.mdx
@@ -34,12 +34,12 @@ the producing harness.
## 1. Install Beacon
Download and install the latest signed Apple Silicon endpoint package from
-[GitHub Releases](https://github.com/Asymptote-Labs/agent-beacon/releases):
+[GitHub Releases](https://github.com/asymptote-labs/agent-beacon/releases):
```bash
tmpdir="$(mktemp -d)"
gh release download \
- --repo Asymptote-Labs/agent-beacon \
+ --repo asymptote-labs/agent-beacon \
--pattern 'BeaconEndpointAgent-*-arm64.pkg' \
--dir "$tmpdir"
diff --git a/docs/images/beacon-favicon.svg b/docs/images/beacon-favicon.svg
new file mode 100644
index 00000000..2def79a0
--- /dev/null
+++ b/docs/images/beacon-favicon.svg
@@ -0,0 +1,5 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" role="img" aria-label="Beacon">
+ <path fill="#FF6A00" d="M256 52C210 91 122 157 82 212c-26 36-39 74-34 111 8 62 49 103 111 125 31 11 57 30 79 56V288h-29v-85a48 48 0 1 1 94 0v85h-29v216c22-26 48-45 79-56 62-22 103-63 111-125 5-37-8-75-34-111-40-55-128-121-174-160Z"/>
+ <circle cx="256" cy="191" r="39" fill="#FFFFFF"/>
+ <rect x="238" y="225" width="36" height="239" fill="#FFFFFF"/>
+</svg>
diff --git a/docs/index.mdx b/docs/index.mdx
index 2aa93d79..93750b94 100644
--- a/docs/index.mdx
+++ b/docs/index.mdx
@@ -1,23 +1,72 @@
---
-title: "Welcome to Asymptote"
-description: "Asymptote is the AI Detection & Response layer for every agent harness. Security teams use Asymptote to get complete agent runtime visibility and govern agent activity at scale."
+title: "Welcome to Beacon"
+description: "Beacon is the open-source self-improving memory layer for AI agents."
---
-<img src="/images/logo.png" alt="Asymptote logo" width="720" height="360" />
+<picture>
+ <source media="(prefers-color-scheme: dark)" srcSet="/logo/beacon-lockup-dark.svg" />
+ <img src="/logo/beacon-lockup-light.svg" alt="Beacon logo" width="720" height="252" />
+</picture>
-<Info>
- Looking for a demo? Visit [asymptotelabs.ai/contact](https://asymptotelabs.ai/contact).
-</Info>
+Beacon is the open-source self-improving memory layer for AI agents. It was designed and built by the founders of [Asymptote Labs](https://asymptotelabs.ai/).
+
+It captures agent activity across Claude Code, Cursor, Codex, OpenCode, and 20+ other harnesses, creating a shared history of how agents work across local, CI, and cloud environments.
+
+Use Beacon to understand agent behavior, debug workflows, and turn what your agents learn into reusable knowledge that compounds across harnesses.
+
+## Install Beacon
+
+<Tabs>
+ <Tab title="macOS">
+ Install Beacon with Homebrew:
+
+ ```bash
+ brew trust asymptote-labs/tap
+ brew tap asymptote-labs/tap
+ brew install beacon
+ beacon version
+ ```
+
+ See the [macOS install guide](/platforms/macos) to configure endpoint telemetry or deploy the signed package to a fleet.
+ </Tab>
+ <Tab title="Windows">
+ Download `BeaconEndpointAgent-<version>-x64.msi` from the [latest release](https://github.com/asymptote-labs/agent-beacon/releases/latest), then run PowerShell as an administrator:
+
+ ```powershell
+ msiexec /i BeaconEndpointAgent-<version>-x64.msi
+ & "$env:ProgramFiles\Beacon\bin\beacon.exe" version
+ ```
+
+ See the [Windows install guide](/platforms/windows) for silent installation, checksum verification, and service management.
+ </Tab>
+ <Tab title="Linux">
+ Download the `.deb` or `.rpm` for your architecture from the [latest release](https://github.com/asymptote-labs/agent-beacon/releases/latest):
+
+ <CodeGroup>
+ ```bash title="Debian, Ubuntu"
+ sudo apt install ./beacon_<version>_linux_amd64.deb
+ beacon version
+ ```
+
+ ```bash title="Fedora, RHEL, Rocky, Alma"
+ sudo dnf install ./beacon_<version>_linux_amd64.rpm
+ beacon version
+ ```
+ </CodeGroup>
+
+ Replace `amd64` with `arm64` on ARM systems. See the [Linux install guide](/platforms/linux) for rootless and tarball installation.
+ </Tab>
+</Tabs>
## Getting started
-Choose the open-source Agent Beacon path to start collecting agent telemetry across local, CI, and cloud surfaces, or request access to managed Asymptote for hosted visibility and governance.
+Start collecting agent traces in minutes, then use Beacon to explore sessions, understand workflows, and build shared knowledge from every agent run.
<CardGroup cols={2}>
- <Card title="Asymptote Overview" icon="rocket" href="/get-started/overview">
- Understand the problem Asymptote solves, how Beacon fits in, and when to use managed or private deployments.
+ <Card title="Beacon Overview" icon="rocket" href="/get-started/overview">
+ Understand the problem Beacon solves and when to use open-source, managed, or private deployments.
</Card>
- <Card title="Managed Asymptote" icon="key" href="/deployment/managed">
+ <Card title="Managed Beacon" icon="key" href="/deployment/managed">
Review managed platform options for hosted agent runtime visibility, governance, and enterprise rollout support.
</Card>
</CardGroup>
diff --git a/docs/log-forwarding/asymptote.mdx b/docs/log-forwarding/asymptote.mdx
index 4056d98a..e9ac2b84 100644
--- a/docs/log-forwarding/asymptote.mdx
+++ b/docs/log-forwarding/asymptote.mdx
@@ -1,13 +1,13 @@
---
-title: "Asymptote Managed"
-description: "Forward Beacon endpoint events to Asymptote's managed ingest service and see them on the Asymptote dashboard."
+title: "Beacon Managed"
+description: "Forward Beacon endpoint events to Beacon's managed ingest service and see them on the Beacon dashboard."
---
## Forwarding overview
-Asymptote Managed is the forwarding path that lands Beacon endpoint events on the Asymptote dashboard without any customer-run infrastructure. Beacon stays the local JSONL producer. A Vector forwarder on the endpoint tails the [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log) and the inventory log and POSTs gzip-compressed NDJSON batches over HTTPS to Asymptote's ingest service, authenticated with a key issued to that one device.
+Beacon Managed is the forwarding path that lands Beacon endpoint events on the Beacon dashboard without any customer-run infrastructure. Beacon stays the local JSONL producer. A Vector forwarder on the endpoint tails the [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log) and the inventory log and POSTs gzip-compressed NDJSON batches over HTTPS to Beacon's ingest service, authenticated with a key issued to that one device.
-This is the only Beacon destination that sends telemetry to an Asymptote-run endpoint, and it is opt-in. Beacon's default remains local-only; nothing is forwarded until a member of your Asymptote organization approves the device in the browser and the forwarder is started with the resulting key. Revoking the device from the dashboard's Beacon Endpoints page stops ingestion within about a minute.
+This is the only Beacon destination that sends telemetry to a Beacon-run endpoint, and it is opt-in. Beacon's default remains local-only; nothing is forwarded until a member of your Beacon organization approves the device in the browser and the forwarder is started with the resulting key. Revoking the device from the dashboard's Beacon Endpoints page stops ingestion within about a minute.
Generate the pack with [`beacon endpoint asymptote`](/cli/asymptote). `beacon endpoint connect` performs enrollment and runs the forwarder as a service; the pack is for running or inspecting the same forwarder by hand.
@@ -37,7 +37,7 @@ Vector keeps reading into a disk buffer (512 MiB for runtime, 256 MiB for invent
## Install the pack
-```bash title="Generate the Asymptote pack for a system-mode deployment"
+```bash title="Generate the Beacon pack for a system-mode deployment"
sudo /opt/beacon/bin/beacon endpoint asymptote install-pack \
--system \
--output ./beacon-asymptote-pack
@@ -49,7 +49,7 @@ The pack includes `README.md`, `vector.toml`, `asymptote-ingest-smoke-test.sh`,
1. Run `sh ./beacon-asymptote-pack/asymptote-ingest-smoke-test.sh` with `BEACON_ASYMPTOTE_INGEST_URL` and `BEACON_ASYMPTOTE_SECRETS_FILE` set. It checks the key (`200` valid, `401` revoked) and posts the log tail once.
2. With Vector running, write a validation event: `beacon endpoint asymptote validate`.
-3. Within a minute or two, search the dashboard telemetry page for `Beacon endpoint Asymptote validation event`.
+3. Within a minute or two, search the dashboard telemetry page for `Beacon endpoint Beacon validation event`.
## Revocation
diff --git a/docs/log-forwarding/ci-telemetry-exports.mdx b/docs/log-forwarding/ci-telemetry-exports.mdx
index df72748a..419bb254 100644
--- a/docs/log-forwarding/ci-telemetry-exports.mdx
+++ b/docs/log-forwarding/ci-telemetry-exports.mdx
@@ -98,8 +98,8 @@ jobs:
See the sample workflows:
-- [Splunk forward telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/splunk-forward-telemetry.yml)
-- [Falcon forward telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/falcon-forward-telemetry.yml)
+- [Splunk forward telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/splunk-forward-telemetry.yml)
+- [Falcon forward telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/falcon-forward-telemetry.yml)
For Falcon LogScale HEC, set `BEACON_CI_FALCON_HEC_TOKEN` and use `forward: falcon`.
@@ -125,7 +125,7 @@ Configure cloud credentials at the job level, then pass the upload destination t
See the sample workflow:
-- [S3 upload telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/s3-upload-telemetry.yml)
+- [S3 upload telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/s3-upload-telemetry.yml)
For GCS, authenticate with your normal Google Cloud CI mechanism and set `BEACON_CI_GCS_BUCKET` plus optional `BEACON_CI_GCS_PREFIX`:
@@ -147,7 +147,7 @@ For GCS, authenticate with your normal Google Cloud CI mechanism and set `BEACON
See the sample workflow:
-- [GCS upload telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/gcs-upload-telemetry.yml)
+- [GCS upload telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/gcs-upload-telemetry.yml)
`--upload` is repeatable, so a job can upload to both destinations when required. Pass `upload: s3,gcs` (or the equivalent `--upload s3 --upload gcs` CLI flags) after configuring credentials for each provider:
@@ -166,7 +166,7 @@ See the sample workflow:
See the sample workflow:
-- [S3 and GCS upload telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/s3-gcs-upload-telemetry.yml)
+- [S3 and GCS upload telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/s3-gcs-upload-telemetry.yml)
## Object layout
@@ -231,7 +231,7 @@ When runners should not download a Beacon release during the action step, provis
See the sample workflow:
-- [binary-path telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/binary-path-telemetry.yml)
+- [binary-path telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/binary-path-telemetry.yml)
## Related
diff --git a/docs/log-forwarding/datadog.mdx b/docs/log-forwarding/datadog.mdx
index c2420c17..fc6d838d 100644
--- a/docs/log-forwarding/datadog.mdx
+++ b/docs/log-forwarding/datadog.mdx
@@ -29,6 +29,7 @@ For production or MDM deployment, prefer **system mode**. It avoids per-user hom
For local testing:
```bash title="Set up local testing"
+brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon
diff --git a/docs/log-forwarding/elastic.mdx b/docs/log-forwarding/elastic.mdx
index ff3c2fbc..2b762a9c 100644
--- a/docs/log-forwarding/elastic.mdx
+++ b/docs/log-forwarding/elastic.mdx
@@ -39,6 +39,7 @@ Use system mode for MDM deployments so every managed endpoint writes to `/var/lo
For a local macOS trial, install Beacon, configure endpoint telemetry, and start the bundled loopback-only stack:
```bash title="Start the local Elastic validation stack"
+brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon
diff --git a/docs/log-forwarding/falcon.mdx b/docs/log-forwarding/falcon.mdx
index de3102c8..28251fb7 100644
--- a/docs/log-forwarding/falcon.mdx
+++ b/docs/log-forwarding/falcon.mdx
@@ -201,9 +201,9 @@ The package installs:
These packaged helpers come from the repository paths:
-- [`packaging/macos/jamf/claude/falcon/install-forwarder.sh`](https://github.com/Asymptote-Labs/agent-beacon/blob/main/packaging/macos/jamf/claude/falcon/install-forwarder.sh)
-- [`packaging/macos/jamf/claude/falcon/repair-hooks-and-forwarder.sh`](https://github.com/Asymptote-Labs/agent-beacon/blob/main/packaging/macos/jamf/claude/falcon/repair-hooks-and-forwarder.sh)
-- [`packaging/macos/jamf/claude/falcon/run-forwarder.sh`](https://github.com/Asymptote-Labs/agent-beacon/blob/main/packaging/macos/jamf/claude/falcon/run-forwarder.sh)
+- [`packaging/macos/jamf/claude/falcon/install-forwarder.sh`](https://github.com/asymptote-labs/agent-beacon/blob/main/packaging/macos/jamf/claude/falcon/install-forwarder.sh)
+- [`packaging/macos/jamf/claude/falcon/repair-hooks-and-forwarder.sh`](https://github.com/asymptote-labs/agent-beacon/blob/main/packaging/macos/jamf/claude/falcon/repair-hooks-and-forwarder.sh)
+- [`packaging/macos/jamf/claude/falcon/run-forwarder.sh`](https://github.com/asymptote-labs/agent-beacon/blob/main/packaging/macos/jamf/claude/falcon/run-forwarder.sh)
### Manual setup without Jamf
diff --git a/docs/log-forwarding/index.mdx b/docs/log-forwarding/index.mdx
index f7969bc0..c3e16c00 100644
--- a/docs/log-forwarding/index.mdx
+++ b/docs/log-forwarding/index.mdx
@@ -7,7 +7,7 @@ description: "Forward Beacon endpoint events from local JSONL into SIEMs, log ag
Beacon writes normalized [endpoint events](/concepts/core-concepts#endpoint-event) as JSONL. The active [runtime log](/concepts/core-concepts#runtime-jsonl-log) is the handoff point for local review, [customer-managed log pipelines](/concepts/core-concepts#customer-managed-forwarding), log aggregators, object storage exporters, and most SIEM content packs. Beacon can also enable optional collector exporters for [Splunk HTTP Event Collector (HEC)](/concepts/core-concepts#splunk-hec) and [CrowdStrike Falcon LogScale HEC](/concepts/core-concepts#falcon-logscale-hec) during endpoint install or repair.
-Use the subpages below by destination category. Asymptote Managed is the one path that sends events to an Asymptote-run service; it is opt-in per device and revocable from the Asymptote dashboard. SIEM pages are for destinations that become investigation or detection systems. Log aggregation pages are for customer-owned pipelines and observability stores that tail local JSONL. Object storage pages are for archival or data lake export. Local pages cover the default runtime log and dashboard source.
+Use the subpages below by destination category. Beacon Managed is the one path that sends events to a Beacon-run service; it is opt-in per device and revocable from the Beacon dashboard. SIEM pages are for destinations that become investigation or detection systems. Log aggregation pages are for customer-owned pipelines and observability stores that tail local JSONL. Object storage pages are for archival or data lake export. Local pages cover the default runtime log and dashboard source.
For [ephemeral CI jobs](/concepts/core-concepts#ci-telemetry), see [CI Telemetry Exports](/log-forwarding/ci-telemetry-exports) for workflow artifacts, S3/GCS upload, and downstream handoff patterns over the completed CI `runtime.jsonl` file.
@@ -29,12 +29,12 @@ Use system mode for MDM deployments so endpoint events land in the shared system
## Destination categories
-### Asymptote Managed
+### Beacon Managed
-Use this path when Beacon events should appear on the Asymptote dashboard. A device key is issued only after a member of your organization approves the machine in the browser, and revoking it stops ingestion within a minute.
+Use this path when Beacon events should appear on the Beacon dashboard. A device key is issued only after a member of your organization approves the machine in the browser, and revoking it stops ingestion within a minute.
<Columns cols={2}>
- <Card title="Asymptote Managed" icon="tower-broadcast" href="/log-forwarding/asymptote">
+ <Card title="Beacon Managed" icon="tower-broadcast" href="/log-forwarding/asymptote">
Vector `http` forwarder over local JSONL with a per-device key; what leaves the machine, the wire contract, and revocation.
</Card>
<Card title="beacon endpoint asymptote" icon="terminal" href="/cli/asymptote">
@@ -214,7 +214,7 @@ For Microsoft Sentinel, generate Beacon's Sentinel content pack and configure Az
beacon endpoint sentinel install-pack --system --output ./beacon-sentinel-pack
```
-The generated pack includes setup guidance, `table-schema.json`, `dcr-template.json`, `dcr-transform.kql`, starter hunting queries, example detection logic, and sample events. Azure tenant IDs, client secrets, workspace IDs, DCR identifiers, and ingestion endpoints stay in Azure Monitor, endpoint-management tooling, or customer-managed forwarders rather than Beacon endpoint configuration.
+The generated pack includes setup guidance, `table-schema.json`, `dcr-template.json`, `dcr-transform.kql`, starter hunting queries, example detection logic, and sample events. Azure tenant IDs, client secrets, workspace IDs, DCR identifiers, and ingestion endpoints stay in Azure Monitor, endpoint-management tooling, or customer-managed forwarders rather tha Beacon endpoint configuration.
See [Microsoft Sentinel forwarding](/log-forwarding/microsoft-sentinel) for Azure Monitor Agent setup, DCR configuration, validation queries, and content handling guidance.
@@ -226,7 +226,7 @@ For AWS CloudWatch Logs, generate Beacon's CloudWatch content pack and configure
beacon endpoint cloudwatch install-pack --system --output ./beacon-cloudwatch-pack
```
-The generated pack includes setup guidance, a Vector `aws_cloudwatch_logs` sink template, and sample events. AWS credentials, IAM roles, log group retention, stream naming, and encryption stay in AWS, Vector, endpoint-management tooling, or your secret store rather than Beacon endpoint configuration.
+The generated pack includes setup guidance, a Vector `aws_cloudwatch_logs` sink template, and sample events. AWS credentials, IAM roles, log group retention, stream naming, and encryption stay in AWS, Vector, endpoint-management tooling, or your secret store rather tha Beacon endpoint configuration.
See [AWS CloudWatch Logs forwarding](/log-forwarding/cloudwatch) for IAM, Vector setup, CloudWatch Logs queries, and validation steps.
@@ -238,7 +238,7 @@ For AWS S3, generate Beacon's S3 content pack and configure a customer-managed V
beacon endpoint s3 install-pack --system --output ./beacon-s3-pack
```
-The generated pack includes setup guidance, a Vector `aws_s3` sink template, a one-shot AWS CLI smoke-test script, and sample events. AWS credentials, bucket policy, lifecycle, retention, encryption, and object ownership stay in AWS, Vector, endpoint-management tooling, or your secret store rather than Beacon endpoint configuration.
+The generated pack includes setup guidance, a Vector `aws_s3` sink template, a one-shot AWS CLI smoke-test script, and sample events. AWS credentials, bucket policy, lifecycle, retention, encryption, and object ownership stay in AWS, Vector, endpoint-management tooling, or your secret store rather tha Beacon endpoint configuration.
See [macOS System-Mode Object Storage Forwarding](/guides/macos-object-storage-system)
for bucket creation, IAM, credentials, Vector setup, and validation.
@@ -263,9 +263,9 @@ See [macOS System-Mode Object Storage Forwarding](/guides/macos-object-storage-s
for bucket creation, IAM, Vector `0.56` authentication limits, safe credential
delivery and rotation, and validation.
-### Asymptote Managed
+### Beacon Managed
-For the Asymptote dashboard, generate the Asymptote pack and run Vector with the device key and ingest URL issued by enrollment. `beacon endpoint connect` does this for you as a managed service.
+For the Beacon dashboard, generate the Beacon pack and run Vector with the device key and ingest URL issued by enrollment. `beacon endpoint connect` does this for you as a managed service.
```bash title="Generate the integration pack"
beacon endpoint asymptote install-pack --system --output ./beacon-asymptote-pack
@@ -273,7 +273,7 @@ beacon endpoint asymptote install-pack --system --output ./beacon-asymptote-pack
The generated pack includes setup guidance, a Vector `http` sink template that reads the device key from a `0600` secrets file through Vector's secret backend, a one-shot credential and upload smoke-test script, and sample events. Only the runtime and inventory JSONL lines leave the machine; the ingest service stamps organization and device identity server-side.
-See [Asymptote Managed](/log-forwarding/asymptote) for the wire contract, revocation, and offline behavior.
+See [Beacon Managed](/log-forwarding/asymptote) for the wire contract, revocation, and offline behavior.
### Vector log forwarding
diff --git a/docs/log-forwarding/rapid7.mdx b/docs/log-forwarding/rapid7.mdx
index b80b0cb2..40925d36 100644
--- a/docs/log-forwarding/rapid7.mdx
+++ b/docs/log-forwarding/rapid7.mdx
@@ -31,7 +31,7 @@ Recommended setup:
```text
Data Collection > Setup Event Source > Add Event Source > Raw Data > Custom Logs
Collection Method: Webhook
-Name: Asymptote Agent Beacon
+Name: Beacon Agent Beacon
JSON Events Key: leave blank for Beacon NDJSON payloads
```
diff --git a/docs/log-forwarding/splunk.mdx b/docs/log-forwarding/splunk.mdx
index 83464110..747b96f1 100644
--- a/docs/log-forwarding/splunk.mdx
+++ b/docs/log-forwarding/splunk.mdx
@@ -61,7 +61,7 @@ beacon endpoint repair \
| Event format | One HEC event per JSONL line |
| Payload | Preserve the full Beacon JSON object as the HEC `event` |
-If you use a customer-managed forwarder instead of Beacon's collector destination, store the token in that forwarder's secret store rather than Beacon configuration.
+If you use a customer-managed forwarder instead of Beacon's collector destination, store the token in that forwarder's secret store rather tha Beacon configuration.
## Example HEC payload
diff --git a/docs/manage/configure-s3-data-connector.mdx b/docs/manage/configure-s3-data-connector.mdx
index 7340579d..f451cb5b 100644
--- a/docs/manage/configure-s3-data-connector.mdx
+++ b/docs/manage/configure-s3-data-connector.mdx
@@ -1,19 +1,19 @@
---
title: "Configure S3 Data Connector"
-description: "Configure read-only S3 access for Asymptote ingestion."
+description: "Configure read-only S3 access for Beacon ingestion."
---
## Overview
-Asymptote can ingest customer-hosted event files from a private AWS S3 bucket or prefix. Grant Asymptote's ingestion worker read-only access to the bucket that contains the event files.
+Beacon can ingest customer-hosted event files from a private AWS S3 bucket or prefix. Grant Beacon's ingestion worker read-only access to the bucket that contains the event files.
Do not make the bucket public. Do not grant write or delete permissions.
-At the end of setup, send Asymptote the full IAM role ARN for the role you create.
+At the end of setup, send Beacon the full IAM role ARN for the role you create.
## Customer steps
-1. Send Asymptote the S3 location details.
+1. Send Beacon the S3 location details.
Include:
@@ -32,7 +32,7 @@ At the end of setup, send Asymptote the full IAM role ARN for the role you creat
3. Configure the role trust policy.
- Use the IAM ARN Asymptote gives you as the trusted principal. Replace `ASYMPTOTE_IAM_ARN` with that ARN.
+ Use the IAM ARN Beacon gives you as the trusted principal. Replace `ASYMPTOTE_IAM_ARN` with that ARN.
```json title="IAM role trust policy"
{
@@ -96,7 +96,7 @@ At the end of setup, send Asymptote the full IAM role ARN for the role you creat
The KMS key policy must also allow this IAM role to use `kms:Decrypt`.
-6. Send Asymptote the final onboarding details.
+6. Send Beacon the final onboarding details.
Send:
@@ -115,7 +115,7 @@ Share a representative sample file before production ingestion. The sample shoul
## Related
<Columns cols={2}>
- <Card title="Asymptote Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
Review managed visibility, governance, and investigation workflows.
</Card>
<Card title="Endpoint Event Schema" icon="code" href="/telemetry-schema/event-schema">
diff --git a/docs/manage/connect-okta.mdx b/docs/manage/connect-okta.mdx
index 7eb6811f..ed06b6ab 100644
--- a/docs/manage/connect-okta.mdx
+++ b/docs/manage/connect-okta.mdx
@@ -1,26 +1,26 @@
---
title: "Connect Okta"
-description: "Connect Okta to populate identity and device inventory in Asymptote."
+description: "Connect Okta to populate identity and device inventory in Beacon."
---
## Overview
-Connect Okta from the Asymptote dashboard to automatically populate the users, groups, and devices tabs.
+Connect Okta from the Beacon dashboard to automatically populate the users, groups, and devices tabs.
## Connect Okta
-1. Log in to the Asymptote dashboard.
+1. Log in to the Beacon dashboard.
2. Go to **Connectors**.
3. Find the Okta integration.
4. Click **Connect**.
5. Enter your Okta org URL.
6. Enter your Okta API token.
-<Frame caption="Use the Okta connector setup flow in the Asymptote dashboard to enter your Okta org URL and API token.">
- <img src="/images/asymptote_dashboard_okta_connector.png" alt="Asymptote dashboard Okta connector setup form." />
+<Frame caption="Use the Okta connector setup flow in the Beacon dashboard to enter your Okta org URL and API token.">
+ <img src="/images/asymptote_dashboard_okta_connector.png" alt="Beacon dashboard Okta connector setup form." />
</Frame>
-After the connector is authorized, Asymptote automatically syncs Okta data into the users, groups, and devices tabs in the dashboard.
+After the connector is authorized, Beacon automatically syncs Okta data into the users, groups, and devices tabs in the dashboard.
## Generate an Okta API token
@@ -31,8 +31,8 @@ Create the Okta API token from the Okta Admin Console:
3. Select **Tokens**.
4. Click **Create token**.
-<Frame caption="Generate the API token from the Okta Admin Console before returning to the Asymptote connector setup.">
+<Frame caption="Generate the API token from the Okta Admin Console before returning to the Beacon connector setup.">
<img src="/images/okta_token_generation.png" alt="Okta Admin Console API token generation screen." />
</Frame>
-Copy the generated token and paste it into the Okta connector setup flow in Asymptote.
+Copy the generated token and paste it into the Okta connector setup flow in Beacon.
diff --git a/docs/manage/connect-slack.mdx b/docs/manage/connect-slack.mdx
index f0ac2e5d..04d71979 100644
--- a/docs/manage/connect-slack.mdx
+++ b/docs/manage/connect-slack.mdx
@@ -1,38 +1,38 @@
---
title: "Connect Slack"
-description: "Connect Slack so Asymptote can send alert notifications to your workspace."
+description: "Connect Slack so Beacon can send alert notifications to your workspace."
---
## Overview
-Connect Slack from the Asymptote dashboard to send alert notifications to a Slack channel. You can choose either a public channel or a private channel that has the Asymptote Slack app added to it.
+Connect Slack from the Beacon dashboard to send alert notifications to a Slack channel. You can choose either a public channel or a private channel that has the Beacon Slack app added to it.
## Connect Slack
-1. Log in to the Asymptote dashboard.
+1. Log in to the Beacon dashboard.
2. Go to **Connectors**.
3. Find the Slack integration.
4. Click **Connect**.
-5. In Slack, select the workspace where Asymptote should send alert notifications.
-6. Review the permissions requested by the Asymptote app.
+5. In Slack, select the workspace where Beacon should send alert notifications.
+6. Review the permissions requested by the Beacon app.
7. Click **Allow**.
-<Frame caption="Authorize the Asymptote Slack app from Slack's connection screen.">
- <img src="/images/slack_app_asymptote_connection.png" alt="Slack authorization screen for allowing the Asymptote app to access a workspace." />
+<Frame caption="Authorize the Beacon Slack app from Slack's connection screen.">
+ <img src="/images/slack_app_asymptote_connection.png" alt="Slack authorization screen for allowing the Beacon app to access a workspace." />
</Frame>
-After Slack redirects back to Asymptote, choose the channel where alert notifications should be delivered.
+After Slack redirects back to Beacon, choose the channel where alert notifications should be delivered.
## Choose a notification channel
-1. Open the Slack connector in Asymptote.
+1. Open the Slack connector in Beacon.
2. Search for the channel by name or channel ID.
3. Select the Slack channel from the dropdown.
4. Click **Save channel**.
-5. Click **Send test notification** to confirm Asymptote can post to the channel.
+5. Click **Send test notification** to confirm Beacon can post to the channel.
-<Frame caption="Select the Slack channel that should receive Asymptote alert notifications.">
- <img src="/images/slack_connector.png" alt="Asymptote Slack connector setup screen with channel selection and test notification controls." />
+<Frame caption="Select the Slack channel that should receive Beacon alert notifications.">
+ <img src="/images/slack_connector.png" alt="Beacon Slack connector setup screen with channel selection and test notification controls." />
</Frame>
## Add private channels
@@ -43,15 +43,15 @@ Slack only allows apps to post in private channels after the app has been added
2. Click the channel name to open channel details.
3. Go to **Integrations**.
4. Click **Add apps**.
-5. Search for **Asymptote**.
-6. Add the Asymptote app to the channel.
-7. Return to the Slack connector in Asymptote.
+5. Search for **Beacon**.
+6. Add the Beacon app to the channel.
+7. Return to the Slack connector in Beacon.
8. Search for the private channel by name or channel ID.
9. Select it, then click **Save channel**.
10. Click **Send test notification** to confirm delivery.
-<Frame caption="Add the Asymptote app to a private Slack channel before selecting it in the connector.">
- <img src="/images/slack_private_channel.png" alt="Slack private channel integrations screen showing the Asymptote app added to the channel." />
+<Frame caption="Add the Beacon app to a private Slack channel before selecting it in the connector.">
+ <img src="/images/slack_private_channel.png" alt="Slack private channel integrations screen showing the Beacon app added to the channel." />
</Frame>
-If the private channel does not appear immediately, refresh the Asymptote connector page and search again. Make sure the Asymptote app is a member of the private channel before selecting it.
+If the private channel does not appear immediately, refresh the Beacon connector page and search again. Make sure the Beacon app is a member of the private channel before selecting it.
diff --git a/docs/manage/onboarding.mdx b/docs/manage/onboarding.mdx
index 3f6f69e8..91327b28 100644
--- a/docs/manage/onboarding.mdx
+++ b/docs/manage/onboarding.mdx
@@ -1,10 +1,10 @@
---
title: "Onboarding"
-description: "Onboarding guides for Asymptote managed connectors."
+description: "Onboarding guides for Beacon managed connectors."
tag: "Enterprise"
---
-Use these guides to connect managed data sources during Asymptote onboarding.
+Use these guides to connect managed data sources during Beacon onboarding.
<Columns cols={2}>
<Card title="Connect Okta" icon="users" href="/manage/connect-okta">
diff --git a/docs/mdm/index.mdx b/docs/mdm/index.mdx
index 44d3a0ed..887988e7 100644
--- a/docs/mdm/index.mdx
+++ b/docs/mdm/index.mdx
@@ -58,7 +58,7 @@ off by default.
</Step>
</Steps>
-Connecting packaged endpoints to Asymptote Managed is a separate, interactive step today: an admin runs `sudo /opt/beacon/bin/beacon endpoint connect --system` on the machine and the approval page opens in the console user's browser. The package never enrolls a device on its own, and there is no headless enrollment for MDM fleets yet; it is a planned follow-up. See [`beacon endpoint connect`](/cli/endpoint-connect).
+Connecting packaged endpoints to Beacon Managed is a separate, interactive step today: an admin runs `sudo /opt/beacon/bin/beacon endpoint connect --system --dashboard-url https://beacon.sh` on the machine and the approval page opens in the console user's browser. The package never enrolls a device on its own, and there is no headless enrollment for MDM fleets yet; it is a planned follow-up. See [`beacon endpoint connect`](/cli/endpoint-connect).
Environment variables take precedence over MDM script parameters:
diff --git a/docs/mdm/rippling.mdx b/docs/mdm/rippling.mdx
index 04d52c77..ffe2a5e7 100644
--- a/docs/mdm/rippling.mdx
+++ b/docs/mdm/rippling.mdx
@@ -279,7 +279,7 @@ The full cleanup makes a best-effort removal of Beacon LaunchDaemons, endpoint
and forwarder configuration, package files and receipts, and Beacon-managed
active-user configuration. It reports some failures as warnings, so inspect its
output and verify the result. Set `BEACON_KEEP_LOGS=1` to retain local logs or
-`BEACON_CLEAN_ALL_USERS=1` to clean Beacon-owned configuration for all local
+`BEACON_CLEAN_ALL_USERS=1` to clea Beacon-owned configuration for all local
users.
## Troubleshooting
diff --git a/docs/platforms/macos.mdx b/docs/platforms/macos.mdx
index e345c14f..ad743731 100644
--- a/docs/platforms/macos.mdx
+++ b/docs/platforms/macos.mdx
@@ -10,6 +10,7 @@ There are two ways in, and which one you want depends on whether you are setting
## Your own machine
```bash title="Install the CLI, then the endpoint"
+brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon
beacon endpoint install
diff --git a/docs/runtimes/antigravity-cli.mdx b/docs/runtimes/antigravity-cli.mdx
index a29b2cb9..65d5198b 100644
--- a/docs/runtimes/antigravity-cli.mdx
+++ b/docs/runtimes/antigravity-cli.mdx
@@ -1,11 +1,11 @@
---
title: "Antigravity CLI"
-description: "Asymptote support details for Antigravity CLI endpoint telemetry"
+description: "Beacon support details for Antigravity CLI endpoint telemetry"
---
## Runtime overview
-Asymptote supports Antigravity CLI through native hook payloads sent to `beacon-hooks`. Antigravity support was added in the endpoint agent in `v0.0.29`.
+Beacon supports Antigravity CLI through native hook payloads sent to `beacon-hooks`. Antigravity support was added in the endpoint agent in `v0.0.29`.
## Prerequisites
@@ -13,17 +13,17 @@ Before enabling Antigravity hooks, make sure:
- Antigravity CLI is installed as `antigravity` or `antigravity-cli`, or an Antigravity hook config directory exists.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote hooks are installed with `beacon endpoint hooks install --harness antigravity`.
+- Beacon hooks are installed with `beacon endpoint hooks install --harness antigravity`.
- For project-level collection, install hooks from the target project with `--level project`.
- Antigravity is restarted after hook install or removal so new sessions load the updated hook configuration.
## Collection path
-Antigravity invokes Asymptote's hook adapter from Antigravity hook configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.
+Antigravity invokes Beacon's hook adapter from Antigravity hook configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.
## Discovery and status
-Asymptote detects Antigravity through the `antigravity` or `antigravity-cli` executable, `~/.gemini/config`, or `./.agents`, then checks Asymptote hook configuration.
+Beacon detects Antigravity through the `antigravity` or `antigravity-cli` executable, `~/.gemini/config`, or `./.agents`, then checks Beacon hook configuration.
Use `beacon endpoint hooks status --harness antigravity` to inspect Antigravity hook status.
@@ -41,7 +41,7 @@ For project-level hooks, run:
beacon endpoint hooks install --harness antigravity --level project
```
-Asymptote writes user-level Antigravity hooks to `~/.gemini/config/hooks.json` and project-level hooks to `./.agents/hooks.json`. It manages a `beacon-endpoint` hook block and preserves unrelated hook blocks.
+Beacon writes user-level Antigravity hooks to `~/.gemini/config/hooks.json` and project-level hooks to `./.agents/hooks.json`. It manages a `beacon-endpoint` hook block and preserves unrelated hook blocks.
## Telemetry coverage
@@ -52,7 +52,7 @@ Asymptote writes user-level Antigravity hooks to `~/.gemini/config/hooks.json` a
| Local JSONL and dashboard | Supported |
| MDM deployment | Supported for the endpoint agent. Antigravity hooks are installed separately in the logged-in user's context or project context |
-Antigravity can invoke a pre-tool hook before its transcript file contains readable prompt text. Asymptote waits until the transcript is available before marking `prompt.submitted` as emitted, so the next hook in the same session can still record the prompt event.
+Antigravity can invoke a pre-tool hook before its transcript file contains readable prompt text. Beacon waits until the transcript is available before marking `prompt.submitted` as emitted, so the next hook in the same session can still record the prompt event.
## Deployment notes
diff --git a/docs/runtimes/browser-extension.mdx b/docs/runtimes/browser-extension.mdx
index 490c619a..cf825c0c 100644
--- a/docs/runtimes/browser-extension.mdx
+++ b/docs/runtimes/browser-extension.mdx
@@ -1,11 +1,11 @@
---
title: "Browser Extension"
-description: "Install and configure the Asymptote browser extension that collects Claude.ai and ChatGPT chat telemetry"
+description: "Install and configure the Beacon browser extension that collects Claude.ai and ChatGPT chat telemetry"
---
## Overview
-Asymptote collects browser chat telemetry through an optional Chrome MV3 extension. It reads the chat streams of the sites you enable and relays them into the same local pipeline as agent activity, so browser conversations land in the runtime log next to CLI agent events.
+Beacon collects browser chat telemetry through an optional Chrome MV3 extension. It reads the chat streams of the sites you enable and relays them into the same local pipeline as agent activity, so browser conversations land in the runtime log next to CLI agent events.
One extension covers both supported sites:
@@ -50,7 +50,7 @@ Events collected this way carry `harness.collection_method` of `otlp`, and a har
## Discovery and status
-Asymptote treats the browser extension as a user-installed source. It is not configured by `beacon endpoint install`, has no hook or plugin file on disk, and does not appear in `beacon endpoint status`, which reports on the endpoint service rather than on browser extensions.
+Beacon treats the browser extension as a user-installed source. It is not configured by `beacon endpoint install`, has no hook or plugin file on disk, and does not appear in `beacon endpoint status`, which reports on the endpoint service rather than on browser extensions.
Its presence is therefore observed rather than declared: the evidence that it is working is `claude_web` or `chatgpt_web` events arriving in the runtime log. See [Confirm it is working](#confirm-it-is-working).
@@ -63,7 +63,7 @@ The extension installs unpacked through Chrome's developer mode, so Chrome will
No prebuilt archive is published yet, so building from source is currently the only way to get the extension. It needs Node 22 or newer and takes a few seconds:
```bash
-git clone https://github.com/Asymptote-Labs/agent-beacon.git
+git clone https://github.com/asymptote-labs/agent-beacon.git
cd agent-beacon/browser-extension
npm ci
npm run build
@@ -77,7 +77,7 @@ pwd -P # then append /dist
### Use a release archive
-Once an `ext-v*` release is published, you will be able to skip the build and download `agent-beacon-browser-extension-<version>-chrome.zip` with its `.sha256` from the [releases page](https://github.com/Asymptote-Labs/agent-beacon/releases), then verify and unzip it:
+Once an `ext-v*` release is published, you will be able to skip the build and download `agent-beacon-browser-extension-<version>-chrome.zip` with its `.sha256` from the [releases page](https://github.com/asymptote-labs/agent-beacon/releases), then verify and unzip it:
```bash
shasum -a 256 -c agent-beacon-browser-extension-<version>-chrome.zip.sha256
diff --git a/docs/runtimes/chatgpt-web.mdx b/docs/runtimes/chatgpt-web.mdx
index 99728544..23761faf 100644
--- a/docs/runtimes/chatgpt-web.mdx
+++ b/docs/runtimes/chatgpt-web.mdx
@@ -1,11 +1,11 @@
---
title: "ChatGPT"
-description: "Asymptote support details for ChatGPT browser chat telemetry"
+description: "Beacon support details for ChatGPT browser chat telemetry"
---
## Runtime overview
-Asymptote collects ChatGPT chat telemetry through the optional [browser extension](/runtimes/browser-extension). Every turn on chatgpt.com becomes prompt and response events in the local runtime log, attributed to the `chatgpt_web` harness so it stays separate from Codex CLI and other agents.
+Beacon collects ChatGPT chat telemetry through the optional [browser extension](/runtimes/browser-extension). Every turn on chatgpt.com becomes prompt and response events in the local runtime log, attributed to the `chatgpt_web` harness so it stays separate from Codex CLI and other agents.
Both `chatgpt.com` and the older `chat.openai.com` host are covered.
@@ -20,7 +20,7 @@ Support is in beta. The ChatGPT chat API is private and undocumented, so a chang
The extension's main-world interceptor tees the streamed response from the message-send endpoint, `POST /backend-api/f/conversation`. The ChatGPT adapter reads the site's `delta_encoding: v1` Server-Sent Event stream, where each frame patches a running document rather than carrying a finished message, and rebuilds one turn from it:
-| Stream signal | What Asymptote takes from it |
+| Stream signal | What Beacon takes from it |
|---------------|------------------------------|
| The outbound request body | Prompt text, the input messages, and the requested model |
| `conversation_id` in the request body or the resume token | `session.id` and `gen_ai.conversation.id` |
@@ -86,7 +86,7 @@ If nothing arrives, work through the [troubleshooting steps](/runtimes/browser-e
- **The stream format is private.** The adapter is written defensively and degrades to a partial turn rather than failing, but a site change can still stop capture until the adapter is updated.
- **Handed-off streams are not captured yet.** ChatGPT sometimes moves a response to a separate resume endpoint instead of streaming it inline. Those turns are missed today; capturing them is a planned follow-up.
-- **No token usage.** Nothing in the stream carries token counts, and Asymptote does not estimate them.
+- **No token usage.** Nothing in the stream carries token counts, and Beacon does not estimate them.
- **Only the chat stream is read.** Uploaded files, canvas documents, and content rendered outside the stream are not captured.
- **Retention defaults to `full`.** Prompt and response text is retained unless you change the mode in the extension's popup. See [retained content](/runtimes/browser-extension#retained-content).
diff --git a/docs/runtimes/claude-code-ci.mdx b/docs/runtimes/claude-code-ci.mdx
index 9dbe1ecf..0d739699 100644
--- a/docs/runtimes/claude-code-ci.mdx
+++ b/docs/runtimes/claude-code-ci.mdx
@@ -1,20 +1,11 @@
---
title: "CI Agent Telemetry"
-description: "Capture supported agent telemetry in CI with Asymptote"
+description: "Capture supported agent telemetry in CI with Beacon"
---
-<Frame>
- <iframe
- src="https://www.loom.com/embed/f45c536b9f37455493f7d513ce6f1866?t=0s"
- title="CI Agent Telemetry walkthrough"
- allowFullScreen
- style={{ aspectRatio: "16 / 9", width: "100%", border: 0 }}
- />
-</Frame>
-
## Runtime overview
-Asymptote can capture supported agent telemetry for a single CI job without installing a persistent endpoint service on the runner. The CI integration starts a temporary local collector, configures the selected agent harness, writes normalized CI runtime JSONL, and validates that events were captured before the job exits.
+Beacon can capture supported agent telemetry for a single CI job without installing a persistent endpoint service on the runner. The CI integration starts a temporary local collector, configures the selected agent harness, writes normalized CI runtime JSONL, and validates that events were captured before the job exits.
## How it works
@@ -38,7 +29,7 @@ beacon ci start --harness claude
beacon ci finish --min-events 1
```
-During collection, Asymptote:
+During collection, Beacon:
1. Starts a temporary local OpenTelemetry collector.
2. Configures supported agent telemetry for the wrapped command or later session steps.
@@ -47,7 +38,7 @@ During collection, Asymptote:
5. Validates that matching agent events were captured.
6. Leaves the completed runtime log available as a CI artifact or upload target.
-By default, Asymptote writes CI artifacts under `$RUNNER_TEMP/beacon` when `RUNNER_TEMP` is available. Otherwise it uses the system temp directory.
+By default, Beacon writes CI artifacts under `$RUNNER_TEMP/beacon` when `RUNNER_TEMP` is available. Otherwise it uses the system temp directory.
| Artifact | Default path |
| --- | --- |
@@ -57,16 +48,16 @@ By default, Asymptote writes CI artifacts under `$RUNNER_TEMP/beacon` when `RUNN
## Telemetry coverage
-CI collection captures supported prompt, tool, command, file, lifecycle, and run context where the configured agent emits telemetry during the job. For example, Claude Code CI collection captures Claude Code events when the `claude` harness is configured. When `GITHUB_ACTIONS=true`, Asymptote also records GitHub Actions metadata such as workflow, run ID, commit, ref, and actor.
+CI collection captures supported prompt, tool, command, file, lifecycle, and run context where the configured agent emits telemetry during the job. For example, Claude Code CI collection captures Claude Code events when the `claude` harness is configured. When `GITHUB_ACTIONS=true`, Beacon also records GitHub Actions metadata such as workflow, run ID, commit, ref, and actor.
-Asymptote applies redaction, sanitization, truncation, and event-size limits before writing the CI runtime JSONL file. Artifact retention, access, object storage, and downstream forwarding remain controlled by your CI and security pipeline.
+Beacon applies redaction, sanitization, truncation, and event-size limits before writing the CI runtime JSONL file. Artifact retention, access, object storage, and downstream forwarding remain controlled by your CI and security pipeline.
## GitHub Actions
-Use the Asymptote GitHub Action when you want the workflow to install the CI collector and upload the runtime log artifact. Pass a command when the workflow invokes the agent directly.
+Use the Beacon GitHub Action when you want the workflow to install the CI collector and upload the runtime log artifact. Pass a command when the workflow invokes the agent directly.
```yaml
-- name: Run an agent with Asymptote telemetry
+- name: Run an agent with Beacon telemetry
uses: asymptote-labs/[email protected]
with:
command: claude --print "Review this pull request"
@@ -77,7 +68,7 @@ Use the Asymptote GitHub Action when you want the workflow to install the CI col
To wrap a third-party action that launches an agent internally, start and finish a Beacon session around that action. Anthropic's Claude Code Security Review action is one example:
```yaml
-- name: Start Asymptote telemetry
+- name: Start Beacon telemetry
uses: asymptote-labs/[email protected]
with:
mode: start
@@ -87,7 +78,7 @@ To wrap a third-party action that launches an agent internally, start and finish
with:
claude-api-key: ${{ secrets.CLAUDE_API_KEY }}
-- name: Finish Asymptote telemetry
+- name: Finish Beacon telemetry
if: always()
uses: asymptote-labs/[email protected]
with:
@@ -97,8 +88,8 @@ To wrap a third-party action that launches an agent internally, start and finish
See the sample workflow:
-- [Claude Code telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/claude-code-telemetry.yml)
-- [Claude Code Security Review session workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/claude-security-review-session.yml)
+- [Claude Code telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/claude-code-telemetry.yml)
+- [Claude Code Security Review session workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/claude-security-review-session.yml)
## Upload to object storage
@@ -112,7 +103,7 @@ Upload to Amazon S3:
role-to-assume: ${{ secrets.BEACON_TELEMETRY_ROLE_ARN }}
aws-region: us-east-1
-- name: Run an agent with Asymptote telemetry
+- name: Run an agent with Beacon telemetry
uses: asymptote-labs/[email protected]
env:
BEACON_CI_S3_BUCKET: my-beacon-telemetry
@@ -130,7 +121,7 @@ Upload to Google Cloud Storage:
workload_identity_provider: ${{ secrets.BEACON_GCP_WORKLOAD_IDENTITY_PROVIDER }}
service_account: ${{ secrets.BEACON_GCP_SERVICE_ACCOUNT }}
-- name: Run an agent with Asymptote telemetry
+- name: Run an agent with Beacon telemetry
uses: asymptote-labs/[email protected]
env:
BEACON_CI_GCS_BUCKET: my-beacon-telemetry
@@ -142,9 +133,9 @@ Upload to Google Cloud Storage:
See the sample workflows:
-- [S3 upload telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/s3-upload-telemetry.yml)
-- [GCS upload telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/gcs-upload-telemetry.yml)
-- [S3 and GCS upload telemetry workflow](https://github.com/Asymptote-Labs/agent-beacon/blob/main/examples/github-actions/s3-gcs-upload-telemetry.yml)
+- [S3 upload telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/s3-upload-telemetry.yml)
+- [GCS upload telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/gcs-upload-telemetry.yml)
+- [S3 and GCS upload telemetry workflow](https://github.com/asymptote-labs/agent-beacon/blob/main/examples/github-actions/s3-gcs-upload-telemetry.yml)
## Validation behavior
diff --git a/docs/runtimes/claude-code-cloud-agents.mdx b/docs/runtimes/claude-code-cloud-agents.mdx
index b17ee348..7b32e2e4 100644
--- a/docs/runtimes/claude-code-cloud-agents.mdx
+++ b/docs/runtimes/claude-code-cloud-agents.mdx
@@ -1,21 +1,12 @@
---
title: "Claude Code Cloud Agents"
-description: "Capture Claude Code cloud agent telemetry and send each session log to Asymptote Managed or to object storage you own"
+description: "Capture Claude Code cloud agent telemetry and send each session log to Beacon Managed or to object storage you own"
---
-<Frame>
- <iframe
- src="https://www.loom.com/embed/5de72ffb97d7409db292119aada1218b?t=0s"
- title="Claude Code Cloud Agents walkthrough"
- allowFullScreen
- style={{ aspectRatio: "16 / 9", width: "100%", border: 0 }}
- />
-</Frame>
-
## Overview
Use this integration to capture Claude Code cloud-agent activity and send each
-session log to one of three places: [Asymptote Managed](/deployment/managed),
+session log to one of three places: [Beacon Managed](/deployment/managed),
where it appears in your dashboard next to your laptops' sessions, or a Google
Cloud Storage or Amazon S3 bucket you own.
@@ -30,7 +21,7 @@ Claude Code Cloud Agents run in Anthropic's cloud environment, so Beacon cannot
use the long-running endpoint agent that local installs use. Instead, the setup
script installs Beacon hooks inside the sandbox. During a cloud-agent session,
those hooks write `/tmp/beacon/runtime.jsonl`. When the agent stops, Beacon
-ships that file: to Asymptote Managed it posts the new lines to the same ingest
+ships that file: to Beacon Managed it posts the new lines to the same ingest
endpoint the laptop forwarder uses, so the session shows up in the dashboard a
minute or two later; to a bucket it uploads the whole file as one object.
@@ -38,17 +29,17 @@ minute or two later; to a bucket it uploads the whole file as one object.
flowchart LR
ClaudeWeb["Claude Code Cloud Agents"] --> Hooks["Beacon hooks in sandbox"]
Hooks --> RuntimeLog["/tmp/beacon/runtime.jsonl"]
- RuntimeLog --> Managed["Asymptote Managed ingest → dashboard"]
+ RuntimeLog --> Managed["Beacon Managed ingest → dashboard"]
RuntimeLog --> Storage["Your GCS or S3 bucket"]
```
The setup has three parts:
-1. Get a device key from Asymptote, or create a GCS or S3 upload path with Beacon.
+1. Get a device key from Beacon, or create a GCS or S3 upload path with Beacon.
2. Add Beacon cloud telemetry environment variables to the Claude Code cloud environment.
3. Paste a Beacon-generated setup script into the Claude cloud environment.
-With Asymptote Managed, the sessions land in the same per-organization tables as
+With Beacon Managed, the sessions land in the same per-organization tables as
your endpoints' telemetry, attributed to the device you created for the cloud
environment. With a bucket, each Claude Code cloud agent session writes one
readable JSONL object:
@@ -72,7 +63,7 @@ s3://<bucket>/<prefix>/runtime/date=YYYY-MM-DD/<timestamp>-claude_code_web-<clau
create buckets, IAM users, inline IAM policies, and access keys.
- Claude Code cloud agent access for the repository you want to test.
- A Claude cloud environment with outbound access to:
- - For Asymptote Managed: the ingest host from your device key hand-off
+ - For Beacon Managed: the ingest host from your device key hand-off
(currently `beacon-ingest-gulcylfs4a-uw.a.run.app`)
- For GCS: `oauth2.googleapis.com` and `storage.googleapis.com`
- For S3: `s3.<region>.amazonaws.com`
@@ -82,6 +73,7 @@ s3://<bucket>/<prefix>/runtime/date=YYYY-MM-DD/<timestamp>-claude_code_web-<clau
Install or upgrade Beacon before you start:
```bash
+brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon
brew upgrade beacon
@@ -103,16 +95,16 @@ aws sts get-caller-identity
## 1. Create the upload path
-Choose Asymptote Managed, GCS, or S3 for the cloud-agent session logs.
+Choose Beacon Managed, GCS, or S3 for the cloud-agent session logs.
-### Asymptote Managed
+### Beacon Managed
A cloud sandbox has no browser and no Vector, so it cannot run
[`beacon endpoint connect`](/cli/endpoint-connect). Instead it authenticates with
-a device key that an Asymptote operator mints for the environment itself: one
+a device key that a Beacon operator mints for the environment itself: one
key per cloud environment, bound to your organization, listed on
`/dashboard/endpoints` like any laptop and revocable from there. Ask your
-Asymptote contact for a key, naming the environment (for example
+Beacon contact for a key, naming the environment (for example
"Claude Code web, acme/frontend"). You receive three values to put in the
environment in step 2: `BEACON_CLOUD_UPLOAD=asymptote`, the ingest URL, and the
key itself. Self-serve headless enrollment is on the roadmap.
@@ -234,7 +226,7 @@ BEACON_RUN_EPHEMERAL=true
BEACON_CLOUD_USER_ID_HASH=<stable-user-or-test-id>
```
-For Asymptote Managed, add:
+For Beacon Managed, add:
```bash
BEACON_CLOUD_UPLOAD=asymptote
@@ -303,7 +295,7 @@ Read the README, run pwd && ls, create a tiny temporary markdown note under /tmp
## 5. Verify upload
-For Asymptote Managed, open `/dashboard/endpoints`: the cloud environment's
+For Beacon Managed, open `/dashboard/endpoints`: the cloud environment's
device shows a fresh **last seen** time as soon as the first batch is accepted,
and the session appears on `/dashboard/telemetry` within a couple of minutes,
with `run.provider=claude_code_web` and the Claude session id as the run id.
@@ -363,7 +355,7 @@ run.run_id=cse_...
## Security note
-The Asymptote Managed flow puts a per-device key in the Claude Code environment.
+The Beacon Managed flow puts a per-device key in the Claude Code environment.
It can only append telemetry to your organization's ingest stream; it reads
nothing and grants no dashboard access, and revoking the device on
`/dashboard/endpoints` stops it within a minute. This is the one place a Beacon
@@ -426,10 +418,10 @@ sandbox-specific configuration and should stay out of commits.
<Card title="Log forwarding" icon="database" href="/log-forwarding">
Review local endpoint S3 forwarding for persistent endpoint deployments.
</Card>
- <Card title="Asymptote Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
Use managed secure ingest for production enterprise cloud-agent telemetry.
</Card>
- <Card title="Agent Beacon on GitHub" icon="github" href="https://github.com/Asymptote-Labs/agent-beacon">
+ <Card title="Agent Beacon on GitHub" icon="github" href="https://github.com/asymptote-labs/agent-beacon">
Request new cloud-agent destinations or contribute support.
</Card>
</Columns>
diff --git a/docs/runtimes/claude-code.mdx b/docs/runtimes/claude-code.mdx
index 5958f429..2330e264 100644
--- a/docs/runtimes/claude-code.mdx
+++ b/docs/runtimes/claude-code.mdx
@@ -1,11 +1,11 @@
---
title: "Claude Code"
-description: "Asymptote support details for Claude Code endpoint telemetry"
+description: "Beacon support details for Claude Code endpoint telemetry"
---
## Runtime overview
-Asymptote supports Claude Code through local OpenTelemetry export to Asymptote's localhost collector, optional hook telemetry for richer lifecycle and tool activity, and local session-file sync for historical backfill.
+Beacon supports Claude Code through local OpenTelemetry export to Beacon's localhost collector, optional hook telemetry for richer lifecycle and tool activity, and local session-file sync for historical backfill.
## Prerequisites
@@ -18,9 +18,9 @@ Before enabling Claude Code telemetry, make sure:
## Collection paths
-Claude Code exports OTLP telemetry to the local Asymptote collector. Asymptote writes normalized [endpoint events](/concepts/core-concepts#endpoint-event) to the configured runtime JSONL log and makes them available in the local dashboard.
+Claude Code exports OTLP telemetry to the local Beacon collector. Beacon writes normalized [endpoint events](/concepts/core-concepts#endpoint-event) to the configured runtime JSONL log and makes them available in the local dashboard.
-For richer local telemetry, Asymptote can also install Claude Code hooks with the same hook adapter used by other supported runtimes:
+For richer local telemetry, Beacon can also install Claude Code hooks with the same hook adapter used by other supported runtimes:
```bash title="Install Claude Code hooks"
beacon endpoint hooks install --harness claude
@@ -33,7 +33,7 @@ User-level hooks are written to `~/.claude/settings.json`. Project-level hooks a
beacon endpoint hooks install --harness claude --level project
```
-For backfill, Asymptote can also read Claude Code's committed JSONL session files under `~/.claude/projects`:
+For backfill, Beacon can also read Claude Code's committed JSONL session files under `~/.claude/projects`:
```bash title="Sync Claude Code session files"
beacon endpoint claude status
@@ -44,31 +44,31 @@ The sync path is local and offline. It appends mapped events to the runtime log
## Claude Code Cloud Agents
-Asymptote also supports proof-of-concept telemetry capture from Claude Code
+Beacon also supports proof-of-concept telemetry capture from Claude Code
cloud agents. The cloud setup path installs ephemeral Beacon hooks inside the
Claude cloud sandbox, writes `/tmp/beacon/runtime.jsonl`, and uploads the
session log to customer-managed Google Cloud Storage.
Start with [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) when you want to
-test Claude Code cloud agent telemetry without deploying Asymptote Managed.
+test Claude Code cloud agent telemetry without deploying Beacon Managed.
<Warning>
The self-serve GCS path passes a scoped service-account credential to the
Claude Code cloud environment. Use it for evaluation and prototypes. For
- production enterprise deployments, use [Asymptote Managed](/deployment/managed)
- or contact Asymptote about secure forwarding in your own customer-managed
+ production enterprise deployments, use [Beacon Managed](/deployment/managed)
+ or contact Beacon about secure forwarding in your own customer-managed
infrastructure.
</Warning>
## Discovery and status
-Asymptote detects Claude Code through the `claude` executable and Claude settings paths. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Claude Code is present and configured for local telemetry. Use `beacon endpoint claude status` to inspect local session files and how far the sync cursor has read.
+Beacon detects Claude Code through the `claude` executable and Claude settings paths. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Claude Code is present and configured for local telemetry. Use `beacon endpoint claude status` to inspect local session files and how far the sync cursor has read.
## Install or configuration support
`beacon endpoint install` configures Claude telemetry settings so Claude Code sends OTLP data to the local collector. It enables detailed tool logging so tool-result events include inputs such as Bash commands, file paths, URLs, search patterns, and MCP server/tool arguments. Claude bounds or truncates some input values; tool output content is not enabled by this setting.
-`beacon endpoint hooks install --harness claude` adds Asymptote-managed Claude Code hooks while preserving existing Claude settings and non-Asymptote hooks. `beacon endpoint hooks uninstall --harness claude` removes only Asymptote-managed Claude hook entries.
+`beacon endpoint hooks install --harness claude` adds Beacon-managed Claude Code hooks while preserving existing Claude settings and non-Beacon hooks. `beacon endpoint hooks uninstall --harness claude` removes only Beacon-managed Claude hook entries.
## Telemetry coverage
@@ -137,7 +137,7 @@ If a system collector is running while the CLI is reading the default per-user l
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures supported runtimes.
+ See how Beacon discovers and configures supported runtimes.
</Card>
<Card title="Runtime hooks" icon="plug" href="/cli/hooks">
Install, inspect, and uninstall Claude Code hook telemetry.
diff --git a/docs/runtimes/claude-cowork.mdx b/docs/runtimes/claude-cowork.mdx
index f74c92a4..a7bd4576 100644
--- a/docs/runtimes/claude-cowork.mdx
+++ b/docs/runtimes/claude-cowork.mdx
@@ -1,18 +1,18 @@
---
title: "Claude Cowork"
-description: "Asymptote support details for Claude Cowork endpoint telemetry"
+description: "Beacon support details for Claude Cowork endpoint telemetry"
---
## Runtime overview
-Asymptote supports Claude Cowork through admin-configured OpenTelemetry from Anthropic's service.
+Beacon supports Claude Cowork through admin-configured OpenTelemetry from Anthropic's service.
## Prerequisites
Before enabling Claude Cowork telemetry, make sure:
- You have Claude organization admin access to configure OpenTelemetry export.
-- Asymptote has a durable collector endpoint that Claude Cowork can reach; production setups should use public HTTPS.
+- Beacon has a durable collector endpoint that Claude Cowork can reach; production setups should use public HTTPS.
- You have run `beacon endpoint integrations claude-cowork print-config` to get the exact OTLP settings for the Claude admin console.
- You can validate arrival with `beacon endpoint integrations claude-cowork validate` after Cowork activity is generated.
- Your content handling expectations match what Claude Cowork emits through OTLP.
@@ -32,7 +32,7 @@ collector, not the remote Cowork execution host.
## Discovery and status
-Asymptote treats Claude Cowork as an admin-configured source because telemetry is enabled in Claude organization settings rather than local endpoint settings.
+Beacon treats Claude Cowork as an admin-configured source because telemetry is enabled in Claude organization settings rather than local endpoint settings.
Use `beacon endpoint integrations claude-cowork status` to report whether Claude Cowork is detected and whether Cowork events have been observed in the endpoint runtime log.
diff --git a/docs/runtimes/claude-web.mdx b/docs/runtimes/claude-web.mdx
index d5829e59..73885a6e 100644
--- a/docs/runtimes/claude-web.mdx
+++ b/docs/runtimes/claude-web.mdx
@@ -1,11 +1,11 @@
---
title: "Claude.ai"
-description: "Asymptote support details for Claude.ai browser chat telemetry"
+description: "Beacon support details for Claude.ai browser chat telemetry"
---
## Runtime overview
-Asymptote collects Claude.ai chat telemetry through the optional [browser extension](/runtimes/browser-extension). Every turn on claude.ai becomes prompt, response, and tool events in the local runtime log, attributed to the `claude_web` harness so it stays separate from Claude Code and other CLI agents.
+Beacon collects Claude.ai chat telemetry through the optional [browser extension](/runtimes/browser-extension). Every turn on claude.ai becomes prompt, response, and tool events in the local runtime log, attributed to the `claude_web` harness so it stays separate from Claude Code and other CLI agents.
Support is in beta. The claude.ai chat API is private and undocumented, so a change on the site can interrupt capture until the adapter is updated.
@@ -18,7 +18,7 @@ Support is in beta. The claude.ai chat API is private and undocumented, so a cha
The extension's main-world interceptor tees the streamed response from claude.ai's completion endpoint. The Claude adapter reads the Anthropic-style Server-Sent Event stream and rebuilds one turn from it:
-| Stream signal | What Asymptote takes from it |
+| Stream signal | What Beacon takes from it |
|---------------|------------------------------|
| The outbound request body | Prompt text and the input messages |
| The conversation id in the request URL or body | `session.id` and `gen_ai.conversation.id` |
@@ -84,7 +84,7 @@ If nothing arrives, work through the [troubleshooting steps](/runtimes/browser-e
- **The stream format is private.** The adapter is written defensively and degrades to a partial turn rather than failing, but a site change can still stop capture until the adapter is updated.
- **Only the chat stream is read.** Attachments, artifacts rendered outside the stream, and project files are not captured.
- **Prompt text comes from the request body.** A turn sent through a path the adapter does not recognize arrives with the response but without the prompt.
-- **Token counts are usually absent.** The adapter reads uncached input, cache creation, cache read, and output counts from the `message_start` and `message_delta` usage objects, but no claude.ai capture on hand has carried a `usage` object at all. Turns therefore normally reach `beacon token-usage` with no token attribution, and Asymptote does not estimate counts it was not given. If the site starts sending them, they land in `gen_ai.usage` with no extension change.
+- **Token counts are usually absent.** The adapter reads uncached input, cache creation, cache read, and output counts from the `message_start` and `message_delta` usage objects, but no claude.ai capture on hand has carried a `usage` object at all. Turns therefore normally reach `beacon token-usage` with no token attribution, and Beacon does not estimate counts it was not given. If the site starts sending them, they land in `gen_ai.usage` with no extension change.
- **Retention defaults to `full`.** Prompt and response text is retained unless you change the mode in the extension's popup. See [retained content](/runtimes/browser-extension#retained-content).
## Related
diff --git a/docs/runtimes/cline.mdx b/docs/runtimes/cline.mdx
index fd323496..70279b8b 100644
--- a/docs/runtimes/cline.mdx
+++ b/docs/runtimes/cline.mdx
@@ -1,13 +1,13 @@
---
title: "Cline"
-description: "Asymptote support details for Cline endpoint telemetry"
+description: "Beacon support details for Cline endpoint telemetry"
---
## Runtime overview
-Asymptote supports [Cline](https://cline.bot/) through a managed local plugin that invokes `beacon-hooks`.
+Beacon supports [Cline](https://cline.bot/) through a managed local plugin that invokes `beacon-hooks`.
-Cline is not a single runtime. The same agent core runs as a VS Code extension, a JetBrains plugin, and a CLI, and Asymptote's plugin covers all of them: it is loaded by whichever host is running, so one install collects telemetry from every surface on that machine.
+Cline is not a single runtime. The same agent core runs as a VS Code extension, a JetBrains plugin, and a CLI, and Beacon's plugin covers all of them: it is loaded by whichever host is running, so one install collects telemetry from every surface on that machine.
## Prerequisites
@@ -15,14 +15,14 @@ Before enabling Cline telemetry, make sure:
- Cline is installed in at least one host, or has a local config directory at `~/.cline`.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote's Cline plugin is installed with `beacon endpoint hooks install --harness cline`.
+- Beacon's Cline plugin is installed with `beacon endpoint hooks install --harness cline`.
- Cline is restarted after plugin install or removal so new sessions load the updated plugin. In the IDE hosts this means reloading the window.
## Collection paths
-Asymptote installs an owned Cline plugin at `~/.cline/plugins/beacon.ts` for user-level hooks or `./.cline/plugins/beacon.ts` for project-level hooks. Cline auto-discovers plugin files in those directories, so no plugin registry command is required. That is also why the install works for the VS Code and JetBrains hosts, neither of which ships a `cline` executable.
+Beacon installs an owned Cline plugin at `~/.cline/plugins/beacon.ts` for user-level hooks or `./.cline/plugins/beacon.ts` for project-level hooks. Cline auto-discovers plugin files in those directories, so no plugin registry command is required. That is also why the install works for the VS Code and JetBrains hosts, neither of which ships a `cline` executable.
-The plugin forwards `beforeRun`, `beforeTool`, `afterTool`, and `afterRun` hook payloads to Asymptote's hook adapter. It spawns the adapter directly with an argument vector rather than through a shell, so the same plugin works unchanged on macOS, Linux, and Windows.
+The plugin forwards `beforeRun`, `beforeTool`, `afterTool`, and `afterRun` hook payloads to Beacon's hook adapter. It spawns the adapter directly with an argument vector rather than through a shell, so the same plugin works unchanged on macOS, Linux, and Windows.
The integration is plugin-based. Cline's own OpenTelemetry export is neither configured nor required by Beacon, and Cline's hosted prompt-storage feature is not used.
@@ -36,7 +36,7 @@ The sync path reads `~/.cline/data/tasks`, `~/.cline/tasks`, Cline's VS Code glo
## Discovery and status
-Asymptote detects Cline through the `~/.cline` directory, treating a `cline` executable on `PATH` as an additional signal rather than the deciding one. A binary check alone would report "not detected" for the IDE hosts, which are the majority of installs.
+Beacon detects Cline through the `~/.cline` directory, treating a `cline` executable on `PATH` as an additional signal rather than the deciding one. A binary check alone would report "not detected" for the IDE hosts, which are the majority of installs.
Use `beacon endpoint hooks status --harness cline` to inspect Cline plugin status. Status reports installed only when the plugin references the hook binary that is actually present, so a plugin left behind by a removed or relocated install is reported as not installed rather than as working telemetry.
diff --git a/docs/runtimes/codex-cli.mdx b/docs/runtimes/codex-cli.mdx
index 1e95deed..bd083d27 100644
--- a/docs/runtimes/codex-cli.mdx
+++ b/docs/runtimes/codex-cli.mdx
@@ -1,11 +1,11 @@
---
title: "Codex CLI and Desktop"
-description: "Asymptote support details for Codex CLI and Codex Desktop endpoint telemetry"
+description: "Beacon support details for Codex CLI and Codex Desktop endpoint telemetry"
---
## Runtime overview
-Asymptote supports Codex CLI runtime telemetry through local OTLP logs and one selective usage-bearing turn trace. Codex Desktop uses the same Codex OTLP configuration path through its app-server process, and Beacon records it as `codex_desktop` instead of merging it with `codex_cli`. A lightweight SessionStart hook records the local OS user for CLI token attribution.
+Beacon supports Codex CLI runtime telemetry through local OTLP logs and one selective usage-bearing turn trace. Codex Desktop uses the same Codex OTLP configuration path through its app-server process, and Beacon records it as `codex_desktop` instead of merging it with `codex_cli`. A lightweight SessionStart hook records the local OS user for CLI token attribution.
## Prerequisites
@@ -20,7 +20,7 @@ Before enabling Codex telemetry, make sure:
## Collection path
-Codex CLI exports local OpenTelemetry logs and traces to Asymptote's localhost collector. Codex Desktop exports the same Codex semantic telemetry from `codex-app-server` when user-level `~/.codex/config.toml` enables OTLP. Asymptote uses Codex semantic logs for session, prompt, approval, and tool-result events. For tokens it keeps only the completed `session_task.turn` span carrying `thread.id`, `turn.id`, model, and usage; hundreds of transport and internal spans remain suppressed. The CLI SessionStart hook writes a metadata-only `session.context` event; it never reads transcript content. Inventory is written by the scheduled inventory job, not by this hook.
+Codex CLI exports local OpenTelemetry logs and traces to Beacon's localhost collector. Codex Desktop exports the same Codex semantic telemetry from `codex-app-server` when user-level `~/.codex/config.toml` enables OTLP. Beacon uses Codex semantic logs for session, prompt, approval, and tool-result events. For tokens it keeps only the completed `session_task.turn` span carrying `thread.id`, `turn.id`, model, and usage; hundreds of transport and internal spans remain suppressed. The CLI SessionStart hook writes a metadata-only `session.context` event; it never reads transcript content. Inventory is written by the scheduled inventory job, not by this hook.
Use `--include-codex-spans` during install or repair only when you need every raw Codex span for troubleshooting. It is not required for token attribution.
@@ -56,10 +56,10 @@ The Codex session sync reads complete JSONL lines and checkpoints by file path a
## CI support
-Asymptote can also capture Codex telemetry in CI with `beacon ci start` and `beacon ci finish`. In GitHub Actions, the Asymptote action creates a temporary `CODEX_HOME` with Codex OTLP settings and exposes it as `steps.<id>.outputs.codex-home` for actions such as `openai/codex-action`.
+Beacon can also capture Codex telemetry in CI with `beacon ci start` and `beacon ci finish`. In GitHub Actions, the Beacon action creates a temporary `CODEX_HOME` with Codex OTLP settings and exposes it as `steps.<id>.outputs.codex-home` for actions such as `openai/codex-action`.
```yaml
-- name: Start Asymptote telemetry
+- name: Start Beacon telemetry
id: beacon
uses: asymptote-labs/[email protected]
with:
@@ -72,7 +72,7 @@ Asymptote can also capture Codex telemetry in CI with `beacon ci start` and `bea
codex-home: ${{ steps.beacon.outputs.codex-home }}
prompt: "Review this pull request"
-- name: Finish Asymptote telemetry
+- name: Finish Beacon telemetry
if: always()
uses: asymptote-labs/[email protected]
with:
@@ -81,7 +81,7 @@ Asymptote can also capture Codex telemetry in CI with `beacon ci start` and `bea
## Discovery and status
-Asymptote detects Codex CLI through the `codex` executable and `~/.codex/config.toml`. Codex Desktop shares the same user-level configuration file, so Desktop app-server events appear once the app emits OTLP to Beacon's local collector. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Codex configuration is present.
+Beacon detects Codex CLI through the `codex` executable and `~/.codex/config.toml`. Codex Desktop shares the same user-level configuration file, so Desktop app-server events appear once the app emits OTLP to Beacon's local collector. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Codex configuration is present.
## Install or configuration support
@@ -127,6 +127,6 @@ If a system collector is running while the CLI is reading the default per-user l
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures supported runtimes.
+ See how Beacon discovers and configures supported runtimes.
</Card>
</Columns>
diff --git a/docs/runtimes/cursor-cloud-agents.mdx b/docs/runtimes/cursor-cloud-agents.mdx
index 6aa63050..6477e65f 100644
--- a/docs/runtimes/cursor-cloud-agents.mdx
+++ b/docs/runtimes/cursor-cloud-agents.mdx
@@ -7,7 +7,7 @@ description: "Capture Cursor cloud agent telemetry and forward cloud-agent runti
Use this integration to capture Cursor cloud-agent activity and upload each
session log to your own Google Cloud Storage or Amazon S3 bucket. It is meant
-for testing cloud-agent telemetry without running a hosted Asymptote backend.
+for testing cloud-agent telemetry without running a hosted Beacon backend.
This flow depends on the Beacon CLI. You run `beacon cloud` commands from your
workstation to create the object-storage upload path, generate project hooks to
@@ -16,7 +16,7 @@ binaries in the Cursor cloud sandbox.
<Info>
If you're interested in leveraging this telemetry ingest across your
- enterprise, [Asymptote Managed](/deployment/managed) is designed for
+ enterprise, [Beacon Managed](/deployment/managed) is designed for
production cloud-agent telemetry ingest at scale.
</Info>
@@ -80,6 +80,7 @@ that value instead.
Install or upgrade Beacon before you start:
```bash
+brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon
brew upgrade beacon
@@ -444,10 +445,10 @@ git diff -- .cursor/hooks.json
<Card title="Log forwarding" icon="database" href="/log-forwarding">
Compare direct cloud-agent uploads with local endpoint object-storage forwarding.
</Card>
- <Card title="Asymptote Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
Use managed secure ingest for production enterprise cloud-agent telemetry.
</Card>
- <Card title="Agent Beacon on GitHub" icon="github" href="https://github.com/Asymptote-Labs/agent-beacon">
+ <Card title="Agent Beacon on GitHub" icon="github" href="https://github.com/asymptote-labs/agent-beacon">
Request new cloud-agent destinations or contribute support.
</Card>
</Columns>
diff --git a/docs/runtimes/cursor.mdx b/docs/runtimes/cursor.mdx
index ab0a68f6..cde25228 100644
--- a/docs/runtimes/cursor.mdx
+++ b/docs/runtimes/cursor.mdx
@@ -1,11 +1,11 @@
---
title: "Cursor"
-description: "Asymptote support details for Cursor endpoint telemetry"
+description: "Beacon support details for Cursor endpoint telemetry"
---
## Runtime overview
-Asymptote supports Cursor through native hook payloads sent to `beacon-hooks`, with local session-store sync for historical backfill.
+Beacon supports Cursor through native hook payloads sent to `beacon-hooks`, with local session-store sync for historical backfill.
For provider-managed Cursor cloud sessions, see
[Cursor Cloud Agents](/runtimes/cursor-cloud-agents).
@@ -15,15 +15,15 @@ Before enabling Cursor hooks, make sure:
- Cursor is installed for the user or the `~/.cursor` directory exists.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote hooks are installed with `beacon endpoint hooks install --harness cursor`.
+- Beacon hooks are installed with `beacon endpoint hooks install --harness cursor`.
- For project-level collection, install hooks from the target project with `--level project`.
- Cursor is restarted after hook install or removal so new sessions load the updated hook configuration.
## Collection path
-Cursor invokes Asymptote's hook adapter from Cursor hook configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.
+Cursor invokes Beacon's hook adapter from Cursor hook configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.
-Asymptote can also read Cursor's committed local session stores:
+Beacon can also read Cursor's committed local session stores:
```bash title="Sync Cursor local sessions"
beacon endpoint cursor status
@@ -34,7 +34,7 @@ The sync path reads Cursor Composer conversations from the global VS Code storag
## Discovery and status
-Asymptote detects Cursor through the Cursor binary or `~/.cursor`, then checks Asymptote hook configuration.
+Beacon detects Cursor through the Cursor binary or `~/.cursor`, then checks Beacon hook configuration.
Use `beacon endpoint hooks status --harness cursor` to inspect Cursor hook status. Use `beacon endpoint cursor status` to inspect local session stores and how much Beacon has synced.
@@ -76,7 +76,7 @@ Run `beacon endpoint cursor sync --watch`, or schedule one-shot sweeps, if you w
Restart Cursor after installing or removing hooks so the updated hook configuration is picked up by new sessions.
-Hook events include metadata such as file path, operation, language, diff hash, and diff byte count. Raw diffs and reasoning text are subject to Asymptote's redaction, sanitization, truncation, and event-size limits before writing.
+Hook events include metadata such as file path, operation, language, diff hash, and diff byte count. Raw diffs and reasoning text are subject to Beacon's redaction, sanitization, truncation, and event-size limits before writing.
## Related
diff --git a/docs/runtimes/deepseek-harness.mdx b/docs/runtimes/deepseek-harness.mdx
index 9d1cbb30..53931e1b 100644
--- a/docs/runtimes/deepseek-harness.mdx
+++ b/docs/runtimes/deepseek-harness.mdx
@@ -1,11 +1,11 @@
---
title: "DeepSeek Harness"
-description: "Asymptote support details for DeepSeek Harness (dsh) endpoint telemetry"
+description: "Beacon support details for DeepSeek Harness (dsh) endpoint telemetry"
---
## Runtime overview
-Asymptote supports DeepSeek Harness — DeepSeek's open agent harness, run as `dsh` — through the Claude Code hook bridge DeepSeek ships in the CLI, sent to `beacon-hooks`.
+Beacon supports DeepSeek Harness — DeepSeek's open agent harness, run as `dsh` — through the Claude Code hook bridge DeepSeek ships in the CLI, sent to `beacon-hooks`.
```bash
beacon endpoint hooks install --harness dsh
@@ -16,7 +16,7 @@ beacon endpoint hooks install --harness dsh
DeepSeek Harness is composed rather than configured: every capability is a plugin, and the CLI, Web, ACP, and SDK surfaces are four compositions of one harness booting from one Harness home. There is one integration rather than one per surface, and one harness name — `deepseek_harness` — rather than a name per surface.
<Note>
-**`dsh` does not read a hooks file until something mounts a reader at it.** `@deepseek-ai/dsh-hooks-claude-code` ships as a dependency of the `dsh` CLI but is not in the default plugin tree, so there is no convention that picks a hooks file up. That is why an Asymptote install here is **two files**: the hooks file, and one row mounting the bridge at it.
+**`dsh` does not read a hooks file until something mounts a reader at it.** `@deepseek-ai/dsh-hooks-claude-code` ships as a dependency of the `dsh` CLI but is not in the default plugin tree, so there is no convention that picks a hooks file up. That is why a Beacon install here is **two files**: the hooks file, and one row mounting the bridge at it.
</Note>
## Prerequisites
@@ -29,16 +29,16 @@ Before enabling DeepSeek Harness telemetry, make sure:
## Collection path
-Asymptote writes two files into the Harness home:
+Beacon writes two files into the Harness home:
| File | Owner | Purpose |
|------|-------|---------|
-| `$DSH_HOME/beacon-endpoint-hooks.json` | Asymptote, outright | The Claude Code hooks file — one command hook per event |
-| `$DSH_HOME/cordis.patch.yml` | **You** | Your patch layer. Asymptote adds one row mounting the bridge at the file above |
+| `$DSH_HOME/beacon-endpoint-hooks.json` | Beacon, outright | The Claude Code hooks file — one command hook per event |
+| `$DSH_HOME/cordis.patch.yml` | **You** | Your patch layer. Beacon adds one row mounting the bridge at the file above |
`$DSH_HOME` defaults to `~/.dsh`, and replaces it when set — matching how `dsh` resolves the Harness home itself.
-The row Asymptote adds looks like this:
+The row Beacon adds looks like this:
```yaml
# Beacon endpoint telemetry. Mounts DeepSeek's Claude Code hook bridge at
@@ -57,17 +57,17 @@ The home-level patch layer is applied over **every** profile and outranks each p
**There is no project scope.** The bridge's `configPath` is process-level — read once at startup — and per-session discovery of a project-local hooks file is unimplemented in the bridge itself. A repository has nowhere to mount a hook bridge from, so `--level project` is **refused with that explanation** rather than quietly becoming a machine-wide install. DeepSeek Harness is also left out of the project-level `--all` sweep for the same reason.
</Warning>
-### Asymptote edits your patch file as a document
+### Beacon edits your patch file as a document
-`cordis.patch.yml` is yours. It carries your comments, your quoting, and `!!js` expressions the loader evaluates at boot — so Asymptote parses it into a YAML node tree, appends or removes **one self-contained element**, and re-encodes from the same tree. Comments, scalar style, and custom tags survive that round trip, and a test pins it.
+`cordis.patch.yml` is yours. It carries your comments, your quoting, and `!!js` expressions the loader evaluates at boot — so Beacon parses it into a YAML node tree, appends or removes **one self-contained element**, and re-encodes from the same tree. Comments, scalar style, and custom tags survive that round trip, and a test pins it.
A self-contained element rather than a row pushed into one of your existing `insert:` lists, so an uninstall removes exactly what an install added.
-Asymptote **refuses** rather than rewriting:
+Beacon **refuses** rather than rewriting:
- a patch file it cannot parse — unlike the hooks file, which it will replace, because this is where your whole plugin tree is tweaked and `dsh`'s parser is not Go's;
- a patch file that is not a list of entries;
-- an `insert` element carrying Asymptote's row alongside rows it did not write.
+- an `insert` element carrying Beacon's row alongside rows it did not write.
<Warning>
**An empty patch file does not boot `dsh`.** A present-but-empty or comments-only `cordis.patch.yml` fails startup — it is not ignored and it is not a warning. So an uninstall that would leave the file empty **removes the file** instead of truncating it. An absent patch layer is skipped cleanly.
@@ -75,7 +75,7 @@ Asymptote **refuses** rather than rewriting:
### Registered events
-The bridge supports seven of Claude Code's hook events. Asymptote registers all seven — there is nothing to leave out, because config for the other 23 is discarded before the bridge's parser sees it.
+The bridge supports seven of Claude Code's hook events. Beacon registers all seven — there is nothing to leave out, because config for the other 23 is discarded before the bridge's parser sees it.
| Event | Adapter subcommand | Timeout |
|-------|--------------------|---------|
@@ -87,9 +87,9 @@ The bridge supports seven of Claude Code's hook events. Asymptote registers all
| `SubagentStart` | `subagent-start` | 10 s |
| `SubagentStop` | `subagent-stop` | 10 s |
-Timeouts are **seconds**, matching Claude Code — the bridge reads `timeout` as `timeoutSec`. Its own default is 600 seconds, which is a very long time to hold an agent turn for a hook that finishes in milliseconds; Asymptote writes explicit lower values as ceilings on a hang, not budgets.
+Timeouts are **seconds**, matching Claude Code — the bridge reads `timeout` as `timeoutSec`. Its own default is 600 seconds, which is a very long time to hold an agent turn for a hook that finishes in milliseconds; Beacon writes explicit lower values as ceilings on a hang, not budgets.
-Asymptote's hooks carry no `matcher`. An absent matcher is the match-all form in this dialect, which is what a telemetry hook wants on all seven — and the bridge validates a written matcher at parse time and rejects the **whole config** on a bad one, so the value that needs no validating is the safer one to write.
+Beacon's hooks carry no `matcher`. An absent matcher is the match-all form in this dialect, which is what a telemetry hook wants on all seven — and the bridge validates a written matcher at parse time and rejects the **whole config** on a bad one, so the value that needs no validating is the safer one to write.
## Discovery and status
@@ -99,7 +99,7 @@ beacon endpoint hooks status --harness dsh
Status reports **both** paths, because `installed` is the conjunction of the two files: a hooks file with nothing mounted at it is a file nothing reads, and a mount pointing at a missing hooks file is a bridge that logs a warning and registers nothing. `beacon endpoint inventory` lists both for the same reason, so a half-install is visible as a half-install.
-DeepSeek Harness reports as the `deepseek_harness` harness with capability `hooks`, and every event carries `harness.collection_method=hook`. The bridge is a plugin, but it is DeepSeek's plugin, shipped and versioned with the CLI; what Asymptote contributes is command hooks, and the thing that runs on each event is the same `beacon-hooks` binary every other hook runtime runs.
+DeepSeek Harness reports as the `deepseek_harness` harness with capability `hooks`, and every event carries `harness.collection_method=hook`. The bridge is a plugin, but it is DeepSeek's plugin, shipped and versioned with the CLI; what Beacon contributes is command hooks, and the thing that runs on each event is the same `beacon-hooks` binary every other hook runtime runs.
## Install or configuration support
@@ -111,7 +111,7 @@ beacon endpoint hooks uninstall --harness dsh
Re-running the install rewrites the hooks file wholesale and **repoints** the mount in place rather than adding a second one — so a reinstall after `$DSH_HOME` moved updates the path the bridge reads, and a repair does not end with each event registered twice.
-Uninstall removes Asymptote's hooks file and its one patch element, and leaves your rows and comments alone.
+Uninstall removes Beacon's hooks file and its one patch element, and leaves your rows and comments alone.
## Telemetry coverage
@@ -152,13 +152,13 @@ Four entries in that table are there because the generic classifier every runtim
### `terminal_send` names its command line `text`
-`dsh` runs commands through a persistent terminal as well as through `bash`, and that tool's payload is `text`, not `command`. Asymptote reads it, so a command run through a terminal session carries a command line rather than being an empty `command.executed` invisible to every rule matching on `command.command`.
+`dsh` runs commands through a persistent terminal as well as through `bash`, and that tool's payload is `text`, not `command`. Beacon reads it, so a command run through a terminal session carries a command line rather than being an empty `command.executed` invisible to every rule matching on `command.command`.
-A call with `submit: false` is still read. It carries control characters or an incomplete REPL line rather than a whole command, so what is recorded is a *fragment* of shell input — worth knowing, and better than letting "send the command in two writes" be a way to run commands Asymptote does not record.
+A call with `submit: false` is still read. It carries control characters or an incomplete REPL line rather than a whole command, so what is recorded is a *fragment* of shell input — worth knowing, and better than letting "send the command in two writes" be a way to run commands Beacon does not record.
### `run_code` is a tool call, not a command
-`run_code` executes a TypeScript program against the other tools and is the one tool that can ask for `danger-full-access`. Asymptote records it as `tool.invoked`, for two reasons.
+`run_code` executes a TypeScript program against the other tools and is the one tool that can ask for `danger-full-access`. Beacon records it as `tool.invoked`, for two reasons.
A program's nested tool calls are **not invisible**: `dsh` dispatches them back through the complete guarded tool pipeline, which is the same seam the hook bridge listens on. So `await tools.bash({command: '...'})` inside a program fires its own `PreToolUse` and `PostToolUse` and is recorded as a command execution with a real command line. Classifying the outer wrapper as a command too would double-count it.
@@ -170,21 +170,21 @@ The program text is not lost: it is retained under `raw.dsh.tool_input.code`, re
The bridge flattens a tool result to text before a hook sees it, so `tool_response` is a plain string rather than an object. `dsh`'s `bash` and `pwsh` tools report a non-zero exit as `[exit code: N]` in that text, and that marker is the only place an exit code reaches a hook.
-Asymptote reads the **last** marker in the output: everything above it is the command's own, and a command that prints something looking like the marker — a test asserting on one, a log line quoting one — would otherwise decide the event's exit code.
+Beacon reads the **last** marker in the output: everything above it is the command's own, and a command that prints something looking like the marker — a test asserting on one, a log line quoting one — would otherwise decide the event's exit code.
A non-zero exit is recorded as `command.executed` with `command.exit_code`, not as a tool failure. A failing test run is an ordinary outcome of a command that ran.
<Note>
-**`command` on `str_replace_editor` is not a shell command.** That tool multiplexes `view`, `create`, `str_replace`, and `insert` onto a `command` argument, and `command` is also what `bash` and `pwsh` call their command line. Asymptote guards on the tool name, so an editor operation is never recorded under `command.command` and a real shell command is never dropped. `view` is the case that matters most: same tool, same arguments as the three writes, and only that word separates looking from creating.
+**`command` on `str_replace_editor` is not a shell command.** That tool multiplexes `view`, `create`, `str_replace`, and `insert` onto a `command` argument, and `command` is also what `bash` and `pwsh` call their command line. Beacon guards on the tool name, so an editor operation is never recorded under `command.command` and a real shell command is never dropped. `view` is the case that matters most: same tool, same arguments as the three writes, and only that word separates looking from creating.
</Note>
## Approvals and enforcement
-**Asymptote records no approval decisions for DeepSeek Harness, and does not synthesize any.**
+**Beacon records no approval decisions for DeepSeek Harness, and does not synthesize any.**
The bridge supports seven events and `PermissionRequest` is not among them, so there is no approval decision anywhere on this runtime's hook surface. `PreToolUse` announces a call the agent is about to make, not a question anybody was asked. This is the same call already settled for [Cline](/runtimes/cline), [Pi](/runtimes/pi), [OpenHands](/runtimes/openhands), [Kiro](/runtimes/kiro), and [fx](/runtimes/vercel-fx).
-Asymptote's observing hooks answer with an empty JSON object, which the bridge's decoder reads as no opinion. They deliberately do **not** answer `allow`: on this runtime that is a real pre-approval, so an observing hook answering it would be disarming your permission gate for every tool call rather than watching it.
+Beacon's observing hooks answer with an empty JSON object, which the bridge's decoder reads as no opinion. They deliberately do **not** answer `allow`: on this runtime that is a real pre-approval, so an observing hook answering it would be disarming your permission gate for every tool call rather than watching it.
Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error. DeepSeek Harness is one of the runtimes where a provider deny takes effect, using Claude Code's deny shape — which is the shape the bridge's decoder reads:
@@ -200,11 +200,11 @@ Enforcement stays behind the optional, off-by-default policy provider seam (`BEA
DeepSeek Harness content is handled like every other runtime. Prompts, tool arguments, commands, command output, paths, and diffs are retained in local or customer-controlled logs, with local secret redaction and per-string limits applied before writing, and a hash and byte count on each content-bearing event. Events over the 64 KiB limit drop raw and retained content, preserve stable metadata, and set `field_truncated`.
-Unlike [Kiro](/runtimes/kiro) and [OpenHands](/runtimes/openhands), Asymptote **does** preserve the verbatim payload under `raw.dsh`, as it does for [Qwen Code](/runtimes/qwen-code) and [Muse Code](/runtimes/muse-code). Non-MCP tool arguments reach no endpoint-schema field on any runtime, so on `dsh` this is where `run_code`'s program, a `glob` or `grep` pattern, a `terminal_send` `submit` flag, and `SessionStart`'s `source` survive. The cost is stated rather than hidden: on a `write` the payload repeats the file content the diff already carries. `raw` is the first thing dropped at the size ceiling, so the duplication is bounded and the diff is what survives.
+Unlike [Kiro](/runtimes/kiro) and [OpenHands](/runtimes/openhands), Beacon **does** preserve the verbatim payload under `raw.dsh`, as it does for [Qwen Code](/runtimes/qwen-code) and [Muse Code](/runtimes/muse-code). Non-MCP tool arguments reach no endpoint-schema field on any runtime, so on `dsh` this is where `run_code`'s program, a `glob` or `grep` pattern, a `terminal_send` `submit` flag, and `SessionStart`'s `source` survive. The cost is stated rather than hidden: on a `write` the payload repeats the file content the diff already carries. `raw` is the first thing dropped at the size ceiling, so the duplication is bounded and the diff is what survives.
## Known gaps
-- **No approval decisions.** The bridge exposes no `PermissionRequest` event, and Asymptote does not synthesize one from `PreToolUse`. Approval rules and dashboards will show nothing for this runtime.
+- **No approval decisions.** The bridge exposes no `PermissionRequest` event, and Beacon does not synthesize one from `PreToolUse`. Approval rules and dashboards will show nothing for this runtime.
- **No token usage or cost.** The bridge builds each payload from a fixed base plus per-event fields, and no usage count is among them on any of the seven events. `dsh` does record usage in its own session log; nothing on the hook surface exposes it. DeepSeek Harness activity therefore does not appear in `beacon token-usage` reports or the dashboard token view.
- **No failed-tool events.** The bridge hands a hook the result's flattened text and nothing else, so a tool that threw is indistinguishable at the hook from one that returned. `tool.failed` is never recorded, and a diff is built from a write's arguments whether or not the write landed. A non-zero shell exit is *not* a tool failure and is recorded as such.
- **No session-end event.** `dsh` has no `SessionEnd`. `Stop` fires when a turn finishes, not when a session ends, so it is recorded as `tool.completed`.
@@ -212,7 +212,7 @@ Unlike [Kiro](/runtimes/kiro) and [OpenHands](/runtimes/openhands), Asymptote **
- **No compaction events.** `PreCompact` and `PostCompact` are among the events the bridge does not support.
- **Subagent detail is thin.** The bridge reports a constant `agent_type` of `general-purpose` and uses the child's session id where Claude Code reports the parent's, so a subagent event cannot be joined to the session that spawned it.
- **No project scope.** See the warning under [Collection path](#collection-path).
-- **Only command hooks run.** The bridge runs shell-form `command` handlers only, which is what Asymptote writes. It has no bearing on Asymptote's install and is noted because it bounds what else you can put in the same file.
+- **Only command hooks run.** The bridge runs shell-form `command` handlers only, which is what Beacon writes. It has no bearing on Beacon's install and is noted because it bounds what else you can put in the same file.
## Deployment notes
@@ -243,6 +243,6 @@ If DeepSeek Harness telemetry is missing:
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
</Columns>
diff --git a/docs/runtimes/devin-cloud-agents.mdx b/docs/runtimes/devin-cloud-agents.mdx
index 9e29d817..761c819e 100644
--- a/docs/runtimes/devin-cloud-agents.mdx
+++ b/docs/runtimes/devin-cloud-agents.mdx
@@ -15,7 +15,7 @@ hook engine. Beacon instead pulls session activity from the Devin
<Info>
If you're interested in leveraging this telemetry ingest across your
- enterprise, [Asymptote Managed](/deployment/managed) is designed for
+ enterprise, [Beacon Managed](/deployment/managed) is designed for
production cloud-agent telemetry ingest at scale.
</Info>
@@ -73,6 +73,7 @@ Beacon uses the Devin session id as the `run_id` and the Devin user id as
Install or upgrade Beacon:
```bash
+brew trust asymptote-labs/tap
brew tap asymptote-labs/tap
brew install beacon
brew upgrade beacon
@@ -235,7 +236,7 @@ in-progress session shows `session.started`, `prompt.submitted`, and
<Card title="Google Cloud Storage forwarding" icon="database" href="/siem-forwarding-gcs">
Review local endpoint GCS forwarding for persistent deployments.
</Card>
- <Card title="Asymptote Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
Use managed secure ingest for production enterprise cloud-agent telemetry.
</Card>
</Columns>
diff --git a/docs/runtimes/devin-desktop.mdx b/docs/runtimes/devin-desktop.mdx
index 5a453615..a05727ea 100644
--- a/docs/runtimes/devin-desktop.mdx
+++ b/docs/runtimes/devin-desktop.mdx
@@ -1,11 +1,11 @@
---
title: "Devin Desktop"
-description: "Asymptote support details for Devin Desktop endpoint telemetry"
+description: "Beacon support details for Devin Desktop endpoint telemetry"
---
## Runtime overview
-Asymptote supports Devin Desktop through Cascade/Windsurf-compatible hook payloads sent to `beacon-hooks`.
+Beacon supports Devin Desktop through Cascade/Windsurf-compatible hook payloads sent to `beacon-hooks`.
## Prerequisites
@@ -13,17 +13,17 @@ Before enabling Devin Desktop hooks, make sure:
- Devin Desktop is installed for the user or available in the workspace where hooks will run.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote hooks are installed with `beacon endpoint hooks install --harness devin-desktop`.
+- Beacon hooks are installed with `beacon endpoint hooks install --harness devin-desktop`.
- For project-level collection, install hooks from the target workspace with `--level project`.
- Devin Desktop is restarted after hook install or removal so new sessions load the updated hook configuration.
## Collection path
-Devin Desktop invokes Asymptote's hook adapter through Cascade/Windsurf hook files. The adapter writes normalized endpoint events to the configured runtime JSONL log.
+Devin Desktop invokes Beacon's hook adapter through Cascade/Windsurf hook files. The adapter writes normalized endpoint events to the configured runtime JSONL log.
## Discovery and status
-Asymptote detects Devin Desktop through Cascade/Windsurf hook paths such as `~/.codeium/windsurf/hooks.json` or `./.windsurf/hooks.json`.
+Beacon detects Devin Desktop through Cascade/Windsurf hook paths such as `~/.codeium/windsurf/hooks.json` or `./.windsurf/hooks.json`.
Use `beacon endpoint hooks status --harness devin-desktop` to inspect Devin Desktop hook status.
@@ -58,11 +58,11 @@ beacon endpoint install --harness claude,codex,devin-desktop
## Deployment notes
-Asymptote writes Devin Desktop user-level hooks to `~/.codeium/windsurf/hooks.json`. Project-level Devin Desktop installs write `./.windsurf/hooks.json`, which can also affect Windsurf/Cascade in that workspace.
+Beacon writes Devin Desktop user-level hooks to `~/.codeium/windsurf/hooks.json`. Project-level Devin Desktop installs write `./.windsurf/hooks.json`, which can also affect Windsurf/Cascade in that workspace.
-Asymptote installs visibility-only hooks for prompt submission, file writes, command execution, MCP tool use, and file reads. The hooks do not block or enforce policy. After installation, generate a Devin Desktop event and check the Asymptote runtime log to validate that the Desktop app executed the hook file.
+Beacon installs visibility-only hooks for prompt submission, file writes, command execution, MCP tool use, and file reads. The hooks do not block or enforce policy. After installation, generate a Devin Desktop event and check the Beacon runtime log to validate that the Desktop app executed the hook file.
-Install and uninstall preserve unrelated settings and non-Asymptote hook commands. Restart Devin Desktop after installing or removing hooks so new sessions pick up the updated hook configuration.
+Install and uninstall preserve unrelated settings and non-Beacon hook commands. Restart Devin Desktop after installing or removing hooks so new sessions pick up the updated hook configuration.
## Related
diff --git a/docs/runtimes/devin.mdx b/docs/runtimes/devin.mdx
index ab6c18e1..ed8ca80a 100644
--- a/docs/runtimes/devin.mdx
+++ b/docs/runtimes/devin.mdx
@@ -1,11 +1,11 @@
---
title: "Devin CLI"
-description: "Asymptote support details for Devin CLI endpoint telemetry"
+description: "Beacon support details for Devin CLI endpoint telemetry"
---
## Runtime overview
-Asymptote supports Devin CLI through native Devin hook payloads sent to `beacon-hooks`.
+Beacon supports Devin CLI through native Devin hook payloads sent to `beacon-hooks`.
## Prerequisites
@@ -13,17 +13,17 @@ Before enabling Devin CLI hooks, make sure:
- Devin CLI is installed for the user or configured in the project where hooks will run.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote hooks are installed with `beacon endpoint hooks install --harness devin-cli`. The legacy `devin` harness name still maps to Devin CLI.
+- Beacon hooks are installed with `beacon endpoint hooks install --harness devin-cli`. The legacy `devin` harness name still maps to Devin CLI.
- For project-level collection, install hooks from the target project with `--level project`.
- Devin CLI is restarted after hook install or removal so new sessions load the updated hook configuration.
## Collection path
-Devin CLI invokes Asymptote's hook adapter from hook entries in Devin configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.
+Devin CLI invokes Beacon's hook adapter from hook entries in Devin configuration. The adapter writes normalized endpoint events to the configured runtime JSONL log.
## Discovery and status
-Asymptote detects Devin CLI through the `devin` executable, `~/.config/devin`, or `./.devin`, then checks Asymptote hook configuration.
+Beacon detects Devin CLI through the `devin` executable, `~/.config/devin`, or `./.devin`, then checks Beacon hook configuration.
Use `beacon endpoint hooks status --harness devin-cli` to inspect Devin CLI hook status.
@@ -52,9 +52,9 @@ beacon endpoint hooks install --harness devin-cli --level project
## Deployment notes
-Asymptote writes Devin CLI user-level hooks under the `hooks` key in `~/.config/devin/config.json`. Devin CLI project-level installs write the standalone hook map to `./.devin/hooks.v1.json`.
+Beacon writes Devin CLI user-level hooks under the `hooks` key in `~/.config/devin/config.json`. Devin CLI project-level installs write the standalone hook map to `./.devin/hooks.v1.json`.
-Install and uninstall preserve unrelated Devin settings and non-Asymptote hook commands. Restart Devin CLI after installing or removing hooks so new sessions pick up the updated hook configuration.
+Install and uninstall preserve unrelated Devin settings and non-Beacon hook commands. Restart Devin CLI after installing or removing hooks so new sessions pick up the updated hook configuration.
## Related
diff --git a/docs/runtimes/factory-droid.mdx b/docs/runtimes/factory-droid.mdx
index 29047c89..fa1e3d60 100644
--- a/docs/runtimes/factory-droid.mdx
+++ b/docs/runtimes/factory-droid.mdx
@@ -1,11 +1,11 @@
---
title: "Factory Droid"
-description: "Asymptote support details for Factory Droid endpoint telemetry"
+description: "Beacon support details for Factory Droid endpoint telemetry"
---
## Runtime overview
-Asymptote supports Factory Droid through an OTLP HTTP launch environment, optional hook telemetry, and a local session-store sync for historical sessions.
+Beacon supports Factory Droid through an OTLP HTTP launch environment, optional hook telemetry, and a local session-store sync for historical sessions.
## Prerequisites
@@ -20,11 +20,11 @@ Before enabling Factory Droid telemetry, make sure:
## Collection path
-Factory Droid can send OTLP HTTP telemetry to Asymptote's local collector. Factory hooks can also invoke Asymptote's hook adapter for richer runtime events where Factory exposes hook payloads. Beacon can also read committed Factory session records from `~/.factory/sessions` and convert them into endpoint events marked `harness.collection_method=poll`.
+Factory Droid can send OTLP HTTP telemetry to Beacon's local collector. Factory hooks can also invoke Beacon's hook adapter for richer runtime events where Factory exposes hook payloads. Beacon can also read committed Factory session records from `~/.factory/sessions` and convert them into endpoint events marked `harness.collection_method=poll`.
## Discovery and status
-Asymptote detects Factory Droid through the `droid` executable and validates `OTEL_TELEMETRY_ENDPOINT` in the effective launch environment.
+Beacon detects Factory Droid through the `droid` executable and validates `OTEL_TELEMETRY_ENDPOINT` in the effective launch environment.
Use `beacon endpoint discover`, `beacon endpoint status`, or `beacon endpoint hooks status --harness factory` to inspect Factory Droid support.
@@ -64,7 +64,7 @@ For scheduled collection, run `beacon endpoint factory sync --watch`, or run one
Factory Droid OTLP is controlled by Droid's launch environment. Set `OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318` through MDM or another customer-owned launch policy.
-Asymptote discovers Droid and validates the endpoint, but it does not mutate shell profiles for Droid. Restart Factory Droid after installing or removing hooks so new sessions pick up the updated hook configuration.
+Beacon discovers Droid and validates the endpoint, but it does not mutate shell profiles for Droid. Restart Factory Droid after installing or removing hooks so new sessions pick up the updated hook configuration.
## Related
diff --git a/docs/runtimes/gemini-cli.mdx b/docs/runtimes/gemini-cli.mdx
index 6972185b..f0cc44eb 100644
--- a/docs/runtimes/gemini-cli.mdx
+++ b/docs/runtimes/gemini-cli.mdx
@@ -1,11 +1,11 @@
---
title: "Gemini CLI"
-description: "Asymptote support details for Gemini CLI endpoint telemetry"
+description: "Beacon support details for Gemini CLI endpoint telemetry"
---
## Runtime overview
-Asymptote supports Gemini CLI through opt-in local OTLP logs, traces, and metrics.
+Beacon supports Gemini CLI through opt-in local OTLP logs, traces, and metrics.
## Prerequisites
@@ -14,24 +14,24 @@ Before enabling Gemini CLI telemetry, make sure:
- Gemini CLI is installed and available as the `gemini` executable for the user or managed endpoint.
- `beacon endpoint install` has run so the local collector, endpoint config, and runtime log path exist.
- The install explicitly includes Gemini, for example `beacon endpoint install --harness claude,codex,gemini`.
-- No project settings or `GEMINI_TELEMETRY_*` environment variables override the user-level Asymptote settings you expect to use.
+- No project settings or `GEMINI_TELEMETRY_*` environment variables override the user-level Beacon settings you expect to use.
- Your team has reviewed content handling and destination access for prompt telemetry.
## Collection path
-Gemini CLI exports local OpenTelemetry data to Asymptote's localhost collector when the `gemini` endpoint harness is enabled. Asymptote maps Gemini prompts, tool calls, MCP activity, file operations, and approval-related events into normalized endpoint events.
+Gemini CLI exports local OpenTelemetry data to Beacon's localhost collector when the `gemini` endpoint harness is enabled. Beacon maps Gemini prompts, tool calls, MCP activity, file operations, and approval-related events into normalized endpoint events.
## Discovery and status
-Asymptote detects Gemini CLI through the `gemini` executable and `~/.gemini/settings.json`. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Gemini CLI is present and configured.
+Beacon detects Gemini CLI through the `gemini` executable and `~/.gemini/settings.json`. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Gemini CLI is present and configured.
## Install or configuration support
-Gemini CLI telemetry is opt-in. Run `beacon endpoint install --harness claude,codex,gemini` when you want Asymptote to manage Gemini telemetry settings.
+Gemini CLI telemetry is opt-in. Run `beacon endpoint install --harness claude,codex,gemini` when you want Beacon to manage Gemini telemetry settings.
-Asymptote writes local OTLP settings to `~/.gemini/settings.json`, sets `target` to `local`, uses OTLP gRPC, enables collector mode, and removes `outfile` so telemetry flows to Asymptote.
+Beacon writes local OTLP settings to `~/.gemini/settings.json`, sets `target` to `local`, uses OTLP gRPC, enables collector mode, and removes `outfile` so telemetry flows to Beacon.
-Gemini CLI is not currently configured through Asymptote's hook adapter.
+Gemini CLI is not currently configured through Beacon's hook adapter.
## Telemetry coverage
@@ -44,9 +44,9 @@ Gemini CLI is not currently configured through Asymptote's hook adapter.
## Deployment notes
-Project settings or `GEMINI_TELEMETRY_*` environment variables may override Asymptote's user-level Gemini config.
+Project settings or `GEMINI_TELEMETRY_*` environment variables may override Beacon's user-level Gemini config.
-For enterprise rollouts, add `gemini` to the endpoint harness list, for example `claude,codex,gemini`, when you want Asymptote to manage `~/.gemini/settings.json` for local OTLP collection.
+For enterprise rollouts, add `gemini` to the endpoint harness list, for example `claude,codex,gemini`, when you want Beacon to manage `~/.gemini/settings.json` for local OTLP collection.
If a system collector is running while the CLI is reading the default per-user log, `beacon endpoint status` and the local dashboard surface a runtime-log source warning so you can tell where OTLP events are being written.
@@ -57,6 +57,6 @@ If a system collector is running while the CLI is reading the default per-user l
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures supported runtimes.
+ See how Beacon discovers and configures supported runtimes.
</Card>
</Columns>
diff --git a/docs/runtimes/github-copilot-cli.mdx b/docs/runtimes/github-copilot-cli.mdx
index e5680cdc..2a9e0459 100644
--- a/docs/runtimes/github-copilot-cli.mdx
+++ b/docs/runtimes/github-copilot-cli.mdx
@@ -1,11 +1,11 @@
---
title: "GitHub Copilot CLI"
-description: "Asymptote support details for GitHub Copilot CLI endpoint telemetry"
+description: "Beacon support details for GitHub Copilot CLI endpoint telemetry"
---
## Runtime overview
-Asymptote supports GitHub Copilot CLI through MDM-managed OpenTelemetry export to the local OTLP HTTP receiver.
+Beacon supports GitHub Copilot CLI through MDM-managed OpenTelemetry export to the local OTLP HTTP receiver.
## Prerequisites
@@ -19,21 +19,21 @@ Before enabling GitHub Copilot CLI telemetry, make sure:
## Collection path
-GitHub Copilot CLI exports OTLP HTTP telemetry to Asymptote's local collector. Asymptote normalizes Copilot spans into endpoint events for prompt submission, session activity, tool invocation, and approval-like permission activity.
+GitHub Copilot CLI exports OTLP HTTP telemetry to Beacon's local collector. Beacon normalizes Copilot spans into endpoint events for prompt submission, session activity, tool invocation, and approval-like permission activity.
Copilot CLI metrics are filtered from the local runtime JSONL log by default so endpoint timelines stay focused on user and agent activity. Use `--include-runtime-metrics` during install or repair only when you need low-level Copilot metrics for troubleshooting.
## Discovery and status
-Asymptote detects GitHub Copilot CLI through the `copilot` executable or `~/.copilot/config.json`. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Copilot CLI is present and exporting to Asymptote's local OTLP HTTP receiver.
+Beacon detects GitHub Copilot CLI through the `copilot` executable or `~/.copilot/config.json`. Use `beacon endpoint discover` or `beacon endpoint status` to confirm that Copilot CLI is present and exporting to Beacon's local OTLP HTTP receiver.
-Asymptote reports Copilot CLI telemetry as configured only when `COPILOT_OTEL_ENABLED` is truthy and the effective OTLP endpoint points to `localhost` or `127.0.0.1`. If `COPILOT_OTEL_FILE_EXPORTER_PATH` is configured, Asymptote reports Copilot as misconfigured because the file exporter bypasses the local OTLP collector.
+Beacon reports Copilot CLI telemetry as configured only when `COPILOT_OTEL_ENABLED` is truthy and the effective OTLP endpoint points to `localhost` or `127.0.0.1`. If `COPILOT_OTEL_FILE_EXPORTER_PATH` is configured, Beacon reports Copilot as misconfigured because the file exporter bypasses the local OTLP collector.
## Install or configuration support
-`beacon endpoint install` prepares the collector, endpoint config, and runtime log paths. Copilot CLI telemetry is configured outside Asymptote through MDM, shell profile management, or another customer-owned launch policy.
+`beacon endpoint install` prepares the collector, endpoint config, and runtime log paths. Copilot CLI telemetry is configured outside Beacon through MDM, shell profile management, or another customer-owned launch policy.
-Do not add Copilot CLI to the `--harness` list. If `copilot`, `copilot_cli`, or `github_copilot` is passed to `beacon endpoint install --harness` or `beacon endpoint repair --harness`, Asymptote reports that Copilot CLI telemetry is MDM-managed instead of writing Copilot configuration directly.
+Do not add Copilot CLI to the `--harness` list. If `copilot`, `copilot_cli`, or `github_copilot` is passed to `beacon endpoint install --harness` or `beacon endpoint repair --harness`, Beacon reports that Copilot CLI telemetry is MDM-managed instead of writing Copilot configuration directly.
Configure Copilot CLI's launch environment to export to the local OTLP HTTP receiver:
@@ -61,9 +61,9 @@ For a one-command local validation flow, see [Test GitHub Copilot CLI telemetry]
## Deployment notes
-Copilot CLI currently exports OTLP over HTTP, not gRPC. Point it at Asymptote's HTTP receiver, usually `http://127.0.0.1:4318`, or the custom `--otlp-http-port` used by your endpoint install.
+Copilot CLI currently exports OTLP over HTTP, not gRPC. Point it at Beacon's HTTP receiver, usually `http://127.0.0.1:4318`, or the custom `--otlp-http-port` used by your endpoint install.
-Asymptote validates the effective Copilot environment but does not write Copilot shell profiles or `~/.copilot/config.json`. Keep Copilot CLI outside the default Asymptote harness list, and deploy its environment settings with the same MDM or shell-management mechanism you use to launch Copilot.
+Beacon validates the effective Copilot environment but does not write Copilot shell profiles or `~/.copilot/config.json`. Keep Copilot CLI outside the default Beacon harness list, and deploy its environment settings with the same MDM or shell-management mechanism you use to launch Copilot.
## Related
diff --git a/docs/runtimes/goose.mdx b/docs/runtimes/goose.mdx
index da67d3b3..fd62f54b 100644
--- a/docs/runtimes/goose.mdx
+++ b/docs/runtimes/goose.mdx
@@ -1,11 +1,11 @@
---
title: "goose"
-description: "Asymptote support details for goose endpoint telemetry"
+description: "Beacon support details for goose endpoint telemetry"
---
## Runtime overview
-Asymptote supports goose — the open-source agent from Block — through **two** collection paths, and both are wanted on the same machine:
+Beacon supports goose — the open-source agent from Block — through **two** collection paths, and both are wanted on the same machine:
```bash
beacon endpoint hooks install --harness goose # plugin hooks
@@ -34,7 +34,7 @@ Before enabling goose telemetry, make sure:
## Collection path 1: plugin hooks
-goose discovers plugins as the **immediate subdirectories** of its plugins directory, names each plugin after its directory, and loads `<plugin-root>/hooks/hooks.json` from every plugin that is enabled. So Asymptote owns a **directory** rather than a file, and never reads or writes any other plugin beside it.
+goose discovers plugins as the **immediate subdirectories** of its plugins directory, names each plugin after its directory, and loads `<plugin-root>/hooks/hooks.json` from every plugin that is enabled. So Beacon owns a **directory** rather than a file, and never reads or writes any other plugin beside it.
| Scope | Directory | Covers |
|-------|-----------|--------|
@@ -44,7 +44,7 @@ goose discovers plugins as the **immediate subdirectories** of its plugins direc
`$GOOSE_PATH_ROOT` relocates the user-scope location when it is set to an absolute path, matching how goose resolves its own directories. A relative value is ignored, exactly as goose ignores it.
<Warning>
-**The two scopes replace each other; they do not add up.** goose deduplicates plugins by **name**, taking project scope first — so a project-scope `beacon-endpoint` plugin replaces the user-scope one for sessions in that directory rather than running alongside it. Asymptote installs the same directory name at both scopes deliberately: an operator who installs at both gets **one** registration, not two copies of every event.
+**The two scopes replace each other; they do not add up.** goose deduplicates plugins by **name**, taking project scope first — so a project-scope `beacon-endpoint` plugin replaces the user-scope one for sessions in that directory rather than running alongside it. Beacon installs the same directory name at both scopes deliberately: an operator who installs at both gets **one** registration, not two copies of every event.
This is the opposite of [Kiro](/runtimes/kiro), where hook files merge across scopes, and it matches [OpenHands](/runtimes/openhands), where a project file shadows the user one.
</Warning>
@@ -54,12 +54,12 @@ This is the opposite of [Kiro](/runtimes/kiro), where hook files merge across sc
<Note>
**`.agents/plugins` is a shared directory, not goose's namespace.** It is the [Open Plugins](https://open-plugins.com) convention, so another agent implementing that specification would also discover this plugin and run its hooks — and those events would be attributed to goose, because nothing in a hook payload says which host invoked it. goose sets no distinguishing variable and the event schema has no field for the question.
-This is a stated limitation with no fix on Asymptote's side. It costs nothing today, because goose is the only supported runtime that reads this directory.
+This is a stated limitation with no fix on Beacon's side. It costs nothing today, because goose is the only supported runtime that reads this directory.
</Note>
### Registered events
-goose exposes twelve lifecycle events. Asymptote registers seven, and the five it leaves out are covered under [Known gaps](#known-gaps).
+goose exposes twelve lifecycle events. Beacon registers seven, and the five it leaves out are covered under [Known gaps](#known-gaps).
| goose event | Adapter subcommand | Timeout |
|-------------|--------------------|---------|
@@ -72,32 +72,32 @@ goose exposes twelve lifecycle events. Asymptote registers seven, and the five i
| `SessionEnd` | `session-end` | 45 s |
<Warning>
-**goose hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a hooks file that looks similar. goose's own default is 30 seconds; Asymptote writes explicit values because these are ceilings on a hang, not budgets — and because goose **holds the turn** for a blocking hook, so the value on `Stop` is the ceiling on a stalled turn.
+**goose hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a hooks file that looks similar. goose's own default is 30 seconds; Beacon writes explicit values because these are ceilings on a hang, not budgets — and because goose **holds the turn** for a blocking hook, so the value on `Stop` is the ceiling on a stalled turn.
</Warning>
`PostToolUse` and `PostToolUseFailure` share the `post-tool` subcommand and are two separate registrations. goose has no single post-tool event: it sends one or the other, with **otherwise identical payloads**, and the event name is the only thing that distinguishes a write that landed from one that did not.
-Asymptote's hooks carry no `matcher`. The field is a regex tested against goose's `matcher_context`, and that is not a tool name on every event — on `UserPromptSubmit` it is **the prompt text**. A matcher that looked like a harmless `.*` would be a regex run over every prompt, and a narrower one would silently drop prompts that did not match it. Omitting it means always-match, which is what a telemetry hook wants on all seven.
+Beacon's hooks carry no `matcher`. The field is a regex tested against goose's `matcher_context`, and that is not a tool name on every event — on `UserPromptSubmit` it is **the prompt text**. A matcher that looked like a harmless `.*` would be a regex run over every prompt, and a narrower one would silently drop prompts that did not match it. Omitting it means always-match, which is what a telemetry hook wants on all seven.
### The hook environment
-goose runs a `command` action through `sh -c`, exports `PLUGIN_ROOT`, and sends the event as JSON on stdin. Asymptote passes the endpoint log and config locations to `beacon-hooks` as `--log` and `--config` flags rather than through the environment, so a hook finds them wherever it runs.
+goose runs a `command` action through `sh -c`, exports `PLUGIN_ROOT`, and sends the event as JSON on stdin. Beacon passes the endpoint log and config locations to `beacon-hooks` as `--log` and `--config` flags rather than through the environment, so a hook finds them wherever it runs.
<Warning>
**On goose, a hook's stdout is judged, not ignored.** `PreToolUse` and `Stop` run through goose's blocking path, which **classifies** what the hook wrote: a hook that exits 0 with stdout carrying no recognized decision is classified as a *failed hook*. goose logs one per tool call and per turn, and on a rule configured `on_failure: block` it **denies the tool call outright**.
-The no-op `{}` that every other runtime reads as "no opinion" lands there, and so does `{"permission":"allow"}` — goose reads `decision`, and accepts only `allow` and `block`. Asymptote therefore answers `{"decision":"allow"}` on both blocking events.
+The no-op `{}` that every other runtime reads as "no opinion" lands there, and so does `{"permission":"allow"}` — goose reads `decision`, and accepts only `allow` and `block`. Beacon therefore answers `{"decision":"allow"}` on both blocking events.
-**That allow approves nothing.** goose's hook chain is a plugin-policy layer inside `ToolExecutionOperation`, and the pipeline runs `ToolApprovalOperation` *before* it — so the operator's decision has already been made by the time a hook is consulted. It means "this policy hook does not object", and reaches no permission judge. This is the opposite of [Qwen Code](/runtimes/qwen-code), where answering "allow" would disarm the user's own prompts and Asymptote therefore answers with an empty object.
+**That allow approves nothing.** goose's hook chain is a plugin-policy layer inside `ToolExecutionOperation`, and the pipeline runs `ToolApprovalOperation` *before* it — so the operator's decision has already been made by the time a hook is consulted. It means "this policy hook does not object", and reaches no permission judge. This is the opposite of [Qwen Code](/runtimes/qwen-code), where answering "allow" would disarm the user's own prompts and Beacon therefore answers with an empty object.
</Warning>
-### Asymptote owns one plugin directory and nothing else
+### Beacon owns one plugin directory and nothing else
-Because goose loads every plugin it discovers, an install is additive by construction: your own plugins keep working, untouched, and Asymptote never parses them.
+Because goose loads every plugin it discovers, an install is additive by construction: your own plugins keep working, untouched, and Beacon never parses them.
-The one thing Asymptote claims is the directory name `beacon-endpoint`. If its `hooks/hooks.json` already holds a hook Asymptote did not write, both install and uninstall **refuse** with an error naming the hook rather than overwriting or deleting it — move that hook into a plugin of its own and run the install again. A file goose itself could not parse is overwritten, since there are no live hooks in it to protect.
+The one thing Beacon claims is the directory name `beacon-endpoint`. If its `hooks/hooks.json` already holds a hook Beacon did not write, both install and uninstall **refuse** with an error naming the hook rather than overwriting or deleting it — move that hook into a plugin of its own and run the install again. A file goose itself could not parse is overwritten, since there are no live hooks in it to protect.
-Re-running the install rewrites the file rather than appending to it, so a repair does not end with each event registered twice. Uninstall removes the file **and the plugin directory Asymptote created**, because a plugin directory with no hooks file is still a plugin goose discovers and records in `config.yaml`. A directory you put something else into is left alone.
+Re-running the install rewrites the file rather than appending to it, so a repair does not end with each event registered twice. Uninstall removes the file **and the plugin directory Beacon created**, because a plugin directory with no hooks file is still a plugin goose discovers and records in `config.yaml`. A directory you put something else into is left alone.
## Collection path 2: OpenTelemetry export
@@ -116,7 +116,7 @@ This path is what carries `gen_ai.usage.*` — including cache reads and writes
### Your config.yaml is edited, not rewritten
-`config.yaml` is a file you write by hand — your provider, your model, your extensions, your permissions. Asymptote changes two keys and **preserves comments, key order, values, nesting and two-space indentation**, and backs the file up before writing. A config Asymptote cannot parse is refused rather than overwritten.
+`config.yaml` is a file you write by hand — your provider, your model, your extensions, your permissions. Beacon changes two keys and **preserves comments, key order, values, nesting and two-space indentation**, and backs the file up before writing. A config Beacon cannot parse is refused rather than overwritten.
The one thing not preserved is **blank lines between top-level keys**, which the YAML library cannot retain. That is the reason for the backup.
@@ -139,7 +139,7 @@ beacon endpoint hooks status --harness goose
beacon endpoint status --json | jq '.harnesses[] | select(.name == "goose")'
```
-goose reports as the `goose` harness. Hook events carry `harness.collection_method=hook` — the events, the payload shapes and the hooks schema are all goose's, and Asymptote ships no plugin source goose loads and executes — while OTLP events carry `harness.collection_method=otlp`.
+goose reports as the `goose` harness. Hook events carry `harness.collection_method=hook` — the events, the payload shapes and the hooks schema are all goose's, and Beacon ships no plugin source goose loads and executes — while OTLP events carry `harness.collection_method=otlp`.
<Note>
**A hooks file on disk is a registration, not a guarantee.** goose lets you disable a plugin from the `plugins` map in `config.yaml` or from `disabledPlugins` in a `settings.json` at any of three scopes, and a disabled plugin keeps its hooks file. `beacon endpoint hooks status` reports the registration, which is the narrower claim it can actually make — answering the rest would mean reimplementing goose's precedence across four files it does not version. Run one session and check the log to confirm events are arriving.
@@ -211,7 +211,7 @@ An edit whose `before` and `after` are identical produces no diff, for the same
## Approvals and enforcement
-**Asymptote records no approval decisions for goose, and does not synthesize any.**
+**Beacon records no approval decisions for goose, and does not synthesize any.**
goose genuinely does ask the operator — `ToolApprovalOperation` runs the permission judge, marks calls that need a person as not executable, and stops the turn for an answer — and exposes none of that to a hook. Its `HookEvent` set has no approval event at all, and `PreToolUse` fires identically whether the call was pre-approved by `goose_mode`, waved through, or already confirmed by somebody. An `approval.allowed` derived from it would claim a decision in exactly the cases where none was made. This is the same call already settled for [Cline](/runtimes/cline), [Pi](/runtimes/pi), [OpenHands](/runtimes/openhands), [Kiro](/runtimes/kiro), and [fx](/runtimes/vercel-fx).
@@ -231,15 +231,15 @@ The reason rides along because goose puts it in front of both the operator and t
goose content is handled like every other runtime. Prompts, tool arguments, command lines, paths, and diffs are retained in local or customer-controlled logs, with local secret redaction and per-string limits applied before writing, and a hash and byte count on each content-bearing event. Events over the 64 KiB limit drop raw and retained content, preserve stable metadata, and set `field_truncated`.
-The OTLP path carries message content only when `OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=true` is set in goose's environment. That is goose's own opt-in and is not written by Asymptote — it cannot be: goose reads it from the environment only, never from `config.yaml`.
+The OTLP path carries message content only when `OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=true` is set in goose's environment. That is goose's own opt-in and is not written by Beacon — it cannot be: goose reads it from the environment only, never from `config.yaml`.
## Known gaps
- **No tool output of any kind.** goose's hook context has a `tool_output` field and **no emission site in the runtime populates it**. So there are no command exit codes, no command output, no file-read contents and no MCP results anywhere on the hook path. A command is recorded as executed, with its command line, and nothing about how it went. This is the largest gap on this runtime, and closing it needs a change in goose.
-- **No approval decisions.** goose exposes no approval event, and Asymptote does not synthesize one from `PreToolUse`. Approval rules and dashboards will show nothing for this runtime.
-- **No reported cost.** goose reports token counts and not a price, so `gen_ai.usage.cost_usd` is empty. Asymptote does not derive cost from local pricing tables for any runtime.
+- **No approval decisions.** goose exposes no approval event, and Beacon does not synthesize one from `PreToolUse`. Approval rules and dashboards will show nothing for this runtime.
+- **No reported cost.** goose reports token counts and not a price, so `gen_ai.usage.cost_usd` is empty. Beacon does not derive cost from local pricing tables for any runtime.
- **Token usage needs the OTLP path.** Usage arrives on `chat` spans, so a hooks-only install reports none. That is expected rather than a fault, and `beacon token-usage` classifies goose accordingly.
-- **No working directory on three events.** goose omits it on `SessionStart` and `SessionEnd` when they come from the agent rather than the CLI session loop, and on a `UserPromptSubmit` raised by steering mid-turn. Those events carry no `session.working_directory` and no repository. Asymptote deliberately does **not** fall back to the hook process's own directory: goose runs hooks with `sh -c` inheriting its own cwd, which is the application bundle under the desktop app — a path that looks like a repository and resolves to nothing. Every tool event does carry it.
+- **No working directory on three events.** goose omits it on `SessionStart` and `SessionEnd` when they come from the agent rather than the CLI session loop, and on a `UserPromptSubmit` raised by steering mid-turn. Those events carry no `session.working_directory` and no repository. Beacon deliberately does **not** fall back to the hook process's own directory: goose runs hooks with `sh -c` inheriting its own cwd, which is the application bundle under the desktop app — a path that looks like a repository and resolves to nothing. Every tool event does carry it.
- **No duplicate shell and file events.** `BeforeShellExecution`, `AfterShellExecution`, `BeforeReadFile` and `AfterFileEdit` are deliberately not subscribed to. Each fires alongside `PreToolUse` or `PostToolUse` for the **same call**, with the same tool name and arguments and — the part that makes them worse than redundant — **no tool call id at all**. Subscribing would record every shell command and file edit twice, with the second copy uncorrelatable.
- **No policy-decision events.** `PreToolUseResult` reports what the `PreToolUse` hook chain decided, which plugin denied, and why. It is real signal with no duplicate elsewhere, but it fires once per tool call to report an outcome that is almost always "allow", so subscribing as-is would double event volume. It is deferred rather than declined.
- **No compaction or subagent events.** goose emits neither on a hook.
@@ -279,6 +279,6 @@ If goose token usage or model data is missing:
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
</Columns>
diff --git a/docs/runtimes/grok-build.mdx b/docs/runtimes/grok-build.mdx
index c9930085..2fba3e00 100644
--- a/docs/runtimes/grok-build.mdx
+++ b/docs/runtimes/grok-build.mdx
@@ -1,11 +1,11 @@
---
title: "Grok Build"
-description: "Asymptote support details for Grok Build endpoint telemetry"
+description: "Beacon support details for Grok Build endpoint telemetry"
---
## Runtime overview
-Asymptote supports Grok Build through native hook payloads sent to `beacon-hooks`.
+Beacon supports Grok Build through native hook payloads sent to `beacon-hooks`.
## Prerequisites
@@ -13,7 +13,7 @@ Before enabling Grok Build hooks, make sure:
- Grok Build is installed for the user or available in the project where hooks will run.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote hooks are installed with `beacon endpoint hooks install --harness grok`.
+- Beacon hooks are installed with `beacon endpoint hooks install --harness grok`.
- Project-level hooks are trusted with `/hooks-trust` in Grok before you expect them to execute.
- Grok is restarted after hook install or removal so new sessions load the updated hook file.
@@ -21,12 +21,12 @@ Before enabling Grok Build hooks, make sure:
Grok Build has two local collection paths:
-- Live hooks: Grok invokes Asymptote's hook adapter from Asymptote's owned hook file. The adapter writes normalized endpoint events to the configured runtime JSONL log and can participate in Beacon's external policy seam.
+- Live hooks: Grok invokes Beacon's hook adapter from Beacon's owned hook file. The adapter writes normalized endpoint events to the configured runtime JSONL log and can participate in Beacon's external policy seam.
- Session sync: `beacon endpoint grok sync` reads committed sessions under `~/.grok/sessions/<url-escaped-working-directory>/<session-id>` and writes endpoint events marked `harness.collection_method=poll`. This backfills historical or unhooked sessions after Grok has written them, so it cannot hold, allow, or deny a tool call.
## Discovery and status
-Asymptote checks for its managed Grok hook file at `~/.grok/hooks/beacon-endpoint.json` for user-level installs or `./.grok/hooks/beacon-endpoint.json` for project-level installs.
+Beacon checks for its managed Grok hook file at `~/.grok/hooks/beacon-endpoint.json` for user-level installs or `./.grok/hooks/beacon-endpoint.json` for project-level installs.
Use `beacon endpoint hooks status --harness grok` to inspect Grok Build hook status. Use `beacon endpoint grok status` to inspect committed local sessions and whether Beacon has synced them.
@@ -65,7 +65,7 @@ beacon endpoint grok sync --print
| Prompt telemetry | Supported through `UserPromptSubmit` hooks and session sync |
| Command, tool, and file telemetry | Supported for live hook payloads and committed session records. Session sync reads `chat_history.jsonl`, `events.jsonl`, `summary.json`, `prompt_context.json`, and terminal logs where present |
| Approval telemetry | Live hooks can observe and enforce at pre-tool time; session sync can report committed Grok permission request/resolution records after the fact |
-| Session lifecycle | `session.started` only. Grok's `turn_ended` record ends a turn, not a session — the next prompt appends to the same session — so session sync records it as `session.context` carrying the turn number and outcome. Grok exposes no session-end record, so Asymptote writes no `session.ended` for this runtime rather than inventing one |
+| Session lifecycle | `session.started` only. Grok's `turn_ended` record ends a turn, not a session — the next prompt appends to the same session — so session sync records it as `session.context` carrying the turn number and outcome. Grok exposes no session-end record, so Beacon writes no `session.ended` for this runtime rather than inventing one |
| Local JSONL and dashboard | Supported |
| MDM deployment | Supported for the endpoint agent. Grok hooks are installed separately in the logged-in user's context or project context |
diff --git a/docs/runtimes/hermes-agent.mdx b/docs/runtimes/hermes-agent.mdx
index 577e18e1..f3ac94c6 100644
--- a/docs/runtimes/hermes-agent.mdx
+++ b/docs/runtimes/hermes-agent.mdx
@@ -1,11 +1,11 @@
---
title: "Hermes Agent"
-description: "Asymptote support details for Hermes Agent endpoint telemetry"
+description: "Beacon support details for Hermes Agent endpoint telemetry"
---
## Runtime overview
-Asymptote supports Hermes Agent through shell hook payloads sent to `beacon-hooks`, with local session database sync for historical backfill.
+Beacon supports Hermes Agent through shell hook payloads sent to `beacon-hooks`, with local session database sync for historical backfill.
## Prerequisites
@@ -13,15 +13,15 @@ Before enabling Hermes Agent hooks, make sure:
- Hermes Agent is installed for the user or `~/.hermes/config.yaml` exists.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote hooks are installed with `beacon endpoint hooks install --harness hermes`.
+- Beacon hooks are installed with `beacon endpoint hooks install --harness hermes`.
- Hermes hook consent is handled for the session, especially in non-interactive gateway, cron, or CI runs.
- Hermes is restarted after hook install or removal so new sessions load the updated config.
## Collection path
-Asymptote merges shell-hook entries into `~/.hermes/config.yaml`. Hermes invokes Asymptote's hook adapter for supported lifecycle, prompt, tool, approval, and subagent events, and the adapter writes normalized endpoint events to the configured runtime JSONL log.
+Beacon merges shell-hook entries into `~/.hermes/config.yaml`. Hermes invokes Beacon's hook adapter for supported lifecycle, prompt, tool, approval, and subagent events, and the adapter writes normalized endpoint events to the configured runtime JSONL log.
-Asymptote can also read Hermes Agent's committed SQLite session store:
+Beacon can also read Hermes Agent's committed SQLite session store:
```bash title="Sync Hermes Agent sessions"
beacon endpoint hermes status
@@ -32,7 +32,7 @@ The sync path reads `~/.hermes/state.db` locally and offline. It writes mapped e
## Discovery and status
-Asymptote detects Hermes through the `hermes` executable or a local `~/.hermes` directory, then checks `~/.hermes/config.yaml` for Asymptote-managed commands, identified by the endpoint settings flags (`--log`, `--config`, `--cli`) or a legacy `BEACON_ENDPOINT_MODE=1` prefix, together with `--platform hermes`.
+Beacon detects Hermes through the `hermes` executable or a local `~/.hermes` directory, then checks `~/.hermes/config.yaml` for Beacon-managed commands, identified by the endpoint settings flags (`--log`, `--config`, `--cli`) or a legacy `BEACON_ENDPOINT_MODE=1` prefix, together with `--platform hermes`.
Use `beacon endpoint hooks status --harness hermes` to inspect Hermes Agent hook status. Use `beacon endpoint hermes status` to inspect committed local sessions and how much Beacon has synced.
@@ -68,7 +68,7 @@ For scheduled collection, run `beacon endpoint hermes sync --watch`, or run one-
Hermes prompts for first-use consent for each `(event, command)` hook pair. For non-interactive gateway, cron, or CI runs, set `HERMES_ACCEPT_HOOKS=1`, start Hermes with `--accept-hooks`, or configure `hooks_auto_accept: true` in `~/.hermes/config.yaml`.
-Asymptote preserves existing Hermes settings and non-Asymptote hooks when installing or uninstalling Hermes telemetry. It replaces only Asymptote-managed Hermes hook commands.
+Beacon preserves existing Hermes settings and non-Beacon hooks when installing or uninstalling Hermes telemetry. It replaces only Beacon-managed Hermes hook commands.
Restart Hermes after installing or removing hooks so new sessions pick up the updated configuration.
diff --git a/docs/runtimes/index.mdx b/docs/runtimes/index.mdx
index 7990b0c4..6474a790 100644
--- a/docs/runtimes/index.mdx
+++ b/docs/runtimes/index.mdx
@@ -1,15 +1,15 @@
---
title: "Runtime Surface Overview"
-description: "Asymptote agent harness support overview and runtime-specific pages"
+description: "Beacon agent harness support overview and runtime-specific pages"
---
## Overview
-Asymptote supports multiple [runtime surfaces](/concepts/core-concepts#runtime-surface) because each [agent harness](/concepts/core-concepts#agent-harness) exposes telemetry differently. The runtime support model applies to both Asymptote Open Source and Asymptote Managed: Open Source collects and normalizes supported local, CI, and cloud-agent telemetry, while Managed adds hosted ingest, visibility, and governance on top of the same surfaces.
+Beacon supports multiple [runtime surfaces](/concepts/core-concepts#runtime-surface) because each [agent harness](/concepts/core-concepts#agent-harness) exposes telemetry differently. Beacon collects and normalizes supported local, CI, and cloud-agent telemetry, while Beacon Managed adds hosted ingest, visibility, and governance on top of the same surfaces.
These integrations are grouped by where the agent runs and how telemetry is collected:
-- **Local**: Agent harnesses running on an endpoint write telemetry to Asymptote's local collector, hook adapter, plugin, or gateway path.
+- **Local**: Agent harnesses running on an endpoint write telemetry to Beacon's local collector, hook adapter, plugin, or gateway path.
- **Browser chat**: An optional Chrome extension reads the chat streams of supported sites in the browser and posts them to the same local collector.
- **[CI](/concepts/core-concepts#ci-telemetry)**: Ephemeral CI jobs use a temporary collector and write normalized runtime JSONL as a build artifact or upload target instead of installing a persistent endpoint service.
- **[Cloud](/concepts/core-concepts#cloud-agent-telemetry)**: Provider-managed cloud agents can write session telemetry from the cloud sandbox to customer-managed storage, while [SDK integrations](/concepts/core-concepts#observe-sdk) instrument agent applications that run in servers, serverless functions, workers, and hosted agent platforms.
@@ -116,15 +116,15 @@ MDM assets, meaning Jamf Pro Extension Attributes, Fleet osquery queries, and Ri
| Cursor | Install hooks with `beacon endpoint hooks install --harness cursor`. To backfill committed local sessions, schedule `beacon endpoint cursor sync` in the logged-in user's context or leave `--watch` running. |
| Cline | Install the managed plugin with `beacon endpoint hooks install --harness cline`. To backfill committed local tasks and sessions, schedule `beacon endpoint cline sync` in the logged-in user's context or leave `--watch` running. |
| Codex CLI | `beacon endpoint install` configures local OTLP export. To backfill committed sessions, schedule `beacon endpoint codex sync` in the logged-in user's context or leave `--watch` running. |
-| Gemini CLI | Opt in by adding `gemini` to the endpoint harness list, for example `claude,codex,gemini`. Asymptote can then manage `~/.gemini/settings.json` for local OTLP collection. |
+| Gemini CLI | Opt in by adding `gemini` to the endpoint harness list, for example `claude,codex,gemini`. Beacon can then manage `~/.gemini/settings.json` for local OTLP collection. |
| fx (Vercel Labs) | Nothing to configure in fx. Schedule [`beacon endpoint fx sync`](/cli/endpoint-fx) in the logged-in user's context, or leave `--watch` running, so committed sessions keep reaching the runtime log. Nothing sweeps on its own. |
| OpenCode | Install the managed plugin for live telemetry with `beacon endpoint hooks install --harness opencode`. To backfill committed local sessions, schedule [`beacon endpoint opencode sync`](/cli/endpoint-opencode) in the logged-in user's context or leave `--watch` running. |
| Pi | Install the managed extension for live telemetry with `beacon endpoint hooks install --harness pi`. To backfill committed local sessions, schedule [`beacon endpoint pi sync`](/cli/endpoint-pi) in the logged-in user's context or leave `--watch` running. |
-| GitHub Copilot CLI | Configure launch environment through MDM or customer policy: `COPILOT_OTEL_ENABLED=true` and `OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318`. Asymptote validates the endpoint but does not edit shell profiles or launch environments. |
-| Factory Droid | Configure launch environment with `OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318`. Asymptote discovers the runtime and validates the endpoint but does not edit shell profiles or launch environments. To backfill committed sessions, schedule `beacon endpoint factory sync` in the logged-in user's context or leave `--watch` running. |
+| GitHub Copilot CLI | Configure launch environment through MDM or customer policy: `COPILOT_OTEL_ENABLED=true` and `OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318`. Beacon validates the endpoint but does not edit shell profiles or launch environments. |
+| Factory Droid | Configure launch environment with `OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318`. Beacon discovers the runtime and validates the endpoint but does not edit shell profiles or launch environments. To backfill committed sessions, schedule `beacon endpoint factory sync` in the logged-in user's context or leave `--watch` running. |
| Grok Build | Install hooks with `beacon endpoint hooks install --harness grok`. To backfill committed local sessions, schedule `beacon endpoint grok sync` in the logged-in user's context or leave `--watch` running. |
| Hermes Agent | Install hooks with `beacon endpoint hooks install --harness hermes`. To backfill committed sessions from `~/.hermes/state.db`, schedule `beacon endpoint hermes sync` in the logged-in user's context or leave `--watch` running. |
-| OpenClaw Gateway | Install the managed plugin in the account the gateway runs as with `beacon endpoint hooks install --harness openclaw`, then grant `plugins.entries.beacon-endpoint.hooks.allowConversationAccess` in OpenClaw's own config so token usage is collected. For the gateway's OTLP export, use [`beacon endpoint integrations openclaw`](/cli/openclaw) to print local settings and validate events; Asymptote never writes OpenClaw's config. To backfill committed session files, schedule `beacon endpoint integrations openclaw sessions sync` in the gateway account or leave `--watch` running. |
+| OpenClaw Gateway | Install the managed plugin in the account the gateway runs as with `beacon endpoint hooks install --harness openclaw`, then grant `plugins.entries.beacon-endpoint.hooks.allowConversationAccess` in OpenClaw's own config so token usage is collected. For the gateway's OTLP export, use [`beacon endpoint integrations openclaw`](/cli/openclaw) to print local settings and validate events; Beacon never writes OpenClaw's config. To backfill committed session files, schedule `beacon endpoint integrations openclaw sessions sync` in the gateway account or leave `--watch` running. |
| Prime Agent | Install the managed extension for live telemetry with `beacon endpoint hooks install --harness prime`. To backfill committed local sessions and subagent artifacts, schedule `beacon endpoint prime sync` in the logged-in user's context or leave `--watch` running. |
Install hooks separately in the logged-in user's context when you need richer hook telemetry. This applies to Antigravity CLI, Claude Code, Cline, Codex CLI session-context hooks, Cursor, Devin CLI, Devin Desktop, Factory Droid, Grok Build, Hermes Agent, goose, Muse Code, Oh My Pi, OpenClaw Gateway, OpenCode, OpenHands, Pi, Qwen Code, and the optional VS Code hooks. Poll sync commands are also run or scheduled in the account that owns the runtime's local session store.
@@ -138,12 +138,12 @@ If a system collector is running while the CLI is reading the default per-user l
Runtime surfaces, agent harnesses, and endpoint events.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
<Card title="Hooks" icon="plug" href="/cli/hooks">
Install, inspect, and uninstall runtime hook integrations.
</Card>
<Card title="MDM deployment" icon="laptop-mobile" href="/mdm">
- Deploy Asymptote through Jamf Pro, Fleet, or another macOS MDM.
+ Deploy Beacon through Jamf Pro, Fleet, or another macOS MDM.
</Card>
</Columns>
diff --git a/docs/runtimes/kiro.mdx b/docs/runtimes/kiro.mdx
index 6c3e02c8..1b945dbb 100644
--- a/docs/runtimes/kiro.mdx
+++ b/docs/runtimes/kiro.mdx
@@ -1,11 +1,11 @@
---
title: "Kiro"
-description: "Asymptote support details for Kiro endpoint telemetry"
+description: "Beacon support details for Kiro endpoint telemetry"
---
## Runtime overview
-Asymptote supports Kiro — the AI coding agent from AWS — through its native [hooks](https://kiro.dev/docs/hooks/), sent to `beacon-hooks`.
+Beacon supports Kiro — the AI coding agent from AWS — through its native [hooks](https://kiro.dev/docs/hooks/), sent to `beacon-hooks`.
```bash
beacon endpoint hooks install --harness kiro
@@ -23,13 +23,13 @@ Kiro runs one agent harness behind the Kiro IDE, the Kiro CLI (`kiro-cli`), Kiro
Before enabling Kiro telemetry, make sure:
-- Kiro IDE 1.0 or later, or Kiro CLI 3.0 or later, is installed. The `.kiro/hooks/*.json` format was introduced in those releases; earlier versions use the `.kiro.hook` format and the embedded agent-config format, which Asymptote does not write.
+- Kiro IDE 1.0 or later, or Kiro CLI 3.0 or later, is installed. The `.kiro/hooks/*.json` format was introduced in those releases; earlier versions use the `.kiro.hook` format and the embedded agent-config format, which Beacon does not write.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
- Kiro is restarted, or a new session started, after hook install or removal — hooks are loaded when a session begins.
## Collection path
-Kiro loads **every** `.json` file in its hooks directory, so Asymptote writes **one file of its own** and never reads, rewrites, or deletes anything you put beside it.
+Kiro loads **every** `.json` file in its hooks directory, so Beacon writes **one file of its own** and never reads, rewrites, or deletes anything you put beside it.
| Scope | File | Read by |
|-------|------|---------|
@@ -46,7 +46,7 @@ Kiro loads **every** `.json` file in its hooks directory, so Asymptote writes **
### Registered events
-Kiro exposes eleven triggers. Asymptote registers five of them, and the six it leaves out are covered under [Known gaps](#known-gaps).
+Kiro exposes eleven triggers. Beacon registers five of them, and the six it leaves out are covered under [Known gaps](#known-gaps).
| Kiro trigger | Adapter subcommand | Timeout |
|--------------|--------------------|---------|
@@ -57,27 +57,27 @@ Kiro exposes eleven triggers. Asymptote registers five of them, and the six it l
| `Stop` | `stop` | 45 s |
<Warning>
-**Kiro hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a hooks file that looks similar. Kiro's own default is 60 seconds; Asymptote writes explicit lower values, because 60 seconds is a long time to hold an agent turn for a hook that finishes in milliseconds. These are ceilings on a hang, not budgets. `0` is never written: on Kiro it means *no timeout at all*, not "the default".
+**Kiro hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a hooks file that looks similar. Kiro's own default is 60 seconds; Beacon writes explicit lower values, because 60 seconds is a long time to hold an agent turn for a hook that finishes in milliseconds. These are ceilings on a hang, not budgets. `0` is never written: on Kiro it means *no timeout at all*, not "the default".
</Warning>
-Asymptote's hooks carry no `matcher`. The field is a regex whose subject depends on the trigger — a tool name on `PreToolUse` and `PostToolUse`, the prompt text on `UserPromptSubmit`, nothing at all on `SessionStart` and `Stop` — and omitting it means always-match, which is what a telemetry hook wants on all five. The `*` that means "all tools" in the IDE's tool-name field is a different thing here and is not a valid regex.
+Beacon's hooks carry no `matcher`. The field is a regex whose subject depends on the trigger — a tool name on `PreToolUse` and `PostToolUse`, the prompt text on `UserPromptSubmit`, nothing at all on `SessionStart` and `Stop` — and omitting it means always-match, which is what a telemetry hook wants on all five. The `*` that means "all tools" in the IDE's tool-name field is a different thing here and is not a valid regex.
-### Asymptote owns one filename and nothing else
+### Beacon owns one filename and nothing else
-Because Kiro loads every file in the directory, an install is additive by construction: your `lint-on-save.json` keeps working, untouched, and Asymptote never parses it.
+Because Kiro loads every file in the directory, an install is additive by construction: your `lint-on-save.json` keeps working, untouched, and Beacon never parses it.
-The one thing Asymptote does claim is the name `beacon-endpoint.json`. If a file with that name already exists and holds a hook Asymptote did not write, both install and uninstall **refuse** with an error naming the hook, rather than overwriting or deleting it — move that hook into another file in the same directory and run the install again. A file at that name that Kiro itself could not parse is overwritten, since there are no live hooks in it to protect.
+The one thing Beacon does claim is the name `beacon-endpoint.json`. If a file with that name already exists and holds a hook Beacon did not write, both install and uninstall **refuse** with an error naming the hook, rather than overwriting or deleting it — move that hook into another file in the same directory and run the install again. A file at that name that Kiro itself could not parse is overwritten, since there are no live hooks in it to protect.
Re-running the install rewrites the file rather than appending to it, so a repair does not end with each trigger registered twice.
### The hook environment
-Kiro runs a `command` action as a shell command in the project root and sends the hook event as JSON on stdin. On `UserPromptSubmit` the IDE also exports the prompt as `USER_PROMPT`; Asymptote reads the payload's `prompt` field instead, which both surfaces send.
+Kiro runs a `command` action as a shell command in the project root and sends the hook event as JSON on stdin. On `UserPromptSubmit` the IDE also exports the prompt as `USER_PROMPT`; Beacon reads the payload's `prompt` field instead, which both surfaces send.
-Asymptote passes the endpoint log and config locations to `beacon-hooks` as `--log` and `--config` flags rather than through the environment, so a hook finds them wherever it runs.
+Beacon passes the endpoint log and config locations to `beacon-hooks` as `--log` and `--config` flags rather than through the environment, so a hook finds them wherever it runs.
<Warning>
-**On Kiro, a hook's stdout is model context, not a response.** Kiro's hook contract is exit codes: on exit 0 a hook's stdout is *added to the agent's context* for `SessionStart` and `UserPromptSubmit`, and ignored for everything else. Asymptote therefore writes **nothing** to stdout on Kiro — an observing hook that emitted its usual no-op JSON object would be putting unexplained text in front of the model at the start of every session and before every prompt. Silence is a complete answer under an exit-code contract.
+**On Kiro, a hook's stdout is model context, not a response.** Kiro's hook contract is exit codes: on exit 0 a hook's stdout is *added to the agent's context* for `SessionStart` and `UserPromptSubmit`, and ignored for everything else. Beacon therefore writes **nothing** to stdout on Kiro — an observing hook that emitted its usual no-op JSON object would be putting unexplained text in front of the model at the start of every session and before every prompt. Silence is a complete answer under an exit-code contract.
</Warning>
## Discovery and status
@@ -86,7 +86,7 @@ Asymptote passes the endpoint log and config locations to `beacon-hooks` as `--l
beacon endpoint hooks status --harness kiro
```
-Kiro reports as the `kiro` harness with capability `hooks`, and every event carries `harness.collection_method=hook`: the events, the payload shapes, and the v1 hook schema are all AWS's. Asymptote owning the file it writes is a question of who authored it, not of who defines the contract — it ships no plugin source Kiro loads and executes.
+Kiro reports as the `kiro` harness with capability `hooks`, and every event carries `harness.collection_method=hook`: the events, the payload shapes, and the v1 hook schema are all AWS's. Beacon owning the file it writes is a question of who authored it, not of who defines the contract — it ships no plugin source Kiro loads and executes.
## Install or configuration support
@@ -101,7 +101,7 @@ beacon endpoint hooks uninstall --harness kiro
Commit `.kiro/hooks/beacon-endpoint.json` if you want the hooks to apply to everyone working in the repository, and to Kiro Web sessions on it.
-Uninstall removes the file Asymptote wrote and nothing else. Your own hook files in the same directory are never touched.
+Uninstall removes the file Beacon wrote and nothing else. Your own hook files in the same directory are never touched.
## Telemetry coverage
@@ -126,7 +126,7 @@ Uninstall removes the file Asymptote wrote and nothing else. Your own hook files
### Tool taxonomy
-Kiro publishes its tool **names** and not its tool **argument schemas**, so Asymptote classifies on names alone, from a table covering Kiro's whole published catalog and its aliases:
+Kiro publishes its tool **names** and not its tool **argument schemas**, so Beacon classifies on names alone, from a table covering Kiro's whole published catalog and its aliases:
| Tool | Recorded as |
|------|-------------|
@@ -152,45 +152,45 @@ Kiro's most frequent tool takes an `operations` array rather than a `path`:
"tool_input": {"operations": [{"mode": "Line", "path": "/repo/docs/hooks.md"}]}}
```
-Asymptote reads it, so a read event carries a file. A call naming several files records the first — the endpoint schema's `file.path` is one string, and joining them would produce a value no rule matching on `file.path` could use.
+Beacon reads it, so a read event carries a file. A call naming several files records the first — the endpoint schema's `file.path` is one string, and joining them would produce a value no rule matching on `file.path` could use.
-### Diffs, and what Asymptote will not guess
+### Diffs, and what Beacon will not guess
Kiro does not publish its write tool's arguments, so the diff builder reads **both** plausible spellings of each field: `file_text`, `old_str`, and `new_str` from the Amazon Q Developer CLI lineage Kiro CLI descends from, and `content`, `old_string`, and `new_string` from the ecosystem convention.
-That is deliberately not guessing. A shape Asymptote cannot read produces **no diff**, never a wrong one — the event still records `file.modified` with the path and the operation, and only the diff is honestly unavailable.
+That is deliberately not guessing. A shape Beacon cannot read produces **no diff**, never a wrong one — the event still records `file.modified` with the path and the operation, and only the diff is honestly unavailable.
A failed write is never recorded as an edit. Kiro reports one with the same tool name and the same arguments as a success, and `success` on the result is the only thing that separates them; without that guard a diff would be built from a write that never landed.
<Note>
-**`command` on a write is not a shell command.** Kiro's write tool descends from a multiplexed `fs_write` where `command` names the editor operation — `create`, `str_replace`, `insert` — and `command` is also what the shell tool calls its command line. Asymptote guards on the tool name, so an editor operation is never recorded under `command.command` and a real shell command is never dropped.
+**`command` on a write is not a shell command.** Kiro's write tool descends from a multiplexed `fs_write` where `command` names the editor operation — `create`, `str_replace`, `insert` — and `command` is also what the shell tool calls its command line. Beacon guards on the tool name, so an editor operation is never recorded under `command.command` and a real shell command is never dropped.
</Note>
## Approvals and enforcement
-**Asymptote records no approval decisions for Kiro, and does not synthesize any.**
+**Beacon records no approval decisions for Kiro, and does not synthesize any.**
Kiro genuinely does ask the operator — through `permissions.yaml` rules and an interactive trust picker — and exposes none of that to a hook. `PreToolUse` fires identically whether the call was pre-approved by a rule, waved through by autopilot, or about to stop and wait for a person. An `approval.allowed` derived from it would therefore claim a decision in exactly the cases where none has been made yet, which is worse than the runtimes that have no approval gate at all. This is the same call already settled for [Cline](/runtimes/cline), [Pi](/runtimes/pi), [OpenHands](/runtimes/openhands), and [fx](/runtimes/vercel-fx).
-Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error. Kiro is one of the runtimes where a provider deny does take effect, and it is the only one where the deny is **not** a JSON object: Asymptote exits with code **2** and writes the reason to stderr, which is Kiro's documented way to block `PreToolUse`. Kiro hands that stderr text to the agent as the explanation for the refusal. Any other non-zero exit code is an error to Kiro rather than a block, which is why Asymptote exits 0 on every other path.
+Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error. Kiro is one of the runtimes where a provider deny does take effect, and it is the only one where the deny is **not** a JSON object: Beacon exits with code **2** and writes the reason to stderr, which is Kiro's documented way to block `PreToolUse`. Kiro hands that stderr text to the agent as the explanation for the refusal. Any other non-zero exit code is an error to Kiro rather than a block, which is why Beacon exits 0 on every other path.
## Data handling
Kiro content is handled like every other runtime. Prompts, tool arguments, commands, command output, paths, diffs, and the agent's final response are retained in local or customer-controlled logs, with local secret redaction and per-string limits applied before writing, and a hash and byte count on each content-bearing event. Events over the 64 KiB limit drop raw and retained content, preserve stable metadata, and set `field_truncated`.
-Unlike [Qwen Code](/runtimes/qwen-code) and [Muse Code](/runtimes/muse-code), Asymptote does **not** preserve the verbatim Kiro payload under a `raw` key. Kiro's envelope has no field left over once the readers have run, so keeping the payload would duplicate `tool_input` and `tool_response` — file contents included — to preserve nothing.
+Unlike [Qwen Code](/runtimes/qwen-code) and [Muse Code](/runtimes/muse-code), Beacon does **not** preserve the verbatim Kiro payload under a `raw` key. Kiro's envelope has no field left over once the readers have run, so keeping the payload would duplicate `tool_input` and `tool_response` — file contents included — to preserve nothing.
## Known gaps
-- **No approval decisions.** Kiro exposes no approval or permission hook, and Asymptote does not synthesize one from `PreToolUse`. Approval rules and dashboards will show nothing for this runtime.
+- **No approval decisions.** Kiro exposes no approval or permission hook, and Beacon does not synthesize one from `PreToolUse`. Approval rules and dashboards will show nothing for this runtime.
- **No token usage or cost.** No Kiro hook payload carries token counts or cost. Kiro activity therefore does not appear in `beacon token-usage` reports or the dashboard token view.
-- **No spec task lifecycle.** Kiro's `PreTaskExec` and `PostTaskExec` triggers announce a spec task starting and finishing, and they are real signal with no duplicate elsewhere — but Kiro does not document what they put on stdin, and without a task id or name the event would say only that some task began. Asymptote does not subscribe to them. This is the one gap a published payload would close.
+- **No spec task lifecycle.** Kiro's `PreTaskExec` and `PostTaskExec` triggers announce a spec task starting and finishing, and they are real signal with no duplicate elsewhere — but Kiro does not document what they put on stdin, and without a task id or name the event would say only that some task began. Beacon does not subscribe to them. This is the one gap a published payload would close.
- **No file-trigger events.** `PostFileCreate`, `PostFileSave`, and `PostFileDelete` are deliberately not subscribed to. Kiro's file triggers fire only for changes the agent made, and every such change goes through a write tool — so subscribing would record two events for one write with no way for a reader to tell they were the same action, and the duplicate would be the poorer of the two: a file trigger offers a path where `PostToolUse` carries the path, the operation, the content, and the result. Nothing is lost, and double-counting a file change in a security log is avoided.
- **No per-session end event.** Kiro's `Stop` fires when the agent finishes a turn, not when a session ends, so it is recorded as `tool.completed` rather than `session.ended`. There is no session-end trigger to subscribe to.
- **No tool call identity.** The hook payload carries no per-call identifier, so `gen_ai.tool.call.id` is absent and a pre-tool event cannot be joined to its post-tool event by id.
- **No transcript path.** Kiro keeps session state in its own directory and no payload field points at it.
- **No compaction or subagent events.** Kiro emits neither on a hook, so neither is recorded.
-- **Write argument shapes are inferred.** Kiro publishes its tool names and not its tool argument schemas. Asymptote reads both plausible spellings and records no diff when neither resolves — see [Diffs, and what Asymptote will not guess](#diffs-and-what-asymptote-will-not-guess).
+- **Write argument shapes are inferred.** Kiro publishes its tool names and not its tool argument schemas. Beacon reads both plausible spellings and records no diff when neither resolves — see [Diffs, and what Beacon will not guess](#diffs-and-what-asymptote-will-not-guess).
- **Kiro Web and Mobile do not read a user-scope install.** Neither surface has a local filesystem, so only hooks committed under a repository's `.kiro/hooks/` reach them.
## Deployment notes
@@ -207,7 +207,7 @@ grep '"name":"kiro"' ~/.beacon/endpoint/logs/runtime.jsonl | tail -3
If Kiro telemetry is missing:
-- Confirm the Kiro version. `.kiro/hooks/*.json` needs IDE 1.0 or CLI 3.0; earlier versions use formats Asymptote does not write. In the CLI, `kiro-cli agent migrate` converts 2.x hooks.
+- Confirm the Kiro version. `.kiro/hooks/*.json` needs IDE 1.0 or CLI 3.0; earlier versions use formats Beacon does not write. In the CLI, `kiro-cli agent migrate` converts 2.x hooks.
- Confirm the file exists at the scope you installed and contains commands with `--platform kiro`.
- Check `$KIRO_HOME`: if it is set, the user-scope file is under that directory, not `~/.kiro`.
- Confirm the file's `version` is `"v1"`. Kiro skips a hook file whose version it does not recognize, without an error.
@@ -222,6 +222,6 @@ If Kiro telemetry is missing:
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
</Columns>
diff --git a/docs/runtimes/muse-code.mdx b/docs/runtimes/muse-code.mdx
index 6b602462..cd089ca8 100644
--- a/docs/runtimes/muse-code.mdx
+++ b/docs/runtimes/muse-code.mdx
@@ -1,11 +1,11 @@
---
title: "Muse Code"
-description: "Asymptote support details for Meta Muse Code endpoint telemetry"
+description: "Beacon support details for Meta Muse Code endpoint telemetry"
---
## Runtime overview
-Asymptote supports Muse Code, Meta's terminal coding agent, through native hook payloads sent to `beacon-hooks`.
+Beacon supports Muse Code, Meta's terminal coding agent, through native hook payloads sent to `beacon-hooks`.
```bash
beacon endpoint hooks install --harness muse
@@ -14,7 +14,7 @@ beacon endpoint hooks install --harness muse
`--harness muse-code` is also accepted.
<Note>
-**Muse Spark is the model; Muse Code is the agent.** Asymptote hooks the agent, so the harness name is `muse_code` and the Muse Spark model id rides on each event in the `model` field. Muse Spark spellings are deliberately **not** accepted as harness aliases: asking to install hooks for a model would otherwise produce an install for the agent under a different name.
+**Muse Spark is the model; Muse Code is the agent.** Beacon hooks the agent, so the harness name is `muse_code` and the Muse Spark model id rides on each event in the `model` field. Muse Spark spellings are deliberately **not** accepted as harness aliases: asking to install hooks for a model would otherwise produce an install for the agent under a different name.
</Note>
Muse Code ships its own OpenTelemetry export, but it cannot be pointed at a local collector. Its `telemetry.destination` setting is an enum (`legacy`, `consolidated`, `edge`, `external`), not a URL: choosing `external` with a local `OTEL_EXPORTER_OTLP_ENDPOINT` causes the binary to detect the non-baseline destination and withhold its credential, disabling export, and the other values name internal destinations unavailable in public builds. Hooks are therefore the only collection path for this runtime, not merely the chosen one.
@@ -33,12 +33,12 @@ Muse Code registers hooks through a **managed hooks file** named by the `managed
| File | Owner | Purpose |
|------|-------|---------|
-| `~/.config/muse/beacon-endpoint-hooks.json` | Asymptote, written outright | The hook registrations themselves |
-| `~/.config/muse/settings.json` | You; Asymptote edits one key | `managed_hooks_path` points Muse at the file above |
+| `~/.config/muse/beacon-endpoint-hooks.json` | Beacon, written outright | The hook registrations themselves |
+| `~/.config/muse/settings.json` | You; Beacon edits one key | `managed_hooks_path` points Muse at the file above |
`$XDG_CONFIG_HOME/muse` is used instead when that variable is set, matching how Muse resolves the directory itself.
-Install edits `settings.json` by exactly one key. Unrelated settings — including ones Asymptote has never heard of — survive the round trip byte for byte. A `settings.json` whose JSON is invalid is reported rather than replaced; its only problem might be a trailing comma.
+Install edits `settings.json` by exactly one key. Unrelated settings — including ones Beacon has never heard of — survive the round trip byte for byte. A `settings.json` whose JSON is invalid is reported rather than replaced; its only problem might be a trailing comma.
<Warning>
**An install is only complete with both files, and Muse reports nothing when it is not.** A hooks file with no `managed_hooks_path` pointing at it is a file Muse never opens. A `managed_hooks_path` with no file behind it registers nothing. `beacon endpoint hooks status --harness muse` therefore checks both halves and prints both paths — checking one would confidently claim telemetry that is not being collected.
@@ -46,7 +46,7 @@ Install edits `settings.json` by exactly one key. Unrelated settings — includi
### Registered events
-Asymptote registers every Muse Code lifecycle event that carries endpoint signal:
+Beacon registers every Muse Code lifecycle event that carries endpoint signal:
| Muse event | Adapter subcommand | Matcher | Timeout |
|------------|--------------------|---------|---------|
@@ -62,7 +62,7 @@ Asymptote registers every Muse Code lifecycle event that carries endpoint signal
| `Stop` | `stop` | `*` | 45 s |
<Warning>
-**Muse hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a settings file that looks nearly identical. Asymptote writes second values for this runtime. Keep the unit in mind if you hand-edit them.
+**Muse hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a settings file that looks nearly identical. Beacon writes second values for this runtime. Keep the unit in mind if you hand-edit them.
</Warning>
### Events that are not collected
@@ -73,17 +73,17 @@ Both carry the full `messages` array and the tool schemas — the entire convers
### The file format fails silently
-Everything about Muse's managed hooks file rejects quietly. There is no `muse hooks validate` command, and a bad file produces no warning, no exit code and no log line — so a broken registration looks exactly like a working one. Asymptote's installer is shaped around that, and each of these is covered by a test:
+Everything about Muse's managed hooks file rejects quietly. There is no `muse hooks validate` command, and a bad file produces no warning, no exit code and no log line — so a broken registration looks exactly like a working one. Beacon's installer is shaped around that, and each of these is covered by a test:
- **The nesting is mandatory.** The `hooks` wrapper and the matcher-group level between the event name and the handlers are both load-bearing. Hoisting event names to the top level, or listing handlers directly under an event name, produces a file Muse ignores entirely.
-- **Unknown keys inside a group or handler are fatal.** One unrecognized key and that whole event is skipped while the rest of the file keeps working — so a typo removes monitoring from one event and leaves the install looking healthy. `env`, `shell`, and a group's `enabled` are all rejected. Asymptote emits only `type`, `command`, `timeout`, and `statusMessage`.
-- **Unknown keys at the top level are tolerated**, which is where Asymptote's `beacon` marker lives.
+- **Unknown keys inside a group or handler are fatal.** One unrecognized key and that whole event is skipped while the rest of the file keeps working — so a typo removes monitoring from one event and leaves the install looking healthy. `env`, `shell`, and a group's `enabled` are all rejected. Beacon emits only `type`, `command`, `timeout`, and `statusMessage`.
+- **Unknown keys at the top level are tolerated**, which is where Beacon's `beacon` marker lives.
### The hook environment
Muse runs hook commands with the environment filtered down to a fixed allowlist. No `BEACON_*` or `OTEL_*` shell export reaches a hook, and `XDG_CONFIG_HOME` is stripped too.
-This costs Asymptote nothing, because the endpoint log and config locations are passed to `beacon-hooks` as `--log` and `--config` flags rather than through the environment. It is worth knowing when reading a hook command by hand, and when debugging why a hook cannot find a path you can see from your shell.
+This costs Beacon nothing, because the endpoint log and config locations are passed to `beacon-hooks` as `--log` and `--config` flags rather than through the environment. It is worth knowing when reading a hook command by hand, and when debugging why a hook cannot find a path you can see from your shell.
## Discovery and status
@@ -105,7 +105,7 @@ beacon endpoint hooks uninstall --harness muse
**User level only.** Muse documents a project-level `.muse/hooks.json`, but the shipping build ignores it, so `--level project` is refused with an error naming the scope that works. Writing that file would report success and collect nothing.
-**Install refuses to take over an existing registration.** Muse reads exactly one managed hooks file, so if `managed_hooks_path` already names somebody else's, Asymptote stops and says so rather than replacing it — overwriting would look like a clean install and quietly end their monitoring. The check runs before anything is written, so a refusal leaves nothing behind. The uninstall is the same property in reverse: it clears the key only while it still names Asymptote's file, and leaves a hooks file Asymptote did not write alone.
+**Install refuses to take over an existing registration.** Muse reads exactly one managed hooks file, so if `managed_hooks_path` already names somebody else's, Beacon stops and says so rather than replacing it — overwriting would look like a clean install and quietly end their monitoring. The check runs before anything is written, so a refusal leaves nothing behind. The uninstall is the same property in reverse: it clears the key only while it still names Beacon's file, and leaves a hooks file Beacon did not write alone.
## Telemetry coverage
@@ -131,15 +131,15 @@ Harness names are matched against a closed set of spellings rather than by subst
### Tool taxonomy
-Muse Code sends the Claude Code payload shape but does not publish its tool names. The names that are confirmed are snake_case (`read_skill`, and the six `subagent_*` control tools), so Asymptote matches file-edit tools with a substring rule over `edit`, `write`, `create` and `patch` rather than a guessed literal list — a wrong literal list would capture nothing, silently.
+Muse Code sends the Claude Code payload shape but does not publish its tool names. The names that are confirmed are snake_case (`read_skill`, and the six `subagent_*` control tools), so Beacon matches file-edit tools with a substring rule over `edit`, `write`, `create` and `patch` rather than a guessed literal list — a wrong literal list would capture nothing, silently.
The false-positive direction is bounded: a `file` block is only attached when the tool's own arguments carry a path, so a non-file tool whose name happens to contain `write` yields an action with no fabricated path. None of `subagent_spawn`, `subagent_status`, `subagent_send_message`, `subagent_cancel`, `subagent_wait` or `subagent_read_result` match, so the lead agent's own fan-out control loop stays out of the file-modification stream.
## Approvals and enforcement
-Approval telemetry comes from Muse's `PermissionRequest` event and is recorded as `observed`, because an operator was actually asked. Asymptote does not synthesize an approval from a pre-tool notification for this runtime — doing so would put an invented decision next to a reported one for the same call.
+Approval telemetry comes from Muse's `PermissionRequest` event and is recorded as `observed`, because an operator was actually asked. Beacon does not synthesize an approval from a pre-tool notification for this runtime — doing so would put an invented decision next to a reported one for the same call.
-Asymptote's `PreToolUse` hook answers with an empty object, for two independent reasons. Muse reads a tool decision from `hookSpecificOutput`, so answering `allow` would disarm the user's own permission prompt on a runtime the hook was installed only to watch. And Muse rejects a stdout object carrying keys it does not know, so a differently shaped permissive answer would not read as permissive — it would fail the hook run.
+Beacon's `PreToolUse` hook answers with an empty object, for two independent reasons. Muse reads a tool decision from `hookSpecificOutput`, so answering `allow` would disarm the user's own permission prompt on a runtime the hook was installed only to watch. And Muse rejects a stdout object carrying keys it does not know, so a differently shaped permissive answer would not read as permissive — it would fail the hook run.
Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error. See [Known gaps](#known-gaps) for the status of Muse's deny contract.
@@ -147,16 +147,16 @@ Enforcement stays behind the optional, off-by-default policy provider seam (`BEA
Muse Code content is handled like every other runtime. Prompts, tool arguments, commands, paths, and diffs are retained in local or customer-controlled logs, with local secret redaction and per-string limits applied before writing, and a hash and byte count on each content-bearing event. Events over the 64 KiB limit drop raw and retained content, preserve stable metadata, and set `field_truncated`.
-Muse carries signal with no endpoint-schema field of its own — most importantly `turn_id`, which is the only per-turn boundary anything in its payload offers, plus `permission_mode` on tool events and `source` on `SessionStart`. Asymptote preserves the verbatim payload under `raw.muse` rather than inventing schema fields for one runtime. It travels the event's normal path through sanitization, so `raw` is secret-redacted and string-limited like every other field, and it is the first thing dropped when an event exceeds the size ceiling.
+Muse carries signal with no endpoint-schema field of its own — most importantly `turn_id`, which is the only per-turn boundary anything in its payload offers, plus `permission_mode` on tool events and `source` on `SessionStart`. Beacon preserves the verbatim payload under `raw.muse` rather than inventing schema fields for one runtime. It travels the event's normal path through sanitization, so `raw` is secret-redacted and string-limited like every other field, and it is the first thing dropped when an event exceeds the size ceiling.
## Known gaps
-- **The hook contract is reverse-engineered, not documented.** Meta publishes no hook API for Muse Code, and `muse --help` does not mention hooks. Asymptote's integration is built from observed behaviour of a shipped build (`muse 0.1.0-R708.1`) rather than from a specification. None of it is a supported interface and any of it can change without notice — which is exactly why the tests pin the payload readers and the emitted file shape: the host rejects a bad hook file silently, so a contract change would otherwise appear as telemetry quietly going missing rather than as an error.
-- **Token usage and cost are not collected.** Muse's usage counts arrive on `PostLLMCall` and in its own session log, neither of which Asymptote reads. Muse Code activity therefore does not appear in `beacon token-usage` reports or the dashboard token view.
-- **No session-end event.** Muse emits `Stop` at the end of a turn but no session-end lifecycle event, so Asymptote records no `session.ended` for this runtime.
-- **Subagents cannot be correlated to their parent.** On `SubagentStart` the payload's own `session_id` is the *child's*, and no parent id is present, so `session.id` on a subagent event identifies the subagent's session rather than the one that spawned it. Muse's on-disk session log does carry `parent_session_id`, but reading it is a poll path Asymptote does not implement; synthesizing a parent from a payload that does not name one would be a fabricated join key in a security log.
+- **The hook contract is reverse-engineered, not documented.** Meta publishes no hook API for Muse Code, and `muse --help` does not mention hooks. Beacon's integration is built from observed behaviour of a shipped build (`muse 0.1.0-R708.1`) rather than from a specification. None of it is a supported interface and any of it can change without notice — which is exactly why the tests pin the payload readers and the emitted file shape: the host rejects a bad hook file silently, so a contract change would otherwise appear as telemetry quietly going missing rather than as an error.
+- **Token usage and cost are not collected.** Muse's usage counts arrive on `PostLLMCall` and in its own session log, neither of which Beacon reads. Muse Code activity therefore does not appear in `beacon token-usage` reports or the dashboard token view.
+- **No session-end event.** Muse emits `Stop` at the end of a turn but no session-end lifecycle event, so Beacon records no `session.ended` for this runtime.
+- **Subagents cannot be correlated to their parent.** On `SubagentStart` the payload's own `session_id` is the *child's*, and no parent id is present, so `session.id` on a subagent event identifies the subagent's session rather than the one that spawned it. Muse's on-disk session log does carry `parent_session_id`, but reading it is a poll path Beacon does not implement; synthesizing a parent from a payload that does not name one would be a fabricated join key in a security log.
- **Assistant text is not collected.** `Stop` carries `last_assistant_message`, which is preserved under `raw.muse` but not promoted to an `agent.response` event.
-- **The policy deny shape is inferred, not measured.** Muse is fail-open on everything except `{"decision":"block"}` and exit code 2. That JSON shape is confirmed to block, but only on `UserPromptSubmit`, where blocking cancels the whole turn — emitting it from a tool phase would escalate "do not run this command" into "abandon what the user asked for", so Asymptote does not use it. The tool-family shape it sends instead (`hookSpecificOutput.permissionDecision`) comes from the binary's own validation strings and has never been exercised against a live tool call. Because sending the wrong shape is ignored silently and the seam fails open, the cost of that inference being wrong is a deny that does not take effect — never a tool call blocked for the wrong reason. Exit code 2 is not used: it is a confirmed deny channel, but it would also fire on a hook crash.
+- **The policy deny shape is inferred, not measured.** Muse is fail-open on everything except `{"decision":"block"}` and exit code 2. That JSON shape is confirmed to block, but only on `UserPromptSubmit`, where blocking cancels the whole turn — emitting it from a tool phase would escalate "do not run this command" into "abandon what the user asked for", so Beacon does not use it. The tool-family shape it sends instead (`hookSpecificOutput.permissionDecision`) comes from the binary's own validation strings and has never been exercised against a live tool call. Because sending the wrong shape is ignored silently and the seam fails open, the cost of that inference being wrong is a deny that does not take effect — never a tool call blocked for the wrong reason. Exit code 2 is not used: it is a confirmed deny channel, but it would also fire on a hook crash.
- **No Windows support.** Muse Code has no Windows build, so there is no host to hook.
## Deployment notes
@@ -173,7 +173,7 @@ grep '"name":"muse_code"' ~/.beacon/endpoint/logs/runtime.jsonl | tail -3
If Muse telemetry is missing:
-- Confirm `~/.config/muse/settings.json` has `managed_hooks_path` pointing at Asymptote's hooks file, and that the file exists. Either half alone collects nothing.
+- Confirm `~/.config/muse/settings.json` has `managed_hooks_path` pointing at Beacon's hooks file, and that the file exists. Either half alone collects nothing.
- Check `$XDG_CONFIG_HOME`: if it is set, Muse reads `$XDG_CONFIG_HOME/muse`, not `~/.config/muse`.
- Confirm the hooks file contains commands with `--platform muse`.
- Confirm hook timeouts are second values, not milliseconds.
@@ -187,6 +187,6 @@ If Muse telemetry is missing:
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
</Columns>
diff --git a/docs/runtimes/oh-my-pi.mdx b/docs/runtimes/oh-my-pi.mdx
index c11ff472..6a50b003 100644
--- a/docs/runtimes/oh-my-pi.mdx
+++ b/docs/runtimes/oh-my-pi.mdx
@@ -1,20 +1,20 @@
---
title: "Oh My Pi"
-description: "Asymptote support details for Oh My Pi (omp) endpoint telemetry"
+description: "Beacon support details for Oh My Pi (omp) endpoint telemetry"
---
## Runtime overview
-Asymptote supports [Oh My Pi](https://github.com/can1357/oh-my-pi) through a managed local extension.
+Beacon supports [Oh My Pi](https://github.com/can1357/oh-my-pi) through a managed local extension.
-Oh My Pi is a fork of [pi-mono](https://github.com/badlogic/pi-mono) that ships as the `omp` binary, so it fits the same integration shape as [Pi](/runtimes/pi): no hooks configuration file to merge a managed hook block into, and no OpenTelemetry support to point at the local collector. Its observation surface is the TypeScript extension API, so one Asymptote-owned extension file forwards runtime events to `beacon-hooks`.
+Oh My Pi is a fork of [pi-mono](https://github.com/badlogic/pi-mono) that ships as the `omp` binary, so it fits the same integration shape as [Pi](/runtimes/pi): no hooks configuration file to merge a managed hook block into, and no OpenTelemetry support to point at the local collector. Its observation surface is the TypeScript extension API, so one Beacon-owned extension file forwards runtime events to `beacon-hooks`.
```bash
beacon endpoint hooks install --harness omp
```
<Note>
-Oh My Pi and Pi are separately installed products, and Asymptote records them under separate harness names. A machine running both produces two distinct streams; nothing is merged. If you are looking for upstream Pi, see [Pi](/runtimes/pi).
+Oh My Pi and Pi are separately installed products, and Beacon records them under separate harness names. A machine running both produces two distinct streams; nothing is merged. If you are looking for upstream Pi, see [Pi](/runtimes/pi).
</Note>
## Prerequisites
@@ -27,7 +27,7 @@ Before enabling Oh My Pi telemetry, make sure:
## Collection path
-Asymptote's managed extension is a single TypeScript file in one of Oh My Pi's two auto-discovered extension directories:
+Beacon's managed extension is a single TypeScript file in one of Oh My Pi's two auto-discovered extension directories:
| Level | Extension path |
|-------|----------------|
@@ -43,13 +43,13 @@ The two paths resolve asymmetrically, which matters if you set either of Oh My P
| `PI_CODING_AGENT_DIR` | Replaces the user agent directory outright, so the extension goes to `$PI_CODING_AGENT_DIR/extensions/beacon.ts`. Oh My Pi sets this on its own process when a named profile is active, so installing from inside a profiled session lands in `~/.omp/profiles/<name>/agent/extensions/` |
| `PI_CONFIG_DIR` | Renames the `.omp` directory under your home directory only. The project path stays `./.omp/extensions/` |
-Asymptote identifies its own extension by the marker `beacon-managed-omp-extension:v1`, which is distinct from Pi's. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Asymptote telemetry.
+Beacon identifies its own extension by the marker `beacon-managed-omp-extension:v1`, which is distinct from Pi's. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Beacon telemetry.
-Oh My Pi has no OpenTelemetry export for Asymptote to configure, so there is no OTLP path for this runtime.
+Oh My Pi has no OpenTelemetry export for Beacon to configure, so there is no OTLP path for this runtime.
## Discovery and status
-Asymptote detects Oh My Pi through the `omp` executable, and treats the resolved agent directory as an additional signal. Oh My Pi installed through bun, a version manager, or its own installer is often missing from the `PATH` the endpoint process inherited while its state directory is still present. The Pi, OpenCode, Cursor, and Hermes probes use the same fallback.
+Beacon detects Oh My Pi through the `omp` executable, and treats the resolved agent directory as an additional signal. Oh My Pi installed through bun, a version manager, or its own installer is often missing from the `PATH` the endpoint process inherited while its state directory is still present. The Pi, OpenCode, Cursor, and Hermes probes use the same fallback.
```bash title="Show Oh My Pi discovery state"
beacon endpoint discover --all --json
@@ -60,8 +60,8 @@ Oh My Pi reports as the `omp` harness with capability `plugin`:
| Telemetry status | Meaning |
|------------------|---------|
| `missing` | No extension file at the user-level managed path |
-| `disabled` | A `beacon.ts` exists but carries no Asymptote Oh My Pi marker, so it is somebody else's extension sharing the filename |
-| `enabled` | Asymptote's managed extension is in place |
+| `disabled` | A `beacon.ts` exists but carries no Beacon Oh My Pi marker, so it is somebody else's extension sharing the filename |
+| `enabled` | Beacon's managed extension is in place |
A file carrying Pi's marker at this path is not an Oh My Pi install. The two runtimes read different directories, so it should not arise, but the markers are distinct so the answer does not depend on that staying true.
@@ -103,16 +103,16 @@ Unlike Pi, a project-level install needs no trust prompt: Oh My Pi loads `.omp`
### Approval telemetry
-Asymptote never synthesizes an approval from a tool call. A `tool_call` handler that blocks is an extension deciding, not an operator being asked, and recording that as an approval would be indistinguishable from an answer a human gave — which is why [Pi](/runtimes/pi) and [Cline](/runtimes/cline) carry no approval telemetry at all.
+Beacon never synthesizes an approval from a tool call. A `tool_call` handler that blocks is an extension deciding, not an operator being asked, and recording that as an approval would be indistinguishable from an answer a human gave — which is why [Pi](/runtimes/pi) and [Cline](/runtimes/cline) carry no approval telemetry at all.
Oh My Pi reports the prompt and the answer as their own events, so its approval events are real. Each one carries:
- The operator's decision, and the runtime's own reason when it gave one.
-- The command or file path being decided on. Oh My Pi's approval events carry the tool name but none of its arguments, so the managed extension remembers each `tool_call`'s input by the runtime's own call id and attaches it to the approval for that call. Without this the approval would say "the operator denied `bash`" rather than "the operator denied `rm -rf /var/data`", and every approval rule Asymptote ships matches on the command or path rather than on a tool name.
+- The command or file path being decided on. Oh My Pi's approval events carry the tool name but none of its arguments, so the managed extension remembers each `tool_call`'s input by the runtime's own call id and attaches it to the approval for that call. Without this the approval would say "the operator denied `bash`" rather than "the operator denied `rm -rf /var/data`", and every approval rule Beacon ships matches on the command or path rather than on a tool name.
- `gen_ai.tool.call.id`, joining the decision to the `tool.invoked` it decided on.
- The session's approval mode in `raw.omp_approval_mode`: `always-ask`, `write`, or `yolo`. A `yolo` session had the prompts turned off, which is the difference between a decision someone made and a decision nobody was asked to make.
-A resolved approval whose outcome Asymptote cannot read is recorded as a denial. The safe reading of "no evidence the operator said yes" is not "the operator said yes". An approval for a call the extension never saw proposed still records the decision, the tool name, and the call id, without inventing a command block for it.
+A resolved approval whose outcome Beacon cannot read is recorded as a denial. The safe reading of "no evidence the operator said yes" is not "the operator said yes". An approval for a call the extension never saw proposed still records the decision, the tool name, and the call id, without inventing a command block for it.
Detections in `rules/approval-abuse/` fire on Oh My Pi activity, unlike on Pi. A denied `rm -rf` followed by its execution raises `approval-denied-command-executed-anyway`; a `yolo`-mode allow of a destructive command raises `high-risk-approval-allowed-without-reason`.
@@ -120,14 +120,14 @@ Detections in `rules/approval-abuse/` fire on Oh My Pi activity, unlike on Pi. A
Oh My Pi content is handled like every other runtime. Prompts, tool arguments, commands, Python source, paths, diffs, and reasoning text are retained in local or customer-controlled logs, with local secret redaction and per-string limits applied before writing, and a hash and byte count on each content-bearing event. Events over the 64 KiB limit drop raw and retained content, preserve stable metadata, and set `field_truncated`.
-The extension itself sends nothing over the network. It spawns the local `beacon-hooks` binary with a fixed argv and writes the event to its stdin. A send that has not completed in two seconds is abandoned so Beacon cannot stall Oh My Pi's agent loop, and a failure to spawn costs the event rather than the run. Every handler returns nothing, so Oh My Pi never reads a directive back from Asymptote — the extension cannot block a tool call, revise its arguments, or answer a question that was put to the operator.
+The extension itself sends nothing over the network. It spawns the local `beacon-hooks` binary with a fixed argv and writes the event to its stdin. A send that has not completed in two seconds is abandoned so Beacon cannot stall Oh My Pi's agent loop, and a failure to spawn costs the event rather than the run. Every handler returns nothing, so Oh My Pi never reads a directive back from Beacon — the extension cannot block a tool call, revise its arguments, or answer a question that was put to the operator.
## Known gaps
- **No enforcement.** As with every other runtime, enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is not wired to Oh My Pi. Its blocking `tool_call` handler and its approval events make it a viable target for that seam later.
- **Streaming events are not collected.** The extension subscribes to ten of Oh My Pi's event types and ignores the rest, which are provider-request internals, streaming message updates, compaction and retry signals, and TUI plumbing. Assistant output is recorded once when a message finalizes rather than token by token, so Beacon stays out of the streaming path.
- **MCP notifications are not collected.** `mcp_notification` fires for every JSON-RPC notification a connected server sends, most of them routine tools and resources list refreshes. It describes MCP transport plumbing rather than an action the agent took. MCP tool calls the agent makes *are* collected.
-- **Named profiles need the environment variable.** Asymptote installs into the agent directory `PI_CODING_AGENT_DIR` names, or the default one when it is unset. It does not enumerate `~/.omp/profiles/`, so instrumenting a named profile means running the install with that variable set — which is what Oh My Pi itself does inside a profiled session.
+- **Named profiles need the environment variable.** Beacon installs into the agent directory `PI_CODING_AGENT_DIR` names, or the default one when it is unset. It does not enumerate `~/.omp/profiles/`, so instrumenting a named profile means running the install with that variable set — which is what Oh My Pi itself does inside a profiled session.
- **Session switches are not distinguished.** Oh My Pi's `session_start` carries no reason, and its `session_switch`, `session_branch`, and `session_tree` events are not subscribed to, so a resumed or forked session is not marked as such.
## Deployment notes
diff --git a/docs/runtimes/openclaw-gateway.mdx b/docs/runtimes/openclaw-gateway.mdx
index b94d2d45..1dbca862 100644
--- a/docs/runtimes/openclaw-gateway.mdx
+++ b/docs/runtimes/openclaw-gateway.mdx
@@ -1,11 +1,11 @@
---
title: "OpenClaw Gateway"
-description: "Asymptote support details for OpenClaw Gateway endpoint telemetry"
+description: "Beacon support details for OpenClaw Gateway endpoint telemetry"
---
## Runtime overview
-[OpenClaw](https://docs.openclaw.ai) is a self-hosted gateway that connects chat apps — Discord, Slack, Signal, Telegram, WhatsApp, iMessage, Matrix, Microsoft Teams and more — to AI coding agents. Asymptote supports it through **three** collection paths. The first two are live collection paths and both are wanted on the same machine; the third is an offline recovery path for historical or missed sessions:
+[OpenClaw](https://docs.openclaw.ai) is a self-hosted gateway that connects chat apps — Discord, Slack, Signal, Telegram, WhatsApp, iMessage, Matrix, Microsoft Teams and more — to AI coding agents. Beacon supports it through **three** collection paths. The first two are live collection paths and both are wanted on the same machine; the third is an offline recovery path for historical or missed sessions:
```bash
beacon endpoint hooks install --harness openclaw # the Beacon-managed plugin
@@ -31,7 +31,7 @@ Before enabling OpenClaw telemetry, make sure:
## Collection path 1: the Beacon-managed plugin
-OpenClaw discovers a plugin as a **directory**, reading each child of its extensions directories and loading the entrypoint that directory's `package.json` declares. So Asymptote owns the directory name `beacon-endpoint` and never reads or writes any other plugin beside it.
+OpenClaw discovers a plugin as a **directory**, reading each child of its extensions directories and loading the entrypoint that directory's `package.json` declares. So Beacon owns the directory name `beacon-endpoint` and never reads or writes any other plugin beside it.
| Scope | Directory | Covers |
|-------|-----------|--------|
@@ -56,7 +56,7 @@ Three files are written, and all three are required — OpenClaw skips a directo
### Registered hooks
-OpenClaw publishes forty-one typed plugin hooks. Asymptote registers ten, and the exclusions are covered under [What Asymptote deliberately does not register](#what-asymptote-deliberately-does-not-register).
+OpenClaw publishes forty-one typed plugin hooks. Beacon registers ten, and the exclusions are covered under [What Beacon deliberately does not register](#what-asymptote-deliberately-does-not-register).
| Hook | Recorded as |
|------|-------------|
@@ -74,18 +74,18 @@ OpenClaw publishes forty-one typed plugin hooks. Asymptote registers ten, and th
<Warning>
**OpenClaw registers `before_tool_call` fail-closed.** A handler that throws, or that exceeds its timeout, **blocks the tool call** — that is OpenClaw's default failure policy for this hook, not a misconfiguration.
-Asymptote's handler therefore dispatches its work and returns **synchronously**, with no promise for OpenClaw to wait on, so telemetry cannot stop an agent from working even if the hook binary hangs or the disk is full.
+Beacon's handler therefore dispatches its work and returns **synchronously**, with no promise for OpenClaw to wait on, so telemetry cannot stop an agent from working even if the hook binary hangs or the disk is full.
The cost is ordering: a `tool.invoked` row can land in the log *after* the `tool.completed` row for the same call. That is fine, because ordering was never the join — `gen_ai.tool.call.id` is, and both halves carry it.
</Warning>
Every other handler resolves to `undefined`. OpenClaw reads a returned object on its modify-kind hooks as a request to change behaviour, so returning nothing is what keeps the plugin an observer.
-### Asymptote owns one directory and nothing else
+### Beacon owns one directory and nothing else
-If `beacon.js` in that directory was not written by Asymptote — a `beacon-endpoint` plugin installed from ClawHub, say — both install and uninstall **refuse** rather than overwriting or deleting it.
+If `beacon.js` in that directory was not written by Beacon — a `beacon-endpoint` plugin installed from ClawHub, say — both install and uninstall **refuse** rather than overwriting or deleting it.
-Uninstall removes the three files **and the directory**, because a directory holding manifests and no entrypoint is a plugin OpenClaw tries to load and reports as broken. A file you put in there stops the directory removal rather than being deleted with Asymptote's.
+Uninstall removes the three files **and the directory**, because a directory holding manifests and no entrypoint is a plugin OpenClaw tries to load and reports as broken. A file you put in there stops the directory removal rather than being deleted with Beacon's.
## Collection path 2: OpenClaw's OpenTelemetry export
@@ -99,7 +99,7 @@ beacon endpoint integrations openclaw validate # fail if none have
This path carries gateway-level traces and metrics. It does **not** replace the plugin: without `captureContent` explicitly enabled it carries no prompt, response, tool-input, tool-output or system-prompt content, and OpenClaw documents that default deliberately.
-By default Asymptote filters OpenClaw's operational metrics out of the runtime log as low-signal; `beacon endpoint install --include-runtime-metrics` keeps them.
+By default Beacon filters OpenClaw's operational metrics out of the runtime log as low-signal; `beacon endpoint install --include-runtime-metrics` keeps them.
## Collection path 3: committed session files
@@ -122,7 +122,7 @@ It does not replace the plugin. A poll reader cannot hold or deny a tool call, c
## Your gateway config is read, never written
-Asymptote does **not** edit `~/.openclaw/openclaw.json`. This is the one deliberate departure from how every other runtime is handled, and the reason is that OpenClaw's config is "JSON or JSON5" by its own documentation: JSON5 permits comments, trailing commas and unquoted keys, none of which survive a round trip through a JSON encoder. Rewriting it would silently strip your comments out of the file that configures every chat channel you run.
+Beacon does **not** edit `~/.openclaw/openclaw.json`. This is the one deliberate departure from how every other runtime is handled, and the reason is that OpenClaw's config is "JSON or JSON5" by its own documentation: JSON5 permits comments, trailing commas and unquoted keys, none of which survive a round trip through a JSON encoder. Rewriting it would silently strip your comments out of the file that configures every chat channel you run.
Instead, the installer reads that config and tells you what is missing. Two keys can matter:
@@ -145,9 +145,9 @@ Instead, the installer reads that config and tells you what is missing. Two keys
This is the failure mode that looks most like success, so `beacon endpoint hooks install` prints it and `beacon endpoint hooks status --harness openclaw` repeats it on every check.
</Warning>
-If — and only if — your config already has a `plugins.allow` allowlist, `beacon-endpoint` has to be named in it or the plugin will not load at all. Asymptote says so when the key is present and stays silent when it is not: introducing an allowlist where none existed would deny every other plugin you run.
+If — and only if — your config already has a `plugins.allow` allowlist, `beacon-endpoint` has to be named in it or the plugin will not load at all. Beacon says so when the key is present and stays silent when it is not: introducing an allowlist where none existed would deny every other plugin you run.
-A config Asymptote cannot parse produces no advice rather than a guess, which is the common case for JSON5.
+A config Beacon cannot parse produces no advice rather than a guess, which is the common case for JSON5.
## Discovery and status
@@ -158,7 +158,7 @@ beacon endpoint integrations openclaw sessions status
beacon endpoint discover --all
```
-OpenClaw reports as the `openclaw_gateway` harness on every path, so one gateway is one harness in any query that groups by `harness.name`. Plugin events carry `harness.collection_method=plugin` — Asymptote ships the plugin source OpenClaw loads, so its coverage is Asymptote's to fix rather than OpenClaw's to expose — OTLP events carry `otlp`, and session-file sync events carry `poll`.
+OpenClaw reports as the `openclaw_gateway` harness on every path, so one gateway is one harness in any query that groups by `harness.name`. Plugin events carry `harness.collection_method=plugin` — Beacon ships the plugin source OpenClaw loads, so its coverage is Beacon's to fix rather than OpenClaw's to expose — OTLP events carry `otlp`, and session-file sync events carry `poll`.
Status checks the manifests as well as the plugin entry, because a directory OpenClaw skipped and a plugin that loaded and saw nothing look identical from the log alone.
@@ -171,7 +171,7 @@ beacon endpoint hooks status --harness openclaw
beacon endpoint hooks uninstall --harness openclaw
```
-`beacon endpoint install --harness openclaw` is **not** the command — OpenClaw's OTLP export lives in OpenClaw's own config, so Asymptote prints the settings rather than writing them. Running it says so and names both commands.
+`beacon endpoint install --harness openclaw` is **not** the command — OpenClaw's OTLP export lives in OpenClaw's own config, so Beacon prints the settings rather than writing them. Running it says so and names both commands.
## Telemetry coverage
@@ -216,7 +216,7 @@ beacon endpoint hooks uninstall --harness openclaw
The Claude-style `mcp__server__tool` form is still recognized first, because OpenClaw's own Codex and Claude harness bridges mint it.
</Note>
-A backgrounded `exec` reports `status: "running"` with a partial tail and no exit code. Asymptote records the command line and **no outcome** for it, rather than presenting a partial tail as the command's output.
+A backgrounded `exec` reports `status: "running"` with a partial tail and no exit code. Beacon records the command line and **no outcome** for it, rather than presenting a partial tail as the command's output.
### apply_patch, and why it needs both halves of the call
@@ -226,9 +226,9 @@ Paths from a call the plugin never saw proposed are **dropped rather than guesse
## Approvals and enforcement
-**Asymptote records no approval decisions for OpenClaw, and does not synthesize any.**
+**Beacon records no approval decisions for OpenClaw, and does not synthesize any.**
-OpenClaw genuinely does ask operators to approve tool calls, and exposes no hook reporting the answer: there is no `tool_approval_*` event in its catalog, and the only approval surface a plugin has is `before_tool_call`'s `requireApproval` result — a plugin *requesting* a prompt and being told its own outcome. Asymptote does not request approvals, so it never sees one. This is the same call already settled for [Cline](/runtimes/cline), [Pi](/runtimes/pi), [goose](/runtimes/goose), [OpenHands](/runtimes/openhands) and [Kiro](/runtimes/kiro).
+OpenClaw genuinely does ask operators to approve tool calls, and exposes no hook reporting the answer: there is no `tool_approval_*` event in its catalog, and the only approval surface a plugin has is `before_tool_call`'s `requireApproval` result — a plugin *requesting* a prompt and being told its own outcome. Beacon does not request approvals, so it never sees one. This is the same call already settled for [Cline](/runtimes/cline), [Pi](/runtimes/pi), [goose](/runtimes/goose), [OpenHands](/runtimes/openhands) and [Kiro](/runtimes/kiro).
<Warning>
**`approvalReviewOutcome` is not an approval.** An `exec` result carries `details.approvalReviewOutcome` with the values `approved`, `denied` and `reviewing`, alongside `approvalReviews[]` entries with a status and a rationale. OpenClaw's own type calls these **model-backed** approval reviews: an LLM judging the command, not a person deciding about it.
@@ -238,18 +238,18 @@ Recording one as `approval.allowed` would put a machine's opinion into the field
Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error.
-## What Asymptote deliberately does not register
+## What Beacon deliberately does not register
Some exclusions are about volume, and some are about what a telemetry plugin is allowed to be.
-**Because registering them would give Asymptote power over your agent:**
+**Because registering them would give Beacon power over your agent:**
- `before_prompt_build`, `agent_turn_prepare` and `heartbeat_prompt_contribution` are prompt **injection** hooks.
- `inbound_claim`, `before_dispatch` and `reply_dispatch` are claim hooks that can swallow a message before the agent sees it.
- `before_install` gates skill and plugin installation.
- `skill_proposal_evaluate` makes its handler a **voting evaluator** on whether a skill may be created.
-Asymptote observes. A test asserts none of these is ever registered.
+Beacon observes. A test asserts none of these is ever registered.
**Because they duplicate what is already collected, at much higher volume:**
@@ -274,11 +274,11 @@ The whole hook envelope is kept under `raw.openclaw`, which preserves the fields
## Known gaps
-- **No approval decisions.** OpenClaw exposes no approval event to a plugin, and Asymptote does not synthesize one. Approval rules and dashboards show nothing for this runtime.
-- **No reported cost.** OpenClaw computes a per-turn USD figure from an operator-configured cost table rather than from a provider report, and it is not on the `llm_output` hook. Asymptote records runtime-*reported* cost only, so `gen_ai.usage.cost_usd` stays empty rather than carrying a local estimate.
+- **No approval decisions.** OpenClaw exposes no approval event to a plugin, and Beacon does not synthesize one. Approval rules and dashboards show nothing for this runtime.
+- **No reported cost.** OpenClaw computes a per-turn USD figure from an operator-configured cost table rather than from a provider report, and it is not on the `llm_output` hook. Beacon records runtime-*reported* cost only, so `gen_ai.usage.cost_usd` stays empty rather than carrying a local estimate.
- **Token usage needs a config key.** See [Your gateway config is read, never written](#your-gateway-config-is-read-never-written). This is the most common reason an otherwise healthy OpenClaw install reports no tokens.
- **Tool ordering is not guaranteed.** `tool.invoked` can be written after the completion for the same call, because the `before_tool_call` handler never blocks. Correlate on `gen_ai.tool.call.id`.
-- **No working directory outside a repository.** OpenClaw sets `workspaceDir` for runs that have one and omits it otherwise — a chat turn that never touched a repository genuinely has none. Asymptote leaves the field absent rather than falling back to the gateway daemon's own directory, which would attribute the work to wherever the service manager started it.
+- **No working directory outside a repository.** OpenClaw sets `workspaceDir` for runs that have one and omits it otherwise — a chat turn that never touched a repository genuinely has none. Beacon leaves the field absent rather than falling back to the gateway daemon's own directory, which would attribute the work to wherever the service manager started it.
- **No per-call tool result for most tools.** `after_tool_call` carries a `result`, but only `exec` publishes a documented structure inside it. Other tools' results are kept under `raw` rather than promoted to schema fields.
- **Gateway lifecycle is not collected.** `gateway_start` and `gateway_stop` describe the service rather than agent activity, and the event schema has no action for them.
diff --git a/docs/runtimes/opencode.mdx b/docs/runtimes/opencode.mdx
index 6dc2910a..cadf8727 100644
--- a/docs/runtimes/opencode.mdx
+++ b/docs/runtimes/opencode.mdx
@@ -1,11 +1,11 @@
---
title: "OpenCode"
-description: "Asymptote support details for OpenCode endpoint telemetry"
+description: "Beacon support details for OpenCode endpoint telemetry"
---
## Runtime overview
-Asymptote supports OpenCode through a managed local plugin that invokes `beacon-hooks`.
+Beacon supports OpenCode through a managed local plugin that invokes `beacon-hooks`.
Beacon can also read OpenCode's committed local session store with `beacon endpoint opencode sync`.
That poll path backfills historical or uninstrumented sessions, while the managed plugin remains the
@@ -17,12 +17,12 @@ Before enabling OpenCode telemetry, make sure:
- OpenCode is installed and available as the `opencode` executable or has a local config directory.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- Asymptote's OpenCode plugin is installed with `beacon endpoint hooks install --harness opencode`.
+- Beacon's OpenCode plugin is installed with `beacon endpoint hooks install --harness opencode`.
- OpenCode is restarted after plugin install or removal so new sessions load the updated plugin.
## Collection path
-Asymptote installs an owned OpenCode plugin at `~/.config/opencode/plugins/beacon.ts` for user-level hooks or `./.opencode/plugins/beacon.ts` for project-level hooks. The plugin forwards supported OpenCode hook payloads to Asymptote's hook adapter.
+Beacon installs an owned OpenCode plugin at `~/.config/opencode/plugins/beacon.ts` for user-level hooks or `./.opencode/plugins/beacon.ts` for project-level hooks. The plugin forwards supported OpenCode hook payloads to Beacon's hook adapter.
The integration is plugin-based. OpenCode's native OTLP export is neither configured nor required by Beacon.
@@ -30,7 +30,7 @@ For backfill, `beacon endpoint opencode sync` reads OpenCode's local `opencode.d
## Discovery and status
-Asymptote detects OpenCode through the `opencode` executable or `~/.config/opencode`, then checks for Asymptote plugin configuration.
+Beacon detects OpenCode through the `opencode` executable or `~/.config/opencode`, then checks for Beacon plugin configuration.
Use `beacon endpoint hooks status --harness opencode` to inspect OpenCode plugin status.
Use `beacon endpoint opencode status` to inspect persisted session-store collection progress.
diff --git a/docs/runtimes/openhands.mdx b/docs/runtimes/openhands.mdx
index 5d890dfc..026fe077 100644
--- a/docs/runtimes/openhands.mdx
+++ b/docs/runtimes/openhands.mdx
@@ -1,11 +1,11 @@
---
title: "OpenHands"
-description: "Asymptote support details for OpenHands endpoint telemetry"
+description: "Beacon support details for OpenHands endpoint telemetry"
---
## Runtime overview
-Asymptote supports OpenHands — the open-source coding agent from All Hands — through its native [hooks](https://docs.openhands.dev/openhands/usage/customization/hooks), sent to `beacon-hooks`.
+Beacon supports OpenHands — the open-source coding agent from All Hands — through its native [hooks](https://docs.openhands.dev/openhands/usage/customization/hooks), sent to `beacon-hooks`.
```bash
beacon endpoint hooks install --harness openhands --level project
@@ -16,7 +16,7 @@ beacon endpoint hooks install --harness openhands --level project
OpenHands runs the same agent in three places — Cloud, the CLI, and the local GUI — and all three read hooks from the same `.openhands/hooks.json`. There is one integration rather than three.
<Note>
-**OpenHands LM is the model family; OpenHands is the agent.** Asymptote hooks the agent, so the harness name is `openhands`. OpenHands LM spellings are deliberately **not** accepted as harness aliases and are **not** mapped to the harness name: every one of those model ids begins with the same word the harness does, so a substring rule would file any event carrying one under the agent, and a reader could not tell that from a real session.
+**OpenHands LM is the model family; OpenHands is the agent.** Beacon hooks the agent, so the harness name is `openhands`. OpenHands LM spellings are deliberately **not** accepted as harness aliases and are **not** mapped to the harness name: every one of those model ids begins with the same word the harness does, so a substring rule would file any event carrying one under the agent, and a reader could not tell that from a real session.
</Note>
## Prerequisites
@@ -29,7 +29,7 @@ Before enabling OpenHands telemetry, make sure:
## Collection path
-OpenHands registers hooks in **one JSON file that you also own**, so Asymptote merges its commands into it rather than writing a file of its own. Hooks you already have are preserved exactly, including their matchers, timeouts, and any fields Asymptote has no model for.
+OpenHands registers hooks in **one JSON file that you also own**, so Beacon merges its commands into it rather than writing a file of its own. Hooks you already have are preserved exactly, including their matchers, timeouts, and any fields Beacon has no model for.
| Scope | File | Read by |
|-------|------|---------|
@@ -46,7 +46,7 @@ OpenHands registers hooks in **one JSON file that you also own**, so Asymptote m
### Registered events
-OpenHands exposes six lifecycle events and Asymptote registers all six. Nothing is left out — this is the runtime's whole hook surface.
+OpenHands exposes six lifecycle events and Beacon registers all six. Nothing is left out — this is the runtime's whole hook surface.
| OpenHands event | Adapter subcommand | Matcher | Timeout |
|-----------------|--------------------|---------|---------|
@@ -58,26 +58,26 @@ OpenHands exposes six lifecycle events and Asymptote registers all six. Nothing
| `session_end` | `session-end` | `*` | 45 s |
<Warning>
-**OpenHands hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a hooks file that looks similar. OpenHands' own default is 60 seconds; Asymptote writes explicit lower values, because 60 seconds is a long time to hold an agent turn for a hook that finishes in milliseconds. These are ceilings on a hang, not budgets.
+**OpenHands hook timeouts are seconds, not milliseconds.** The same `timeout` field is milliseconds on [Qwen Code](/runtimes/qwen-code), in a hooks file that looks similar. OpenHands' own default is 60 seconds; Beacon writes explicit lower values, because 60 seconds is a long time to hold an agent turn for a hook that finishes in milliseconds. These are ceilings on a hang, not budgets.
</Warning>
Hooks are registered synchronously rather than with `"async": true`. An async hook is fire-and-forget with its stdout discarded, which would make the [policy seam](#approvals-and-enforcement) unable to deny on the one event that can block.
### The file format fails silently
-`hooks.json` has a closed schema, and every way of getting it wrong ends with hooks silently not running rather than with an error you see. Asymptote's installer is shaped around that, and each of these is covered by a test:
+`hooks.json` has a closed schema, and every way of getting it wrong ends with hooks silently not running rather than with an error you see. Beacon's installer is shaped around that, and each of these is covered by a test:
-- **The top level is the event map itself, and unknown keys are fatal.** One unrecognized top-level key fails validation and the whole file loads as nothing. That is why Asymptote writes no marker key here, unlike the files it owns on other runtimes: an install is recognized by the hook command it contains.
-- **A legacy `{"hooks": {...}}` wrapper is accepted, and the loader unwraps it by replacing the whole document.** Adding a top-level event beside an existing wrapper therefore does not merge — it discards the added hooks. Asymptote writes **inside** the wrapper when it finds one.
-- **Event names may be snake_case or Claude Code's PascalCase, and naming one event both ways is fatal to the entire file.** Asymptote writes under whichever spelling the file already uses for an event and never introduces a second one, so a `hooks.json` shared with Claude Code keeps its PascalCase names.
+- **The top level is the event map itself, and unknown keys are fatal.** One unrecognized top-level key fails validation and the whole file loads as nothing. That is why Beacon writes no marker key here, unlike the files it owns on other runtimes: an install is recognized by the hook command it contains.
+- **A legacy `{"hooks": {...}}` wrapper is accepted, and the loader unwraps it by replacing the whole document.** Adding a top-level event beside an existing wrapper therefore does not merge — it discards the added hooks. Beacon writes **inside** the wrapper when it finds one.
+- **Event names may be snake_case or Claude Code's PascalCase, and naming one event both ways is fatal to the entire file.** Beacon writes under whichever spelling the file already uses for an event and never introduces a second one, so a `hooks.json` shared with Claude Code keeps its PascalCase names.
-A file that already breaks one of these is **refused** with an error naming the problem, rather than written into. Asymptote cannot fix it, and installing would report success while OpenHands went on loading nothing.
+A file that already breaks one of these is **refused** with an error naming the problem, rather than written into. Beacon cannot fix it, and installing would report success while OpenHands went on loading nothing.
### The hook environment
OpenHands runs hook commands through a shell with the conversation's working directory as the cwd, and exports `OPENHANDS_EVENT_TYPE`, `OPENHANDS_TOOL_NAME`, `OPENHANDS_PROJECT_DIR`, and `OPENHANDS_SESSION_ID`.
-Asymptote passes the endpoint log and config locations to `beacon-hooks` as `--log` and `--config` flags rather than through the environment, so a hook finds them wherever it runs. `OPENHANDS_PROJECT_DIR` is read as a fallback for the workspace path, because the payload's `working_dir` is optional and null when the SDK was given no working directory.
+Beacon passes the endpoint log and config locations to `beacon-hooks` as `--log` and `--config` flags rather than through the environment, so a hook finds them wherever it runs. `OPENHANDS_PROJECT_DIR` is read as a fallback for the workspace path, because the payload's `working_dir` is optional and null when the SDK was given no working directory.
## Discovery and status
@@ -85,7 +85,7 @@ Asymptote passes the endpoint log and config locations to `beacon-hooks` as `--l
beacon endpoint hooks status --harness openhands --level project
```
-OpenHands reports as the `openhands` harness with capability `hooks`, and every event carries `harness.collection_method=hook`: the events, the payload shapes, and the `hooks.json` contract are all the vendor's, and Asymptote ships no plugin source of its own for this runtime.
+OpenHands reports as the `openhands` harness with capability `hooks`, and every event carries `harness.collection_method=hook`: the events, the payload shapes, and the `hooks.json` contract are all the vendor's, and Beacon ships no plugin source of its own for this runtime.
## Install or configuration support
@@ -99,7 +99,7 @@ beacon endpoint hooks uninstall --harness openhands --level project
Commit `.openhands/hooks.json` if you want the hooks to apply to everyone working in the repository, the same way the OpenHands documentation describes for hooks you write yourself.
-Re-running the install replaces Asymptote's own hooks rather than adding a second copy, so a repair does not end with the binary firing twice per event. Uninstall removes what Asymptote added and nothing else; a file that still holds your own hooks is rewritten without Asymptote's, and a file left with nothing in it is removed rather than left behind as an empty stub.
+Re-running the install replaces Beacon's own hooks rather than adding a second copy, so a repair does not end with the binary firing twice per event. Uninstall removes what Beacon added and nothing else; a file that still holds your own hooks is rewritten without Beacon's, and a file left with nothing in it is removed rather than left behind as an empty stub.
## Telemetry coverage
@@ -143,35 +143,35 @@ Every other runtime's diff is reconstructed from what the model *asked* for —
OpenHands reports the file's whole content before and after on the observation, so nothing has to be inferred. An insert at line 40 and a single-occurrence replace both come back as the same two strings and produce a diff that matches what is on disk. An `apply_patch` that applied with fuzz records what landed, not what was requested.
-Diffs are captured for the file types Asymptote scans, subject to the usual retention, redaction, and size controls. An edit to a file outside that set is still recorded as `file.modified` with its path — it simply carries no diff.
+Diffs are captured for the file types Beacon scans, subject to the usual retention, redaction, and size controls. An edit to a file outside that set is still recorded as `file.modified` with its path — it simply carries no diff.
A failed edit is never recorded as an edit. The editor reports a failed `str_replace` with the same tool name and the same arguments as a successful one, so without that guard a diff would be built from a write that never landed and the log would assert a file changed when it did not.
## Approvals and enforcement
-**Asymptote records no approval decisions for OpenHands, and does not synthesize any.** OpenHands exposes no approval hook: `pre_tool_use` announces a tool call the agent is about to make, not a question anybody was asked, and its own confirmation mode is not surfaced to hooks. Recording an `approval.allowed` from it would put an operator decision in the log that no operator made — the same call already settled for [Cline](/runtimes/cline), [Pi](/runtimes/pi), and [fx](/runtimes/vercel-fx).
+**Beacon records no approval decisions for OpenHands, and does not synthesize any.** OpenHands exposes no approval hook: `pre_tool_use` announces a tool call the agent is about to make, not a question anybody was asked, and its own confirmation mode is not surfaced to hooks. Recording an `approval.allowed` from it would put an operator decision in the log that no operator made — the same call already settled for [Cline](/runtimes/cline), [Pi](/runtimes/pi), and [fx](/runtimes/vercel-fx).
-Asymptote's `pre_tool_use` hook answers with an empty object. OpenHands reads `decision`, `reason`, `additionalContext`, and `continue` from a hook's stdout; a speculative `allow` carries none of those and is inert today, but the raw string is shown in the conversation as a decision Asymptote did not make, and would begin taking effect if OpenHands ever read that key.
+Beacon's `pre_tool_use` hook answers with an empty object. OpenHands reads `decision`, `reason`, `additionalContext`, and `continue` from a hook's stdout; a speculative `allow` carries none of those and is inert today, but the raw string is shown in the conversation as a decision Beacon did not make, and would begin taking effect if OpenHands ever read that key.
-Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error. OpenHands is one of the runtimes where a provider deny does take effect: `pre_tool_use` can block, and Asymptote answers a deny with `{"decision": "deny", "reason": "..."}`. The reason is sent because OpenHands surfaces it in the conversation as the explanation for the block and hands it to the agent as the tool's failure — without it, the operator and the model both see a call refused with no account of why.
+Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error. OpenHands is one of the runtimes where a provider deny does take effect: `pre_tool_use` can block, and Beacon answers a deny with `{"decision": "deny", "reason": "..."}`. The reason is sent because OpenHands surfaces it in the conversation as the explanation for the block and hands it to the agent as the tool's failure — without it, the operator and the model both see a call refused with no account of why.
## Data handling
OpenHands content is handled like every other runtime. Prompts, tool arguments, commands, command output, paths, and diffs are retained in local or customer-controlled logs, with local secret redaction and per-string limits applied before writing, and a hash and byte count on each content-bearing event. Events over the 64 KiB limit drop raw and retained content, preserve stable metadata, and set `field_truncated`.
-Unlike [Qwen Code](/runtimes/qwen-code) and [Muse Code](/runtimes/muse-code), Asymptote does **not** preserve the verbatim OpenHands payload under a `raw` key. The payload's only field with no schema home is `metadata`, which is empty on five of the six events and carries a constant `reason` on `stop`. Keeping the payload would cost the whole `tool_input` and `tool_response` on every event — file contents included, twice over on an edit — to preserve a value that never varies.
+Unlike [Qwen Code](/runtimes/qwen-code) and [Muse Code](/runtimes/muse-code), Beacon does **not** preserve the verbatim OpenHands payload under a `raw` key. The payload's only field with no schema home is `metadata`, which is empty on five of the six events and carries a constant `reason` on `stop`. Keeping the payload would cost the whole `tool_input` and `tool_response` on every event — file contents included, twice over on an edit — to preserve a value that never varies.
Image parts in a tool result are skipped rather than described: they carry base64 data URLs, often megabytes of them, and writing one into an event field would be worse than recording nothing.
## Known gaps
-- **No approval decisions.** OpenHands has no approval or permission hook, and Asymptote does not synthesize one from `pre_tool_use`. Approval rules and dashboards will show nothing for this runtime.
+- **No approval decisions.** OpenHands has no approval or permission hook, and Beacon does not synthesize one from `pre_tool_use`. Approval rules and dashboards will show nothing for this runtime.
- **No token usage or cost.** None of the six hook payloads carries token counts or cost, and OpenHands exposes no other hook that would. OpenHands activity therefore does not appear in `beacon token-usage` reports or the dashboard token view.
- **No tool call identity.** The hook payload carries no per-call identifier, so `gen_ai.tool.call.id` is absent and a pre-tool event cannot be joined to its post-tool event by id. The `HookEvent` model has no field for it; the id exists on the conversation's action event, which hooks are not given.
- **MCP calls are only identifiable after the fact.** OpenHands calls an MCP tool by whatever name its server gave it, with no prefix and no `mcp_*` argument, so the only thing that says a call went to an MCP server is the result it came back with. A `pre_tool_use` event for an MCP tool is recorded under the action its name implies. The MCP server name is not exposed on the result at all, so `mcp.server` is empty.
- **No transcript path.** Conversation state lives in the OpenHands persistence directory and no payload field points at it, so nothing on this path reads it.
-- **No compaction or subagent events.** OpenHands emits neither on a hook. Its `Stop` hook is a turn boundary, not a session end; the session-end event is separate and Asymptote registers both.
-- **A user-scope install is shadowed by a repository's own hooks file, and invisible to the agent server.** See the warning under [Collection path](#collection-path). This is OpenHands' loader behaviour, not something Asymptote can work around.
+- **No compaction or subagent events.** OpenHands emits neither on a hook. Its `Stop` hook is a turn boundary, not a session end; the session-end event is separate and Beacon registers both.
+- **A user-scope install is shadowed by a repository's own hooks file, and invisible to the agent server.** See the warning under [Collection path](#collection-path). This is OpenHands' loader behaviour, not something Beacon can work around.
- **Assistant response text is not collected.** No hook payload carries it.
## Deployment notes
@@ -203,6 +203,6 @@ If OpenHands telemetry is missing:
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
</Columns>
diff --git a/docs/runtimes/pi.mdx b/docs/runtimes/pi.mdx
index f8a8c301..536950e0 100644
--- a/docs/runtimes/pi.mdx
+++ b/docs/runtimes/pi.mdx
@@ -1,23 +1,23 @@
---
title: "Pi"
-description: "Asymptote support details for Pi endpoint telemetry"
+description: "Beacon support details for Pi endpoint telemetry"
---
## Runtime overview
-Asymptote supports [Pi](https://pi.dev/) through a managed local extension.
+Beacon supports [Pi](https://pi.dev/) through a managed local extension.
<Note>
Looking for [Oh My Pi](/runtimes/oh-my-pi) (`omp`), [Prime Agent](/runtimes/prime-agent), or [Senpi](/runtimes/senpi) (`omo`, the standalone edition of oh-my-openagent)? All three are forks of Pi, supported separately and recorded under their own harness names. Unlike Pi, Oh My Pi reports operator approval decisions.
</Note>
-Pi fits neither of Asymptote's two usual live integration shapes. It has no hooks configuration file to merge a managed hook block into, and no OpenTelemetry support to point at the local collector. Its documented observation surface is the TypeScript extension API, so the live integration is extension-shaped: one Asymptote-owned extension file forwards runtime events to `beacon-hooks`, the same shape as the OpenCode and Cline plugins.
+Pi fits neither of Beacon's two usual live integration shapes. It has no hooks configuration file to merge a managed hook block into, and no OpenTelemetry support to point at the local collector. Its documented observation surface is the TypeScript extension API, so the live integration is extension-shaped: one Beacon-owned extension file forwards runtime events to `beacon-hooks`, the same shape as the OpenCode and Cline plugins.
```bash
beacon endpoint hooks install --harness pi
```
-Asymptote can also read Pi's committed JSONL session store after the fact:
+Beacon can also read Pi's committed JSONL session store after the fact:
```bash
beacon endpoint pi sync
@@ -35,7 +35,7 @@ Before enabling Pi telemetry, make sure:
## Collection path
-Asymptote's managed Pi extension is a single TypeScript file at one of two documented extension locations:
+Beacon's managed Pi extension is a single TypeScript file at one of two documented extension locations:
| Level | Extension path |
|-------|----------------|
@@ -44,13 +44,13 @@ Asymptote's managed Pi extension is a single TypeScript file at one of two docum
User level is the default. A project-level extension is subject to Pi's project-trust prompt, and `beacon endpoint discover` reports on the user path only, so a project-level extension does not appear in discovery output.
-Asymptote identifies its own extension file by the marker `beacon-managed-pi-extension:v1`. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Asymptote telemetry.
+Beacon identifies its own extension file by the marker `beacon-managed-pi-extension:v1`. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Beacon telemetry.
-Pi has no OpenTelemetry export for Asymptote to configure, so there is no OTLP path for this runtime. The poll path reads JSONL transcripts from `~/.pi/agent/sessions`; if `PI_CODING_AGENT_DIR` is set, Asymptote reads `sessions` below that directory, matching Pi's user-level agent directory override. The cursor lives in Asymptote state, not in Pi's directory.
+Pi has no OpenTelemetry export for Beacon to configure, so there is no OTLP path for this runtime. The poll path reads JSONL transcripts from `~/.pi/agent/sessions`; if `PI_CODING_AGENT_DIR` is set, Beacon reads `sessions` below that directory, matching Pi's user-level agent directory override. The cursor lives in Beacon state, not in Pi's directory.
## Discovery and status
-Asymptote detects Pi through the `pi` executable, and treats the `~/.pi/agent` state directory as an additional signal. Pi installed through npm, pnpm, or bun is often missing from the `PATH` the endpoint process inherited, because a shell alias, a version manager, or a per-project install can all hide it while the state directory is still present. The OpenCode, Cursor, and Hermes probes use the same fallback.
+Beacon detects Pi through the `pi` executable, and treats the `~/.pi/agent` state directory as an additional signal. Pi installed through npm, pnpm, or bun is often missing from the `PATH` the endpoint process inherited, because a shell alias, a version manager, or a per-project install can all hide it while the state directory is still present. The OpenCode, Cursor, and Hermes probes use the same fallback.
```bash title="Show Pi discovery state"
beacon endpoint discover --all --json
@@ -61,8 +61,8 @@ Pi reports as the `pi_cli` harness with capability `plugin`:
| Telemetry status | Meaning |
|------------------|---------|
| `missing` | No extension file at the user-level managed path |
-| `disabled` | A `beacon.ts` exists but carries no Asymptote marker, so it is somebody else's extension sharing the filename |
-| `enabled` | Asymptote's managed extension is in place |
+| `disabled` | A `beacon.ts` exists but carries no Beacon marker, so it is somebody else's extension sharing the filename |
+| `enabled` | Beacon's managed extension is in place |
An unmarked extension file reports `disabled` rather than `enabled`, because reporting it as enabled would show the runtime as covered while no events arrive.
@@ -136,6 +136,6 @@ grep '"name":"pi_cli"' ~/.beacon/endpoint/logs/runtime.jsonl | tail -3
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
</Columns>
diff --git a/docs/runtimes/prime-agent.mdx b/docs/runtimes/prime-agent.mdx
index 6616cefd..6f004e74 100644
--- a/docs/runtimes/prime-agent.mdx
+++ b/docs/runtimes/prime-agent.mdx
@@ -1,19 +1,19 @@
---
title: "Prime Agent"
-description: "Asymptote support details for Prime Agent (Prime Intellect) endpoint telemetry"
+description: "Beacon support details for Prime Agent (Prime Intellect) endpoint telemetry"
---
## Runtime overview
-Asymptote supports [Prime Agent](https://github.com/PrimeIntellect-ai/prime-agent), Prime Intellect's coding and research harness, through a managed local extension.
+Beacon supports [Prime Agent](https://github.com/PrimeIntellect-ai/prime-agent), Prime Intellect's coding and research harness, through a managed local extension.
<Note>
Prime Agent is a hard fork of [pi-mono](https://github.com/badlogic/pi-mono), as [Oh My Pi](/runtimes/oh-my-pi) and [Senpi](/runtimes/senpi) are. All four are supported separately and recorded under their own harness names, because they are separately installed products that one machine can run side by side.
</Note>
-Prime Agent fits neither of Asymptote's two usual live integration shapes. It has no hooks configuration file to merge a managed hook block into, and no OpenTelemetry export to point at the local collector. Its documented observation surface is the TypeScript extension API it inherited from Pi, so the live integration is extension-shaped: one Asymptote-owned extension file forwards runtime events to `beacon-hooks`, the same shape as the [Pi](/runtimes/pi), [Oh My Pi](/runtimes/oh-my-pi), [OpenCode](/cli/supported-runtimes-opencode) and [Cline](/cli/supported-runtimes-cline) integrations.
+Prime Agent fits neither of Beacon's two usual live integration shapes. It has no hooks configuration file to merge a managed hook block into, and no OpenTelemetry export to point at the local collector. Its documented observation surface is the TypeScript extension API it inherited from Pi, so the live integration is extension-shaped: one Beacon-owned extension file forwards runtime events to `beacon-hooks`, the same shape as the [Pi](/runtimes/pi), [Oh My Pi](/runtimes/oh-my-pi), [OpenCode](/cli/supported-runtimes-opencode) and [Cline](/cli/supported-runtimes-cline) integrations.
-Asymptote can also read Prime Agent's committed JSONL session store after the fact:
+Beacon can also read Prime Agent's committed JSONL session store after the fact:
```bash
beacon endpoint prime sync
@@ -43,7 +43,7 @@ Before enabling Prime Agent telemetry, make sure:
## Collection path
-Asymptote's managed Prime Agent extension is a single TypeScript file at one of two auto-discovered extension locations:
+Beacon's managed Prime Agent extension is a single TypeScript file at one of two auto-discovered extension locations:
| Level | Extension path |
|-------|----------------|
@@ -56,15 +56,15 @@ User level is the default, because it follows the operator rather than one check
The project path keeps the `agent` segment. Prime Agent's config directory name is the two-segment literal `.prime/agent`, and it joins that whole string under the working directory as well as under the home directory — where [Pi](/runtimes/pi) uses `.pi/extensions` and [Oh My Pi](/runtimes/oh-my-pi) uses `.omp/extensions` at project scope. A file written to `./.prime/extensions/` is never loaded.
</Warning>
-`PRIME_AGENT_CODING_AGENT_DIR` replaces the user-level agent directory outright, and Asymptote honors it — including a leading `~`, which the runtime expands before use. It does not move the project path, because Prime Agent does not consult it there. Asymptote deliberately ignores `PI_CODING_AGENT_DIR`: that is the variable the same upstream code produces for Pi and Oh My Pi, and reading it here would move this install whenever you had set it for a different product.
+`PRIME_AGENT_CODING_AGENT_DIR` replaces the user-level agent directory outright, and Beacon honors it — including a leading `~`, which the runtime expands before use. It does not move the project path, because Prime Agent does not consult it there. Beacon deliberately ignores `PI_CODING_AGENT_DIR`: that is the variable the same upstream code produces for Pi and Oh My Pi, and reading it here would move this install whenever you had set it for a different product.
-Asymptote identifies its own extension file by the marker `beacon-managed-prime-extension:v1`. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Asymptote telemetry. The marker is distinct from Pi's and Oh My Pi's, so a file found at any of the three paths is attributed to the runtime that actually loads it.
+Beacon identifies its own extension file by the marker `beacon-managed-prime-extension:v1`. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Beacon telemetry. The marker is distinct from Pi's and Oh My Pi's, so a file found at any of the three paths is attributed to the runtime that actually loads it.
-Prime Agent has no OpenTelemetry export for Asymptote to configure, so there is no OTLP path for this runtime. The poll path reads JSONL transcripts from `~/.prime/agent/sessions` and subagent artifacts from `~/.prime/agent/session-artifacts`; if `PRIME_AGENT_CODING_AGENT_DIR` is set, Asymptote reads `sessions` and `session-artifacts` below that directory, matching the runtime's user-level agent directory override. The cursor lives in Asymptote state, not in Prime Agent's directory.
+Prime Agent has no OpenTelemetry export for Beacon to configure, so there is no OTLP path for this runtime. The poll path reads JSONL transcripts from `~/.prime/agent/sessions` and subagent artifacts from `~/.prime/agent/session-artifacts`; if `PRIME_AGENT_CODING_AGENT_DIR` is set, Beacon reads `sessions` and `session-artifacts` below that directory, matching the runtime's user-level agent directory override. The cursor lives in Beacon state, not in Prime Agent's directory.
## Discovery and status
-Asymptote detects Prime Agent through the `prime-agent` executable, and treats the `~/.prime/agent` state directory as an additional signal. Prime Agent installed through npm, or through its own installer into `~/.local/share/prime-agent`, is often missing from the `PATH` the endpoint process inherited, because a shell alias, a version manager, or a per-project install can all hide it while the state directory is still present. The Pi, Oh My Pi, OpenCode, Cursor, and Hermes probes use the same fallback.
+Beacon detects Prime Agent through the `prime-agent` executable, and treats the `~/.prime/agent` state directory as an additional signal. Prime Agent installed through npm, or through its own installer into `~/.local/share/prime-agent`, is often missing from the `PATH` the endpoint process inherited, because a shell alias, a version manager, or a per-project install can all hide it while the state directory is still present. The Pi, Oh My Pi, OpenCode, Cursor, and Hermes probes use the same fallback.
The bare name `prime` is deliberately not probed for. It is an ordinary word another binary or an internal script could plausibly claim, and a false positive reports a runtime the machine does not have.
@@ -77,8 +77,8 @@ Prime Agent reports as the `prime_agent` harness with capability `plugin`:
| Telemetry status | Meaning |
|------------------|---------|
| `missing` | No extension file at the user-level managed path |
-| `disabled` | A `beacon.ts` exists but carries no Asymptote marker, so it is somebody else's extension sharing the filename |
-| `enabled` | Asymptote's managed extension is in place |
+| `disabled` | A `beacon.ts` exists but carries no Beacon marker, so it is somebody else's extension sharing the filename |
+| `enabled` | Beacon's managed extension is in place |
An unmarked extension file reports `disabled` rather than `enabled`, because reporting it as enabled would show the runtime as covered while no events arrive.
diff --git a/docs/runtimes/qwen-code.mdx b/docs/runtimes/qwen-code.mdx
index 19d33584..32fdc8db 100644
--- a/docs/runtimes/qwen-code.mdx
+++ b/docs/runtimes/qwen-code.mdx
@@ -1,13 +1,13 @@
---
title: "Qwen Code"
-description: "Asymptote support details for Qwen Code endpoint telemetry"
+description: "Beacon support details for Qwen Code endpoint telemetry"
---
## Runtime overview
-Asymptote supports Qwen Code through native hook payloads sent to `beacon-hooks`.
+Beacon supports Qwen Code through native hook payloads sent to `beacon-hooks`.
-Qwen Code is a Gemini CLI fork, but it does not carry Gemini's OpenTelemetry export, so there is no OTLP path for this runtime. Hooks are the only collection path. Asymptote merges a managed hook block into Qwen's own `settings.json`, the same way the Claude Code and Factory Droid installers do.
+Qwen Code is a Gemini CLI fork, but it does not carry Gemini's OpenTelemetry export, so there is no OTLP path for this runtime. Hooks are the only collection path. Beacon merges a managed hook block into Qwen's own `settings.json`, the same way the Claude Code and Factory Droid installers do.
```bash
beacon endpoint hooks install --harness qwen
@@ -21,7 +21,7 @@ Before enabling Qwen Code telemetry, make sure:
- Qwen Code is installed and available as the `qwen` executable, or has a local config directory at `~/.qwen`.
- `beacon endpoint install` has run so shared endpoint config and runtime log paths exist.
-- On Windows, `bash` is on `PATH`. Asymptote's hooks declare `shell: bash`. See [Hook shell](#hook-shell).
+- On Windows, `bash` is on `PATH`. Beacon's hooks declare `shell: bash`. See [Hook shell](#hook-shell).
- Project-level hooks are only used in a folder Qwen Code trusts. See [Known gaps](#known-gaps).
- Qwen Code is restarted after hook install or removal so new sessions load the updated settings.
@@ -36,11 +36,11 @@ Qwen Code reads settings from two locations, with project settings taking preced
User level is the default. A project-level install only takes effect once Qwen trusts the folder, and `beacon endpoint discover` reports on the user path only, so a project-level install does not appear in discovery output.
-`settings.json` also holds the user's own configuration, such as model, theme, MCP servers, and their own hooks. Install merges into that file rather than rewriting it: unrelated top-level keys are preserved, non-Asymptote hooks in the same event group survive, and a re-install replaces Asymptote's entries instead of adding a second copy. Asymptote recognizes its own entries by the `--platform qwen` argument in the hook command.
+`settings.json` also holds the user's own configuration, such as model, theme, MCP servers, and their own hooks. Install merges into that file rather than rewriting it: unrelated top-level keys are preserved, non-Beacon hooks in the same event group survive, and a re-install replaces Beacon's entries instead of adding a second copy. Beacon recognizes its own entries by the `--platform qwen` argument in the hook command.
### Registered events
-Asymptote registers every Qwen event that carries endpoint signal:
+Beacon registers every Qwen event that carries endpoint signal:
| Qwen event | Adapter subcommand | Matcher | Timeout |
|------------|--------------------|---------|---------|
@@ -58,22 +58,22 @@ Asymptote registers every Qwen event that carries endpoint signal:
A failed tool is a separate event in Qwen, so `PostToolUseFailure` is registered alongside `PostToolUse`. `PermissionRequest` is what makes an approval prompt observable. Events with no timeout listed use Qwen's own default of 60000 ms.
<Warning>
-**Qwen hook timeouts are milliseconds, not seconds.** Claude Code reads `timeout` as seconds, so a Claude-style `10` means 10 ms to Qwen. That is not enough time for a hook process to start, read stdin, and append to the log, so every tool event is killed mid-write while the install still reports success. Asymptote writes millisecond values for this runtime. Keep the unit in mind if you hand-edit them.
+**Qwen hook timeouts are milliseconds, not seconds.** Claude Code reads `timeout` as seconds, so a Claude-style `10` means 10 ms to Qwen. That is not enough time for a hook process to start, read stdin, and append to the log, so every tool event is killed mid-write while the install still reports success. Beacon writes millisecond values for this runtime. Keep the unit in mind if you hand-edit them.
</Warning>
### Hook shell
-Every hook Asymptote writes for Qwen carries `shell: bash`. Qwen accepts two values, `bash` and `powershell`, and only uses bash when the hook configuration asks for it. Claude Code, by contrast, runs hook commands through Git Bash on Windows regardless.
+Every hook Beacon writes for Qwen carries `shell: bash`. Qwen accepts two values, `bash` and `powershell`, and only uses bash when the hook configuration asks for it. Claude Code, by contrast, runs hook commands through Git Bash on Windows regardless.
-Asymptote quotes its hook command with POSIX single quotes, which is what a Windows path needs. If `shell` were left unset on Windows, a Node-hosted runtime would fall back to `cmd.exe`, where those quotes are literal characters and every hook fails to start while the install still reports success. On macOS and Linux, `bash` names the shell that would have run anyway.
+Beacon quotes its hook command with POSIX single quotes, which is what a Windows path needs. If `shell` were left unset on Windows, a Node-hosted runtime would fall back to `cmd.exe`, where those quotes are literal characters and every hook fails to start while the install still reports success. On macOS and Linux, `bash` names the shell that would have run anyway.
### Events that are not collected
-Asymptote does not register Qwen's fire-and-forget events: `MessageDisplay`, `StopFailure`, `PostCompact`, `SessionDelete`, and the todo pair. `MessageDisplay` alone fires roughly every 200 ms for the length of every reply, and it carries assistant text that Asymptote does not otherwise retain.
+Beacon does not register Qwen's fire-and-forget events: `MessageDisplay`, `StopFailure`, `PostCompact`, `SessionDelete`, and the todo pair. `MessageDisplay` alone fires roughly every 200 ms for the length of every reply, and it carries assistant text that Beacon does not otherwise retain.
## Discovery and status
-Asymptote detects Qwen Code through the `qwen` executable, and treats the `~/.qwen` config directory as an additional signal. Qwen Code installs through npm, so a version manager, a shell alias, or a per-project install can hide the binary from the endpoint process's `PATH` while `~/.qwen` is still present. The OpenCode, Cursor, Pi, and Hermes probes use the same fallback.
+Beacon detects Qwen Code through the `qwen` executable, and treats the `~/.qwen` config directory as an additional signal. Qwen Code installs through npm, so a version manager, a shell alias, or a per-project install can hide the binary from the endpoint process's `PATH` while `~/.qwen` is still present. The OpenCode, Cursor, Pi, and Hermes probes use the same fallback.
```bash title="Show Qwen Code discovery state"
beacon endpoint discover --all --json
@@ -85,12 +85,12 @@ Qwen Code reports as the `qwen_code` harness with capability `hooks`:
|------------------|---------|
| `missing` | No `~/.qwen/settings.json`, or it could not be read |
| `misconfigured` | `settings.json` exists but its JSON is invalid, so install will refuse to touch it |
-| `disabled` | Hooks are turned off by `disableAllHooks`, or the file exists with no Asymptote `--platform qwen` entry |
-| `enabled` | Asymptote's Qwen Code hooks are configured |
+| `disabled` | Hooks are turned off by `disableAllHooks`, or the file exists with no Beacon `--platform qwen` entry |
+| `enabled` | Beacon's Qwen Code hooks are configured |
-A settings file with hooks that are not Asymptote's reports `disabled` rather than `enabled`, because Asymptote is not collecting from them. Invalid JSON reports `misconfigured` rather than `missing`, because the file is there and install will refuse to write to it.
+A settings file with hooks that are not Beacon's reports `disabled` rather than `enabled`, because Beacon is not collecting from them. Invalid JSON reports `misconfigured` rather than `missing`, because the file is there and install will refuse to write to it.
-`disableAllHooks` is Qwen's own kill switch. Asymptote's hooks can be present in the file and still never run. Fix that in Qwen's settings, not by re-running the installer.
+`disableAllHooks` is Qwen's own kill switch. Beacon's hooks can be present in the file and still never run. Fix that in Qwen's settings, not by re-running the installer.
```bash title="Show Qwen Code hook status"
beacon endpoint hooks status --harness qwen
@@ -136,7 +136,7 @@ Both `qwen` and `qwen_code` arrive in practice. The hook path installs with `--p
### Tool taxonomy
-Qwen sends the Claude Code payload shape but not Claude's tool names. Its built-ins are snake_case ids inherited from the Gemini CLI it forked, and Asymptote matches them against a closed set:
+Qwen sends the Claude Code payload shape but not Claude's tool names. Its built-ins are snake_case ids inherited from the Gemini CLI it forked, and Beacon matches them against a closed set:
| Qwen built-in | Action | `file.operation` |
|---------------|--------|------------------|
@@ -151,13 +151,13 @@ Without this mapping the generic classifier is wrong in both directions. `write_
The set is closed rather than substring-matched so an MCP tool whose name contains `edit` or `glob` is not classified as a Qwen built-in. Qwen's non-filesystem built-ins (`web_fetch`, `web_search`, `todo_write`, `save_memory`, `task`, `skill`) stay on the shared path, where the MCP rule and the `tool.invoked` fallback already give the right answer.
-A failed tool is classified as a failure before its name is consulted, so a `write_file` that hit `EACCES` is recorded as `tool.failed` rather than a successful `file.modified`, and it does not go down the diff path. Asymptote reads three independent failure signals, since any of them can arrive alone: the `PostToolUseFailure` event name, a non-empty `error`, and Qwen's `is_interrupt` flag.
+A failed tool is classified as a failure before its name is consulted, so a `write_file` that hit `EACCES` is recorded as `tool.failed` rather than a successful `file.modified`, and it does not go down the diff path. Beacon reads three independent failure signals, since any of them can arrive alone: the `PostToolUseFailure` event name, a non-empty `error`, and Qwen's `is_interrupt` flag.
## Approvals and enforcement
-Approval telemetry comes from Qwen's `PermissionRequest` event and is recorded as observed, because an operator was actually asked. Asymptote does not synthesize an approval from a pre-tool notification for this runtime.
+Approval telemetry comes from Qwen's `PermissionRequest` event and is recorded as observed, because an operator was actually asked. Beacon does not synthesize an approval from a pre-tool notification for this runtime.
-Asymptote's `PreToolUse` hook answers with an empty object. Qwen's `PreToolUse` contract reads a decision from `hookSpecificOutput.permissionDecision`, where `allow` means run the tool without the usual approval prompt. A hook that answered `allow` would disarm the user's own permission prompts for every tool call. An empty object carries no decision, so Qwen's normal permission flow runs untouched.
+Beacon's `PreToolUse` hook answers with an empty object. Qwen's `PreToolUse` contract reads a decision from `hookSpecificOutput.permissionDecision`, where `allow` means run the tool without the usual approval prompt. A hook that answered `allow` would disarm the user's own permission prompts for every tool call. An empty object carries no decision, so Qwen's normal permission flow runs untouched.
Enforcement stays behind the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`), which is inert unless it names an executable and fails open on any error. When a provider denies a call, Qwen uses Claude Code's deny shape: `hookSpecificOutput.permissionDecision` with a `permissionDecisionReason`.
@@ -165,17 +165,17 @@ Enforcement stays behind the optional, off-by-default policy provider seam (`BEA
Qwen Code content is handled like every other runtime. Prompts, tool arguments, commands, paths, and diffs are retained in local or customer-controlled logs, with local secret redaction and per-string limits applied before writing, and a hash and byte count on each content-bearing event. Events over the 64 KiB limit drop raw and retained content, preserve stable metadata, and set `field_truncated`.
-Qwen carries signal with no endpoint-schema field of its own: `permission_mode` on every tool event, `source` on `SessionStart`, and `stop_hook_active` plus the `context_usage` / `context_limit` / `input_tokens` trio on `Stop`. Asymptote preserves the verbatim payload under `raw.qwen` rather than inventing schema fields for one runtime. It travels the event's normal path through sanitization, so `raw` is secret-redacted and string-limited like every other field, and it is the first thing dropped when an event exceeds the size ceiling.
+Qwen carries signal with no endpoint-schema field of its own: `permission_mode` on every tool event, `source` on `SessionStart`, and `stop_hook_active` plus the `context_usage` / `context_limit` / `input_tokens` trio on `Stop`. Beacon preserves the verbatim payload under `raw.qwen` rather than inventing schema fields for one runtime. It travels the event's normal path through sanitization, so `raw` is secret-redacted and string-limited like every other field, and it is the first thing dropped when an event exceeds the size ceiling.
## Known gaps
- **No OTLP path.** Qwen Code is a Gemini CLI fork without Gemini's OpenTelemetry export, so there is no collector endpoint to configure. Hooks are the only collection path, and `beacon endpoint install --harness qwen` says so rather than appearing to succeed.
- **Token spend is not collected, and cannot be.** Qwen's `Stop` payload carries no per-call token counts. Its `input_tokens` is the prompt for that turn, which in a multi-turn session already contains every prior turn, so summing it into `gen_ai.usage` would inflate a session's total by roughly the square of its length. Qwen Code therefore contributes no rows to the spend totals in `beacon token-usage`.
- **Context utilization is collected.** The same numbers describe how full the window was, which is a level rather than an amount, so they normalize into `gen_ai.context` instead: `input_tokens` becomes `gen_ai.context.used_tokens` and `context_limit` becomes `gen_ai.context.limit_tokens`. Qwen Code appears in the context utilization section of `beacon token-usage`, measured against the window it reported rather than a static model table. `context_usage` is the ratio of the two and stays in `raw.qwen` rather than being stored a second time in different units.
-- **A policy deny is honored in one of two phases.** The seam runs in both the `pre-tool` and `permission-request` hooks, and Asymptote returns Claude Code's deny shape, which Qwen's `PreToolUse` contract honors. Qwen's `PermissionRequest` event reads a differently shaped `hookSpecificOutput.decision` object, so a deny raised from that phase is not honored. Because the seam fails open, the cost is a deny that does not take effect on one phase, never a tool call blocked for the wrong reason.
-- **Assistant text is not collected.** `MessageDisplay` is not registered, so Asymptote records no assistant output or reasoning for Qwen Code. See [Events that are not collected](#events-that-are-not-collected).
+- **A policy deny is honored in one of two phases.** The seam runs in both the `pre-tool` and `permission-request` hooks, and Beacon returns Claude Code's deny shape, which Qwen's `PreToolUse` contract honors. Qwen's `PermissionRequest` event reads a differently shaped `hookSpecificOutput.decision` object, so a deny raised from that phase is not honored. Because the seam fails open, the cost is a deny that does not take effect on one phase, never a tool call blocked for the wrong reason.
+- **Assistant text is not collected.** `MessageDisplay` is not registered, so Beacon records no assistant output or reasoning for Qwen Code. See [Events that are not collected](#events-that-are-not-collected).
- **Project-level installs need a trusted folder.** Qwen gates project hooks behind trusted-folder status, so a user-level install is the one that works without further interaction. Grok Build has the same caveat.
-- **Payload fixtures are built from documentation.** Asymptote's Qwen fixtures are constructed from Qwen Code's published hooks documentation rather than captured from a running install. The documentation specifies the envelope and per-event fields precisely, so the shapes match the documented contract, but they are not evidence that a shipped build sends exactly this.
+- **Payload fixtures are built from documentation.** Beacon's Qwen fixtures are constructed from Qwen Code's published hooks documentation rather than captured from a running install. The documentation specifies the envelope and per-event fields precisely, so the shapes match the documented contract, but they are not evidence that a shipped build sends exactly this.
## Deployment notes
@@ -206,6 +206,6 @@ If Qwen telemetry is missing:
Return to the runtime support overview.
</Card>
<Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">
- See how Asymptote discovers and configures each runtime.
+ See how Beacon discovers and configures each runtime.
</Card>
</Columns>
diff --git a/docs/runtimes/senpi.mdx b/docs/runtimes/senpi.mdx
index 15f9ee35..8189fbf3 100644
--- a/docs/runtimes/senpi.mdx
+++ b/docs/runtimes/senpi.mdx
@@ -1,19 +1,19 @@
---
title: "Senpi"
-description: "Asymptote support details for the Senpi standalone edition of oh-my-openagent"
+description: "Beacon support details for the Senpi standalone edition of oh-my-openagent"
---
## Runtime overview
-Asymptote supports [Senpi](https://github.com/code-yeongyu/senpi), the standalone edition of [oh-my-openagent](https://github.com/code-yeongyu/oh-my-openagent) (OMO), through a managed local extension.
+Beacon supports [Senpi](https://github.com/code-yeongyu/senpi), the standalone edition of [oh-my-openagent](https://github.com/code-yeongyu/oh-my-openagent) (OMO), through a managed local extension.
<Note>
-oh-my-openagent ships three editions. **Ultimate** is a plugin riding [OpenCode](/runtimes/opencode); **Light** is a plugin riding [Codex CLI](/runtimes/codex-cli); both already flow through Asymptote's existing OpenCode and Codex CLI integrations, so no separate work is needed for them. **Senpi** is the one edition with no host of its own: an [in-flight fork of pi-mono](https://github.com/badlogic/pi-mono) that OMO brands and bundles its own extension into, distributed as the `omo` command. This page covers that edition only.
+oh-my-openagent ships three editions. **Ultimate** is a plugin riding [OpenCode](/runtimes/opencode); **Light** is a plugin riding [Codex CLI](/runtimes/codex-cli); both already flow through Beacon's existing OpenCode and Codex CLI integrations, so no separate work is needed for them. **Senpi** is the one edition with no host of its own: an [in-flight fork of pi-mono](https://github.com/badlogic/pi-mono) that OMO brands and bundles its own extension into, distributed as the `omo` command. This page covers that edition only.
</Note>
Senpi is a hard fork of pi-mono, as [Pi](/runtimes/pi), [Oh My Pi](/runtimes/oh-my-pi), and [Prime Agent](/runtimes/prime-agent) are. All four are supported separately and recorded under their own harness names, because they are separately installed products that one machine can run side by side.
-Senpi fits neither of Asymptote's two usual integration shapes. It has no hooks configuration file to merge a managed hook block into, and no OpenTelemetry export to point at the local collector. Its documented observation surface is the TypeScript extension API it inherited from Pi, so the integration is extension-shaped: one Asymptote-owned extension file forwards runtime events to `beacon-hooks`, the same shape as the [Pi](/runtimes/pi), [Oh My Pi](/runtimes/oh-my-pi), [Prime Agent](/runtimes/prime-agent), [OpenCode](/runtimes/opencode) and [Cline](/runtimes/cline) integrations.
+Senpi fits neither of Beacon's two usual integration shapes. It has no hooks configuration file to merge a managed hook block into, and no OpenTelemetry export to point at the local collector. Its documented observation surface is the TypeScript extension API it inherited from Pi, so the integration is extension-shaped: one Beacon-owned extension file forwards runtime events to `beacon-hooks`, the same shape as the [Pi](/runtimes/pi), [Oh My Pi](/runtimes/oh-my-pi), [Prime Agent](/runtimes/prime-agent), [OpenCode](/runtimes/opencode) and [Cline](/runtimes/cline) integrations.
```bash
beacon endpoint hooks install --harness omo
@@ -35,7 +35,7 @@ Before enabling Senpi telemetry, make sure:
## Collection path
-Asymptote's managed Senpi extension is a single TypeScript file at one of two auto-discovered extension locations:
+Beacon's managed Senpi extension is a single TypeScript file at one of two auto-discovered extension locations:
| Level | Extension path |
|-------|----------------|
@@ -48,15 +48,15 @@ User level is the default, because it follows the operator rather than one check
The project path keeps the `agent` segment, the same shape [Prime Agent](/runtimes/prime-agent) uses. Senpi's config directory name for this brand is `.omo`, and its own directory resolver joins the `agent` segment under the working directory just as it does under the home directory — where [Pi](/runtimes/pi) uses `.pi/extensions` and [Oh My Pi](/runtimes/oh-my-pi) uses `.omp/extensions` at project scope. A file written to `./.omo/extensions/` is never loaded.
</Warning>
-`OMO_CODING_AGENT_DIR` replaces the user-level agent directory outright, and Asymptote honors it — including a leading `~`, which the runtime expands before use. When it is unset, Asymptote falls back to `SENPI_CODING_AGENT_DIR` and then `PI_CODING_AGENT_DIR`, the same two legacy prefixes Senpi's own brand profile keeps readable: `SENPI` is the upstream engine's own name, and `PI` is pi-mono's. None of the three moves the project path, because Senpi does not consult any of them there.
+`OMO_CODING_AGENT_DIR` replaces the user-level agent directory outright, and Beacon honors it — including a leading `~`, which the runtime expands before use. When it is unset, Beacon falls back to `SENPI_CODING_AGENT_DIR` and then `PI_CODING_AGENT_DIR`, the same two legacy prefixes Senpi's own brand profile keeps readable: `SENPI` is the upstream engine's own name, and `PI` is pi-mono's. None of the three moves the project path, because Senpi does not consult any of them there.
-Asymptote identifies its own extension file by the marker `beacon-managed-omo-extension:v1`. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Asymptote telemetry. The marker is distinct from Pi's, Oh My Pi's, and Prime Agent's, so a file found at any of the four paths is attributed to the runtime that actually loads it.
+Beacon identifies its own extension file by the marker `beacon-managed-omo-extension:v1`. The version suffix is part of the contract with the extension source: it is what lets a repair recognize a stale file instead of leaving it in place. A `beacon.ts` without the marker belongs to somebody else, so install will not overwrite it and discovery does not report it as Beacon telemetry. The marker is distinct from Pi's, Oh My Pi's, and Prime Agent's, so a file found at any of the four paths is attributed to the runtime that actually loads it.
-Senpi has no OpenTelemetry export for Asymptote to configure, so there is no OTLP path for this runtime.
+Senpi has no OpenTelemetry export for Beacon to configure, so there is no OTLP path for this runtime.
## Discovery and status
-Asymptote detects Senpi through the `omo` executable, and treats the `~/.omo/agent` state directory as an additional signal. Senpi installed through npm into a directory this process did not inherit on `PATH` is not visible as an executable, because a shell alias, a version manager, or a per-project install can all hide it while the state directory is still present. The Pi, Oh My Pi, Prime Agent, OpenCode, Cursor, and Hermes probes use the same fallback.
+Beacon detects Senpi through the `omo` executable, and treats the `~/.omo/agent` state directory as an additional signal. Senpi installed through npm into a directory this process did not inherit on `PATH` is not visible as an executable, because a shell alias, a version manager, or a per-project install can all hide it while the state directory is still present. The Pi, Oh My Pi, Prime Agent, OpenCode, Cursor, and Hermes probes use the same fallback.
`senpi` is deliberately not probed for. It is the upstream engine's own binary name, and a machine can have plain, un-OMO'd Senpi installed without oh-my-openagent at all — probing for it here would claim an install this integration did not verify.
@@ -69,8 +69,8 @@ Senpi reports as the `omo_senpi` harness with capability `plugin`:
| Telemetry status | Meaning |
|------------------|---------|
| `missing` | No extension file at the user-level managed path |
-| `disabled` | A `beacon.ts` exists but carries no Asymptote marker, so it is somebody else's extension sharing the filename |
-| `enabled` | Asymptote's managed extension is in place |
+| `disabled` | A `beacon.ts` exists but carries no Beacon marker, so it is somebody else's extension sharing the filename |
+| `enabled` | Beacon's managed extension is in place |
An unmarked extension file reports `disabled` rather than `enabled`, because reporting it as enabled would show the runtime as covered while no events arrive.
@@ -117,7 +117,7 @@ Senpi content is handled like every other runtime. Prompts, command lines, comma
The extension itself sends nothing over the network. It spawns the local `beacon-hooks` binary with a fixed argv and writes the event to its stdin. A send that has not completed in two seconds is abandoned so Beacon cannot stall Senpi's agent loop, and a failure to spawn costs the event rather than the run.
-Senpi's own telemetry — the anonymous, PostHog-backed "OmO Native" analytics pipeline documented in its `senpi-telemetry.md` — is unrelated to this integration. It reports only aggregated buckets and counters with no raw content, and Asymptote neither reads from it nor writes to it.
+Senpi's own telemetry — the anonymous, PostHog-backed "OmO Native" analytics pipeline documented in its `senpi-telemetry.md` — is unrelated to this integration. It reports only aggregated buckets and counters with no raw content, and Beacon neither reads from it nor writes to it.
## Known gaps
diff --git a/docs/runtimes/vercel-fx.mdx b/docs/runtimes/vercel-fx.mdx
index 58a4ef4d..f404583a 100644
--- a/docs/runtimes/vercel-fx.mdx
+++ b/docs/runtimes/vercel-fx.mdx
@@ -1,20 +1,20 @@
---
title: "fx (Vercel Labs)"
-description: "Asymptote support details for fx (vercel-labs/fx) endpoint telemetry"
+description: "Beacon support details for fx (vercel-labs/fx) endpoint telemetry"
---
## Runtime overview
-Asymptote supports [fx](https://github.com/vercel-labs/fx), Vercel Labs' native coding agent, by reading the session records fx commits to disk.
+Beacon supports [fx](https://github.com/vercel-labs/fx), Vercel Labs' native coding agent, by reading the session records fx commits to disk.
-fx is the one supported runtime with no third-party observation surface at all. Its lifecycle hooks are Zig handlers compiled into the binary rather than commands a settings file can point at, it ships no OpenTelemetry export, and its plugin story is MCP — which describes the tools fx calls, not what fx did. What it does have is a durable, append-only record of every session under `~/.fx/sessions`, so Asymptote reads that.
+fx is the one supported runtime with no third-party observation surface at all. Its lifecycle hooks are Zig handlers compiled into the binary rather than commands a settings file can point at, it ships no OpenTelemetry export, and its plugin story is MCP — which describes the tools fx calls, not what fx did. What it does have is a durable, append-only record of every session under `~/.fx/sessions`, so Beacon reads that.
```bash
beacon endpoint fx sync
```
<Note>
-There is nothing to install into fx and nothing to configure inside it. Collection is an action you run rather than a setting Asymptote writes, which is why fx has a command instead of a `beacon endpoint hooks install --harness` target.
+There is nothing to install into fx and nothing to configure inside it. Collection is an action you run rather than a setting Beacon writes, which is why fx has a command instead of a `beacon endpoint hooks install --harness` target.
</Note>
## Prerequisites
@@ -27,7 +27,7 @@ Before collecting fx telemetry, make sure:
## Collection path
-Every fx event carries `harness.collection_method=poll`. Asymptote sees what a turn did once fx committed it, rather than observing the agent as it works. Stating the consequence plainly: nothing on this path can hold or deny a tool call, and nothing appears in the runtime log until the turn is committed.
+Every fx event carries `harness.collection_method=poll`. Beacon sees what a turn did once fx committed it, rather than observing the agent as it works. Stating the consequence plainly: nothing on this path can hold or deny a tool call, and nothing appears in the runtime log until the turn is committed.
| Item | Path |
|------|------|
@@ -40,17 +40,17 @@ A sweep reads each session's log only as far as the manifest's committed waterma
Re-reading is safe. Each event's dedup id comes from the record's own coordinates — session, log generation, sequence, and position within the turn — not from its content, so the same fx record maps to the same event on every sweep.
-fx has no OpenTelemetry export and no hook or plugin file for Asymptote to write, so there is no OTLP path and no managed file for this runtime.
+fx has no OpenTelemetry export and no hook or plugin file for Beacon to write, so there is no OTLP path and no managed file for this runtime.
## Discovery and status
-Asymptote detects fx through the `fx` executable, and treats `~/.fx` as an additional signal. fx installed through its setup script, a shell alias, or a per-user bin directory is often missing from the `PATH` the endpoint process inherited while its profile directory is still present. The Pi, Oh My Pi, OpenCode, Cursor, and Hermes probes use the same fallback.
+Beacon detects fx through the `fx` executable, and treats `~/.fx` as an additional signal. fx installed through its setup script, a shell alias, or a per-user bin directory is often missing from the `PATH` the endpoint process inherited while its profile directory is still present. The Pi, Oh My Pi, OpenCode, Cursor, and Hermes probes use the same fallback.
```bash title="Show fx discovery state"
beacon endpoint discover --all --json
```
-fx reports as the `vercel_fx` harness with capability `session_log`, which no other runtime has. The other capabilities describe something Asymptote writes into the runtime and the runtime then calls; fx offers nothing to write into, so there is no marker to check. That changes what "telemetry enabled" can honestly mean here: the only evidence telemetry is flowing is that a sweep has actually run and is level with the sessions on this machine.
+fx reports as the `vercel_fx` harness with capability `session_log`, which no other runtime has. The other capabilities describe something Beacon writes into the runtime and the runtime then calls; fx offers nothing to write into, so there is no marker to check. That changes what "telemetry enabled" can honestly mean here: the only evidence telemetry is flowing is that a sweep has actually run and is level with the sessions on this machine.
| Telemetry status | Meaning |
|------------------|---------|
@@ -105,12 +105,12 @@ The sweep is local and offline. It reads files already on this machine and write
## Known gaps
-- **No approvals.** fx persists permission feedback as text rather than a per-call decision, so there is nothing to record as an approval. Asymptote does not synthesize one, matching the [Cline](/runtimes/cline) and [Pi](/runtimes/pi) posture.
-- **No session end.** fx sessions are resumable, so there is no point at which fx declares one over. Asymptote does not invent a `session.ended` for a session that may be resumed tomorrow.
+- **No approvals.** fx persists permission feedback as text rather than a per-call decision, so there is nothing to record as an approval. Beacon does not synthesize one, matching the [Cline](/runtimes/cline) and [Pi](/runtimes/pi) posture.
+- **No session end.** fx sessions are resumable, so there is no point at which fx declares one over. Beacon does not invent a `session.ended` for a session that may be resumed tomorrow.
- **No enforcement, and none possible on this path.** A poll sees a committed record. Even the optional, off-by-default policy provider seam (`BEACON_POLICY_PROVIDER`) has nothing to attach to here, because the tool call already ran.
- **Events land a turn late.** fx commits a turn when it finishes, so telemetry arrives at turn granularity rather than as the agent works, and no sooner than the next sweep.
- **Nothing sweeps automatically.** `beacon endpoint fx sync` runs when you run it. Schedule it, or leave `--watch` running, or the runtime log stops at the last sweep.
-- **Unknown record kinds are skipped by name.** A kind fx adds later is skipped as unknown rather than mistaken for one Asymptote maps, so new fx behavior needs a Beacon update before it appears.
+- **Unknown record kinds are skipped by name.** A kind fx adds later is skipped as unknown rather than mistaken for one Beacon maps, so new fx behavior needs a Beacon update before it appears.
## Deployment notes
diff --git a/docs/runtimes/vscode.mdx b/docs/runtimes/vscode.mdx
index 30375a21..0fd8dd5c 100644
--- a/docs/runtimes/vscode.mdx
+++ b/docs/runtimes/vscode.mdx
@@ -1,11 +1,11 @@
---
title: "VS Code"
-description: "Asymptote support details for VS Code Copilot and hook telemetry"
+description: "Beacon support details for VS Code Copilot and hook telemetry"
---
## Runtime overview
-Asymptote supports VS Code primarily through GitHub Copilot Chat OpenTelemetry export to Asymptote's localhost collector. VS Code hooks are also supported as an optional preview path when your organization allows them.
+Beacon supports VS Code primarily through GitHub Copilot Chat OpenTelemetry export to Beacon's localhost collector. VS Code hooks are also supported as an optional preview path when your organization allows them.
## Prerequisites
@@ -24,7 +24,7 @@ Use OpenTelemetry as the primary VS Code collection path:
beacon endpoint install --harness vscode
```
-This configures VS Code Copilot Chat to export OTLP/HTTP to Asymptote's local collector at `http://127.0.0.1:4318`. Reload VS Code after setup so the Copilot extension reinitializes its telemetry configuration.
+This configures VS Code Copilot Chat to export OTLP/HTTP to Beacon's local collector at `http://127.0.0.1:4318`. Reload VS Code after setup so the Copilot extension reinitializes its telemetry configuration.
Validate recent activity:
@@ -38,7 +38,7 @@ OTel-derived events use `harness.name=vscode_copilot`.
VS Code hooks are currently in preview, and the `Chat: Use Hooks` setting may be disabled or managed by your organization. Use hooks only when you want extra lifecycle/tool detail or cross-agent coverage beyond Copilot's OTel stream.
-Before installing hooks, confirm `Chat: Use Hooks` is enabled in VS Code settings. If this setting is unchecked and marked as managed by your organization, VS Code will not execute `.github/hooks/*.json` hook files even if Asymptote installs them successfully.
+Before installing hooks, confirm `Chat: Use Hooks` is enabled in VS Code settings. If this setting is unchecked and marked as managed by your organization, VS Code will not execute `.github/hooks/*.json` hook files even if Beacon installs them successfully.
<img src="/images/vscode-chat-use-hooks-setting.png" alt="VS Code settings showing Chat: Use Hooks disabled and managed by organization, while Chat: Use Claude Hooks is enabled." />
@@ -59,7 +59,7 @@ Hook-derived events use `harness.name=vscode`. They can capture VS Code lifecycl
## Discovery and status
-Asymptote detects VS Code through the `code` executable or the VS Code user settings directory. It checks whether Copilot Chat OTel is enabled, whether the exporter is `otlp-http`, and whether the endpoint points to Asymptote's local OTLP HTTP receiver.
+Beacon detects VS Code through the `code` executable or the VS Code user settings directory. It checks whether Copilot Chat OTel is enabled, whether the exporter is `otlp-http`, and whether the endpoint points to Beacon's local OTLP HTTP receiver.
Use:
@@ -82,13 +82,13 @@ beacon endpoint hooks status --harness vscode --level project
## Deployment notes
-For managed endpoint deployments, include `vscode` in the endpoint harness list when you want Asymptote to manage VS Code Copilot OTel settings:
+For managed endpoint deployments, include `vscode` in the endpoint harness list when you want Beacon to manage VS Code Copilot OTel settings:
-```bash title="For managed endpoint deployments, include vscode in the endpoint harness list when you want Asymptote to manage VS Code Copilot OTel settings"
+```bash title="For managed endpoint deployments, include vscode in the endpoint harness list when you want Beacon to manage VS Code Copilot OTel settings"
beacon endpoint install --system --harness claude,codex,vscode
```
-If hooks are allowed by organization policy, install them separately in the logged-in user's context or within the target project. Do not rely on hooks as the primary VS Code signal path; Copilot OTel is preferred and should provide most of the session, prompt, model, and tool visibility needed for Asymptote.
+If hooks are allowed by organization policy, install them separately in the logged-in user's context or within the target project. Do not rely on hooks as the primary VS Code signal path; Copilot OTel is preferred and should provide most of the session, prompt, model, and tool visibility needed for Beacon.
## Related
diff --git a/docs/sdk/index.mdx b/docs/sdk/index.mdx
index 47c8f1e9..6281393e 100644
--- a/docs/sdk/index.mdx
+++ b/docs/sdk/index.mdx
@@ -1,19 +1,19 @@
---
-title: "Asymptote Observe SDK"
+title: "Beacon Observe SDK"
description: "Instrument cloud-hosted agent applications with Beacon-compatible telemetry"
---
## SDK overview
-Asymptote Observe instruments cloud-hosted agent applications and exports OpenTelemetry traces that remain compatible with Beacon's normalized endpoint event model. Use it for servers, serverless functions, workers, and hosted agent platforms where installing the local Beacon endpoint agent is not the right fit.
+Beacon Observe instruments cloud-hosted agent applications and exports OpenTelemetry traces that remain compatible with Beacon's normalized endpoint event model. Use it for servers, serverless functions, workers, and hosted agent platforms where installing the local Beacon endpoint agent is not the right fit.
-Hosted Observe ingest is available through Asymptote Managed. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
+Hosted Observe ingest is available through Beacon Managed. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
The open-source `agent-beacon` repository currently includes the TypeScript package `@asymptote/sdk`. It provides the `Observe` module for OpenTelemetry setup, common AI SDK instrumentation, manual span wrappers, lifecycle helpers, and Beacon compatibility attributes.
-## What Asymptote captures
+## What Beacon captures
-Asymptote Observe is OpenTelemetry-first. It records supported model calls, agent turns, tool calls, custom orchestration steps, errors, and Beacon compatibility attributes as spans that can be sent to Asymptote Managed hosted Observe or a customer-managed OTLP collector.
+Beacon Observe is OpenTelemetry-first. It records supported model calls, agent turns, tool calls, custom orchestration steps, errors, and Beacon compatibility attributes as spans that can be sent to Beacon Managed hosted Observe or a customer-managed OTLP collector.
Supported cloud SDK paths:
@@ -48,24 +48,24 @@ Supported cloud SDK paths:
## Choose the right surface
-Use the SDK when agent activity runs in application code you control. Use Asymptote endpoint or CI collection when activity happens in a local harness or ephemeral build job.
+Use the SDK when agent activity runs in application code you control. Use Beacon endpoint or CI collection when activity happens in a local harness or ephemeral build job.
| Environment | Recommended surface |
| --- | --- |
-| Node.js services, workers, and hosted agent apps | [Asymptote Observe SDK](/sdk/quickstart) |
+| Node.js services, workers, and hosted agent apps | [Beacon Observe SDK](/sdk/quickstart) |
| Next.js and serverless functions | [Next.js and serverless guide](/sdk/integrations-nextjs-serverless) |
-| Local coding and knowledge-worker harnesses | [Asymptote endpoint agent](/runtimes) |
+| Local coding and knowledge-worker harnesses | [Beacon endpoint agent](/runtimes) |
| CI jobs running Claude Code | [`beacon ci`](/cli/ci) |
## SDK and endpoint telemetry
-The SDK and Asymptote endpoint telemetry share an event contract, but they target different deployment surfaces.
+The SDK and Beacon endpoint telemetry share an event contract, but they target different deployment surfaces.
| Surface | Purpose |
| --- | --- |
-| Asymptote Observe SDK | Cloud application telemetry exported as OpenTelemetry traces |
-| Asymptote endpoint agent | Local endpoint telemetry collected from supported agent harnesses |
-| Asymptote CI | Ephemeral CI telemetry captured for a single job |
+| Beacon Observe SDK | Cloud application telemetry exported as OpenTelemetry traces |
+| Beacon endpoint agent | Local endpoint telemetry collected from supported agent harnesses |
+| Beacon CI | Ephemeral CI telemetry captured for a single job |
| Beacon JSONL schema | Normalized event model used by local logs, dashboards, and downstream security pipelines |
-Cloud SDK spans set `beacon.origin=cloud` and can include Beacon compatibility attributes such as `beacon.harness.name`, `beacon.event.action`, `beacon.tool.name`, and `beacon.prompt.text`. The same attributes can be consumed by Beacon-compatible collectors or Asymptote Managed Observe ingest.
+Cloud SDK spans set `beacon.origin=cloud` and can include Beacon compatibility attributes such as `beacon.harness.name`, `beacon.event.action`, `beacon.tool.name`, and `beacon.prompt.text`. The same attributes can be consumed by Beacon-compatible collectors or Beacon Managed Observe ingest.
diff --git a/docs/sdk/instrumentation.mdx b/docs/sdk/instrumentation.mdx
index 7ed0575d..5607d5c4 100644
--- a/docs/sdk/instrumentation.mdx
+++ b/docs/sdk/instrumentation.mdx
@@ -1,6 +1,6 @@
---
title: "Instrumentation"
-description: "Initialize Asymptote Observe and configure TypeScript SDK instrumentation"
+description: "Initialize Beacon Observe and configure TypeScript SDK instrumentation"
---
## Instrumentation model
@@ -23,8 +23,8 @@ By default, the SDK creates OpenAI and Anthropic OpenLLMetry instrumentations wh
| Option | Purpose |
| --- | --- |
-| `apiKey` | Asymptote Managed hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
-| `baseUrl` | Asymptote Managed hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
+| `apiKey` | Beacon Managed hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
+| `baseUrl` | Beacon Managed hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
| `otlpEndpoint` | Explicit OTLP/HTTP endpoint. Defaults to `OTEL_EXPORTER_OTLP_ENDPOINT` |
| `headers` | Additional exporter headers |
| `serviceName` | OpenTelemetry service name. Defaults to `OTEL_SERVICE_NAME` or `asymptote-app` |
diff --git a/docs/sdk/integrations-anthropic.mdx b/docs/sdk/integrations-anthropic.mdx
index 6e18e6eb..2929871a 100644
--- a/docs/sdk/integrations-anthropic.mdx
+++ b/docs/sdk/integrations-anthropic.mdx
@@ -1,19 +1,19 @@
---
title: "Anthropic"
-description: "Instrument Anthropic SDK calls with Asymptote Observe"
+description: "Instrument Anthropic SDK calls with Beacon Observe"
---
## Integration overview
-Use this integration when your application calls Anthropic's `@anthropic-ai/sdk` TypeScript package directly. Asymptote Observe uses OpenLLMetry's Anthropic instrumentation so Anthropic model calls flow through the same exporter and Beacon-compatible attribute path as the rest of your agent telemetry.
+Use this integration when your application calls Anthropic's `@anthropic-ai/sdk` TypeScript package directly. Beacon Observe uses OpenLLMetry's Anthropic instrumentation so Anthropic model calls flow through the same exporter and Beacon-compatible attribute path as the rest of your agent telemetry.
## Overview
-Initialize Asymptote Observe before creating the Anthropic client when possible. The instrumentation captures supported Anthropic SDK spans without changing the way you call `anthropic.messages.create()`.
+Initialize Beacon Observe before creating the Anthropic client when possible. The instrumentation captures supported Anthropic SDK spans without changing the way you call `anthropic.messages.create()`.
Using Claude Agent SDK instead of the direct provider SDK? See [Claude Agent SDK](/sdk/integrations-claude-agent-sdk).
-## What Asymptote captures
+## What Beacon captures
- Anthropic model calls emitted by the OpenLLMetry Anthropic instrumentation.
- OpenTelemetry resource attributes such as service name, SDK version, `beacon.origin=cloud`, and export mode.
@@ -25,7 +25,7 @@ Using Claude Agent SDK instead of the direct provider SDK? See [Claude Agent SDK
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `@anthropic-ai/sdk` installed.
-- `ASYMPTOTE_API_KEY` set for Asymptote Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get an Asymptote Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Anthropic client"
npm install @asymptote/sdk @anthropic-ai/sdk
@@ -33,7 +33,7 @@ npm install @asymptote/sdk @anthropic-ai/sdk
Set environment variables:
-```bash title="Set Asymptote Managed and Anthropic environment variables"
+```bash title="Set Beacon Managed and Anthropic environment variables"
export ASYMPTOTE_API_KEY=...
export ANTHROPIC_API_KEY=...
```
@@ -73,7 +73,7 @@ const message = await anthropic.messages.create({
await Observe.flush();
```
-All supported Anthropic SDK calls are now traced through the configured Asymptote exporter.
+All supported Anthropic SDK calls are now traced through the configured Beacon exporter.
## Already-loaded clients
@@ -97,7 +97,7 @@ Observe.initialize({
## Existing OpenTelemetry providers
-If your application already owns OpenTelemetry setup, register only Asymptote's Anthropic instrumentation with your existing provider.
+If your application already owns OpenTelemetry setup, register only Beacon's Anthropic instrumentation with your existing provider.
```typescript title="Register Anthropic instrumentation on an existing provider" lines
import { registerInstrumentations } from "@opentelemetry/instrumentation";
diff --git a/docs/sdk/integrations-claude-agent-sdk.mdx b/docs/sdk/integrations-claude-agent-sdk.mdx
index dbf5a36a..72b27c65 100644
--- a/docs/sdk/integrations-claude-agent-sdk.mdx
+++ b/docs/sdk/integrations-claude-agent-sdk.mdx
@@ -1,11 +1,11 @@
---
title: "Claude Agent SDK"
-description: "Wrap Claude Agent SDK query functions with Asymptote Observe"
+description: "Wrap Claude Agent SDK query functions with Beacon Observe"
---
## Integration overview
-Use this integration when your application runs Claude Agent SDK queries through `@anthropic-ai/claude-agent-sdk`. Asymptote Observe can wrap the query function to create a Beacon-compatible root span for each agent turn.
+Use this integration when your application runs Claude Agent SDK queries through `@anthropic-ai/claude-agent-sdk`. Beacon Observe can wrap the query function to create a Beacon-compatible root span for each agent turn.
## Overview
@@ -13,7 +13,7 @@ Claude Agent SDK integration is currently a query wrapper, not a custom hook ada
For direct Anthropic API calls through `@anthropic-ai/sdk`, use [Anthropic](/sdk/integrations-anthropic).
-## What Asymptote captures
+## What Beacon captures
- A `claude_agent_sdk.query` span for wrapped query calls.
- `beacon.harness.name=claude_agent_sdk`.
@@ -26,7 +26,7 @@ For direct Anthropic API calls through `@anthropic-ai/sdk`, use [Anthropic](/sdk
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `@anthropic-ai/claude-agent-sdk` installed.
-- `ASYMPTOTE_API_KEY` set for Asymptote Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get an Asymptote Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Claude Agent SDK"
npm install @asymptote/sdk @anthropic-ai/claude-agent-sdk
@@ -34,7 +34,7 @@ npm install @asymptote/sdk @anthropic-ai/claude-agent-sdk
Set environment variables:
-```bash title="Set the Asymptote Managed API key"
+```bash title="Set the Beacon Managed API key"
export ASYMPTOTE_API_KEY=...
```
diff --git a/docs/sdk/integrations-custom-agent-steps.mdx b/docs/sdk/integrations-custom-agent-steps.mdx
index 275ceae2..82c7ac63 100644
--- a/docs/sdk/integrations-custom-agent-steps.mdx
+++ b/docs/sdk/integrations-custom-agent-steps.mdx
@@ -11,7 +11,7 @@ Use `Observe.observe()` for orchestration steps, tool execution, policy checks,
Custom agent steps are the fallback integration path for frameworks, internal tools, and orchestration code without a dedicated adapter. Wrap the function you control and add Beacon compatibility attributes that describe what happened.
-## What Asymptote captures
+## What Beacon captures
- A span for each wrapped function call.
- Input count and output type unless disabled.
@@ -23,7 +23,7 @@ Custom agent steps are the fallback integration path for frameworks, internal to
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- The agent framework, tool client, or internal orchestration code you want to wrap.
-- `ASYMPTOTE_API_KEY` set for Asymptote Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get an Asymptote Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK"
npm install @asymptote/sdk
@@ -31,7 +31,7 @@ npm install @asymptote/sdk
Set an export destination:
-```bash title="Set the Asymptote Managed API key"
+```bash title="Set the Beacon Managed API key"
export ASYMPTOTE_API_KEY=...
```
diff --git a/docs/sdk/integrations-nextjs-serverless.mdx b/docs/sdk/integrations-nextjs-serverless.mdx
index 1429c4d1..15a5a75b 100644
--- a/docs/sdk/integrations-nextjs-serverless.mdx
+++ b/docs/sdk/integrations-nextjs-serverless.mdx
@@ -1,6 +1,6 @@
---
title: "Next.js And Serverless"
-description: "Initialize Asymptote Observe in Next.js and short-lived serverless runtimes"
+description: "Initialize Beacon Observe in Next.js and short-lived serverless runtimes"
---
## Serverless setup
@@ -13,7 +13,7 @@ Initialize `Observe` once in the earliest Node-only entrypoint. In Next.js, use
- A Next.js app or another serverless Node.js runtime.
- `@asymptote/sdk` installed.
- Any agent SDKs used by your route handlers, such as Vercel AI SDK.
-- `ASYMPTOTE_API_KEY` set for Asymptote Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get an Asymptote Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Vercel AI SDK"
npm install @asymptote/sdk ai @ai-sdk/openai
@@ -65,7 +65,7 @@ If the runtime owns a long-lived process, reserve `Observe.shutdown()` for grace
## Customer-managed OTLP
-Serverless and preview environments can send to a customer-managed collector by setting `OTEL_EXPORTER_OTLP_ENDPOINT` instead of Asymptote Managed hosted Observe credentials.
+Serverless and preview environments can send to a customer-managed collector by setting `OTEL_EXPORTER_OTLP_ENDPOINT` instead of Beacon Managed hosted Observe credentials.
```bash title="Set the OTLP endpoint"
export OTEL_EXPORTER_OTLP_ENDPOINT=https://otel.example.com
@@ -79,4 +79,4 @@ Observe.initialize({
});
```
-Explicit OTLP export does not require an Asymptote Managed `ASYMPTOTE_API_KEY`.
+Explicit OTLP export does not require a Beacon Managed `ASYMPTOTE_API_KEY`.
diff --git a/docs/sdk/integrations-openai.mdx b/docs/sdk/integrations-openai.mdx
index d9415016..f1b47788 100644
--- a/docs/sdk/integrations-openai.mdx
+++ b/docs/sdk/integrations-openai.mdx
@@ -1,17 +1,17 @@
---
title: "OpenAI"
-description: "Instrument OpenAI SDK calls with Asymptote Observe"
+description: "Instrument OpenAI SDK calls with Beacon Observe"
---
## Integration overview
-Use this integration when your application calls the `openai` JavaScript package directly. Asymptote Observe uses OpenLLMetry's OpenAI instrumentation so OpenAI spans flow through the same exporter and Beacon-compatible attribute path as the rest of your agent telemetry.
+Use this integration when your application calls the `openai` JavaScript package directly. Beacon Observe uses OpenLLMetry's OpenAI instrumentation so OpenAI spans flow through the same exporter and Beacon-compatible attribute path as the rest of your agent telemetry.
## Overview
-Initialize Asymptote Observe before creating the OpenAI client when possible. The instrumentation captures supported OpenAI SDK spans without changing the way you call `openai`.
+Initialize Beacon Observe before creating the OpenAI client when possible. The instrumentation captures supported OpenAI SDK spans without changing the way you call `openai`.
-## What Asymptote captures
+## What Beacon captures
- OpenAI model calls emitted by the OpenLLMetry OpenAI instrumentation.
- OpenTelemetry resource attributes such as service name, SDK version, `beacon.origin=cloud`, and export mode.
@@ -23,7 +23,7 @@ Initialize Asymptote Observe before creating the OpenAI client when possible. Th
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `openai` installed.
-- `ASYMPTOTE_API_KEY` set for Asymptote Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get an Asymptote Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and OpenAI client"
npm install @asymptote/sdk openai
@@ -31,7 +31,7 @@ npm install @asymptote/sdk openai
Set environment variables:
-```bash title="Set Asymptote Managed and OpenAI environment variables"
+```bash title="Set Beacon Managed and OpenAI environment variables"
export ASYMPTOTE_API_KEY=...
export OPENAI_API_KEY=...
```
@@ -65,7 +65,7 @@ const response = await openai.responses.create({
await Observe.flush();
```
-All supported OpenAI SDK calls are now traced through the configured Asymptote exporter.
+All supported OpenAI SDK calls are now traced through the configured Beacon exporter.
## Already-loaded clients
@@ -131,7 +131,7 @@ const reviewPullRequest = Observe.observe(
## Existing OpenTelemetry providers
-If your application already owns OpenTelemetry setup, register Asymptote's OpenAI instrumentation with your existing provider instead of calling `Observe.initialize()` twice.
+If your application already owns OpenTelemetry setup, register Beacon's OpenAI instrumentation with your existing provider instead of calling `Observe.initialize()` twice.
```typescript title="Register OpenAI instrumentation on an existing provider" lines
import { registerInstrumentations } from "@opentelemetry/instrumentation";
diff --git a/docs/sdk/integrations-vercel-ai-sdk.mdx b/docs/sdk/integrations-vercel-ai-sdk.mdx
index cdf6a3e5..d497c79d 100644
--- a/docs/sdk/integrations-vercel-ai-sdk.mdx
+++ b/docs/sdk/integrations-vercel-ai-sdk.mdx
@@ -1,19 +1,19 @@
---
title: "Vercel AI SDK"
-description: "Use Asymptote Observe tracing with Vercel AI SDK telemetry"
+description: "Use Beacon Observe tracing with Vercel AI SDK telemetry"
---
## Integration overview
-Pass the Asymptote tracer into AI SDK telemetry so model calls and tool loops stay in the same trace.
+Pass the Beacon tracer into AI SDK telemetry so model calls and tool loops stay in the same trace.
## Overview
-AI SDK exposes OpenTelemetry hooks through `experimental_telemetry`. Asymptote Observe is OpenTelemetry-first, so you can trace `generateText`, `streamText`, tool loops, and custom orchestration by passing `Observe.getTracer()` to each AI SDK call you want captured.
+AI SDK exposes OpenTelemetry hooks through `experimental_telemetry`. Beacon Observe is OpenTelemetry-first, so you can trace `generateText`, `streamText`, tool loops, and custom orchestration by passing `Observe.getTracer()` to each AI SDK call you want captured.
This page covers Node.js usage. For framework placement and serverless flushing, see [Next.js and serverless](/sdk/integrations-nextjs-serverless).
-## What Asymptote captures
+## What Beacon captures
- AI SDK spans emitted when `experimental_telemetry.isEnabled` is `true`.
- Model call spans for supported `generate*` and `stream*` operations.
@@ -26,15 +26,15 @@ This page covers Node.js usage. For framework placement and serverless flushing,
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `ai` and an AI SDK model provider package installed.
-- `ASYMPTOTE_API_KEY` set for Asymptote Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get an Asymptote Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Vercel AI SDK"
npm install @asymptote/sdk ai @ai-sdk/openai
```
-Set environment variables for Asymptote and your provider:
+Set environment variables for Beacon and your provider:
-```bash title="Set Asymptote Managed and OpenAI environment variables"
+```bash title="Set Beacon Managed and OpenAI environment variables"
export ASYMPTOTE_API_KEY=...
export OPENAI_API_KEY=...
```
diff --git a/docs/sdk/integrations.mdx b/docs/sdk/integrations.mdx
index a0792292..8018a376 100644
--- a/docs/sdk/integrations.mdx
+++ b/docs/sdk/integrations.mdx
@@ -1,23 +1,23 @@
---
title: "Agent SDK Integrations"
-description: "Choose an Asymptote Observe integration path for AI SDKs and agent orchestration"
+description: "Choose a Beacon Observe integration path for AI SDKs and agent orchestration"
---
## Integration overview
-Asymptote Observe traces supported LLM providers, agent SDKs, and orchestration code through OpenTelemetry. Initialize `Observe`, configure the integration path for the SDK you use, and your model calls or agent turns can flow to Asymptote Managed hosted Observe or a customer-managed OTLP collector.
+Beacon Observe traces supported LLM providers, agent SDKs, and orchestration code through OpenTelemetry. Initialize `Observe`, configure the integration path for the SDK you use, and your model calls or agent turns can flow to Beacon Managed hosted Observe or a customer-managed OTLP collector.
Browse the integrations below to see setup instructions, what is captured, and troubleshooting guidance.
<Columns cols={2}>
<Card title="Anthropic" icon="robot" href="/sdk/integrations-anthropic">
- Instrument `@anthropic-ai/sdk` model calls with Asymptote Observe.
+ Instrument `@anthropic-ai/sdk` model calls with Beacon Observe.
</Card>
<Card title="Claude Agent SDK" icon="robot" href="/sdk/integrations-claude-agent-sdk">
Wrap Claude Agent SDK query functions with Beacon-compatible prompt spans.
</Card>
<Card title="OpenAI" icon="brain" href="/sdk/integrations-openai">
- Instrument `openai` package model calls with Asymptote Observe.
+ Instrument `openai` package model calls with Beacon Observe.
</Card>
<Card title="Vercel AI SDK" icon="bolt" href="/sdk/integrations-vercel-ai-sdk">
Pass `Observe.getTracer()` into AI SDK telemetry for model calls and tool loops.
@@ -34,7 +34,7 @@ Browse the integrations below to see setup instructions, what is captured, and t
All integration paths start by installing and initializing the SDK:
-Hosted Observe export requires an Asymptote Managed API key. To get `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
+Hosted Observe export requires a Beacon Managed API key. To get `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK"
npm install @asymptote/sdk
@@ -48,7 +48,7 @@ Observe.initialize({
});
```
-See the [SDK quickstart](/sdk/quickstart) for Asymptote Managed hosted Observe, customer-managed OTLP, custom exporter, and shutdown options.
+See the [SDK quickstart](/sdk/quickstart) for Beacon Managed hosted Observe, customer-managed OTLP, custom exporter, and shutdown options.
## Not supported yet
diff --git a/docs/sdk/lifecycle.mdx b/docs/sdk/lifecycle.mdx
index 0bf657ae..2d428f46 100644
--- a/docs/sdk/lifecycle.mdx
+++ b/docs/sdk/lifecycle.mdx
@@ -1,6 +1,6 @@
---
title: "SDK Lifecycle"
-description: "Flush and shut down Asymptote Observe tracing"
+description: "Flush and shut down Beacon Observe tracing"
---
## Lifecycle overview
diff --git a/docs/sdk/observe.mdx b/docs/sdk/observe.mdx
index a5eff978..850441ac 100644
--- a/docs/sdk/observe.mdx
+++ b/docs/sdk/observe.mdx
@@ -1,6 +1,6 @@
---
title: "Observe"
-description: "Wrap custom agent functions with Asymptote Observe"
+description: "Wrap custom agent functions with Beacon Observe"
---
## Observe API
diff --git a/docs/sdk/quickstart.mdx b/docs/sdk/quickstart.mdx
index be1d7721..58c18af4 100644
--- a/docs/sdk/quickstart.mdx
+++ b/docs/sdk/quickstart.mdx
@@ -1,6 +1,6 @@
---
title: "SDK Quickstart"
-description: "Install and initialize the Asymptote TypeScript SDK"
+description: "Install and initialize the Beacon TypeScript SDK"
---
## Setup flow
@@ -17,13 +17,13 @@ The package requires Node.js 20 or newer.
## 2. Configure export
-Choose Asymptote Managed hosted Observe or a customer-managed OTLP endpoint.
+Choose Beacon Managed hosted Observe or a customer-managed OTLP endpoint.
### Hosted Observe
-Hosted Observe requires an Asymptote Managed account. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact), then initialize `Observe` as early as possible in your application startup:
+Hosted Observe requires a Beacon Managed account. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact), then initialize `Observe` as early as possible in your application startup:
-```bash title="Set the Asymptote Managed API key"
+```bash title="Set the Beacon Managed API key"
export ASYMPTOTE_API_KEY=...
```
@@ -49,7 +49,7 @@ The SDK appends `/v1/observe` when the configured base URL or endpoint does not
### Customer-managed OTLP
-Use an explicit OTLP endpoint when traces should go to a local or customer-managed collector instead of Asymptote Managed hosted Observe:
+Use an explicit OTLP endpoint when traces should go to a local or customer-managed collector instead of Beacon Managed hosted Observe:
```bash title="Set the OTLP endpoint"
export OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318
@@ -63,7 +63,7 @@ Observe.initialize({
});
```
-Explicit OTLP export does not require an Asymptote Managed API key.
+Explicit OTLP export does not require a Beacon Managed API key.
## 3. Create a first trace
@@ -103,7 +103,7 @@ await Observe.flush();
| --- | --- |
| 1 | `initialize({ otlpEndpoint })` |
| 2 | `OTEL_EXPORTER_OTLP_ENDPOINT` |
-| 3 | Asymptote Managed hosted `baseUrl` when `apiKey` or `ASYMPTOTE_API_KEY` is present |
+| 3 | Beacon Managed hosted `baseUrl` when `apiKey` or `ASYMPTOTE_API_KEY` is present |
If neither hosted credentials nor an explicit OTLP endpoint is configured, use a custom exporter or disable the default exporter.
diff --git a/docs/sdk/reference.mdx b/docs/sdk/reference.mdx
index 806d8ed2..7d037582 100644
--- a/docs/sdk/reference.mdx
+++ b/docs/sdk/reference.mdx
@@ -1,6 +1,6 @@
---
title: "SDK Reference"
-description: "Asymptote Observe TypeScript API, options, and Beacon compatibility attributes"
+description: "Beacon Observe TypeScript API, options, and Beacon compatibility attributes"
---
## API surface
@@ -22,14 +22,14 @@ For guided setup, start with [SDK Quickstart](/sdk/quickstart), [Instrumentation
| `Observe.flush()` | Force flush finished spans |
| `Observe.shutdown()` | Disable instrumentations, shut down the provider, and allow later reinitialization |
-Function exports are also available for the same operations, including `initialize`, `getTracer`, `observe`, `patch`, `initializeAsymptoteInstrumentations`, `wrapClaudeAgentQuery`, `flush`, `shutdown`, `isInitialized`, and `resolveExporterConfig`.
+Function exports are also available for the same operations, including `initialize`, `getTracer`, `observe`, `patch`, `initializeBeaconInstrumentations`, `wrapClaudeAgentQuery`, `flush`, `shutdown`, `isInitialized`, and `resolveExporterConfig`.
## Initialize options
| Option | Purpose |
| --- | --- |
-| `apiKey` | Asymptote Managed hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
-| `baseUrl` | Asymptote Managed hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
+| `apiKey` | Beacon Managed hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
+| `baseUrl` | Beacon Managed hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
| `otlpEndpoint` | Explicit OTLP/HTTP endpoint. Defaults to `OTEL_EXPORTER_OTLP_ENDPOINT` |
| `headers` | Additional exporter headers |
| `serviceName` | OpenTelemetry service name. Defaults to `OTEL_SERVICE_NAME` or `asymptote-app` |
@@ -60,7 +60,7 @@ Function exports are also available for the same operations, including `initiali
| Mode | How it is selected |
| --- | --- |
-| `hosted` | Asymptote Managed `apiKey` or `ASYMPTOTE_API_KEY` is present and no explicit OTLP endpoint is configured |
+| `hosted` | Beacon Managed `apiKey` or `ASYMPTOTE_API_KEY` is present and no explicit OTLP endpoint is configured |
| `otlp` | `otlpEndpoint` or `OTEL_EXPORTER_OTLP_ENDPOINT` is present |
| `custom` | Default exporter is disabled or a custom span exporter is provided |
@@ -145,6 +145,6 @@ The wire-compatible Beacon event identity remains:
Instrument `openai` package model calls.
</Card>
<Card title="Vercel AI SDK" icon="bolt" href="/sdk/integrations-vercel-ai-sdk">
- Pass the Asymptote tracer into AI SDK telemetry.
+ Pass the Beacon tracer into AI SDK telemetry.
</Card>
</Columns>
diff --git a/docs/security/data-flow-threat-model.mdx b/docs/security/data-flow-threat-model.mdx
index 05533993..67c924be 100644
--- a/docs/security/data-flow-threat-model.mdx
+++ b/docs/security/data-flow-threat-model.mdx
@@ -28,17 +28,17 @@ flowchart LR
| Local storage | Beacon writes one JSON object per line to `runtime.jsonl` | Filesystem permissions and log ownership |
| Local inspection | The dashboard reads the runtime log over a loopback-only service | Local browser to local dashboard service |
| Optional forwarding | Wazuh, Elastic/Filebeat, Datadog Agent, Sumo Logic, Rapid7, Microsoft Sentinel, AWS S3, Google Cloud Storage, Splunk HEC, Falcon LogScale HEC, or customer-managed shippers read or receive events | Customer-managed network and SIEM boundary |
-| Asymptote Managed forwarding (opt-in) | A Vector forwarder posts runtime and inventory JSONL over HTTPS to Asymptote's ingest service with a per-device key issued after browser approval | Endpoint to Asymptote-run service; identity derived from the key, revocable from the dashboard |
+| Beacon Managed forwarding (opt-in) | A Vector forwarder posts runtime and inventory JSONL over HTTPS to Beacon's ingest service with a per-device key issued after browser approval | Endpoint to Beacon-run service; identity derived from the key, revocable from the dashboard |
## Threat model
| Risk | Design response |
|------|-----------------|
-| Unintended hosted telemetry | Normal endpoint collection writes local JSONL and does not require a Beacon-hosted account, remote policy fetch, or external network dependency. Asymptote Managed forwarding starts only after a member of the organization approves the specific device in the browser, forwards only lines written after that approval, and stops within a minute of revocation |
+| Unintended hosted telemetry | Normal endpoint collection writes local JSONL and does not require a Beacon-hosted account, remote policy fetch, or external network dependency. Beacon Managed forwarding starts only after a member of the organization approves the specific device in the browser, forwards only lines written after that approval, and stops within a minute of revocation |
| Network exposure of collectors | Default OTLP receivers bind to `127.0.0.1` rather than an externally reachable interface |
| Over-collection of prompt or diff content | Scope supported runtimes and hook deployment deliberately before rollout, and review destination access for retained local telemetry |
| Secret leakage in retained content | Beacon applies redaction, sanitization, truncation, and event-size limits before writing supported content fields |
-| Destination credential exposure | Persistent endpoint file-based destinations tail local JSONL, so Beacon endpoint configuration does not store Elastic, Datadog, Sumo Logic, Rapid7, Microsoft Sentinel, AWS, or Google Cloud credentials. Optional Splunk and Falcon tokens live in collector configuration. The Asymptote Managed device key is a per-machine credential stored in a `0600` secrets file read through Vector's secret backend, never in `config.json`, `vector.toml`, or the process environment; it grants only the right to post events for one device and is revocable from the dashboard. Self-serve cloud-agent uploads are a separate proof-of-concept path: scoped GCS or AWS credentials are injected into the provider-managed sandbox as runtime secrets and must be rotated and access-reviewed. |
+| Destination credential exposure | Persistent endpoint file-based destinations tail local JSONL, so Beacon endpoint configuration does not store Elastic, Datadog, Sumo Logic, Rapid7, Microsoft Sentinel, AWS, or Google Cloud credentials. Optional Splunk and Falcon tokens live in collector configuration. The Beacon Managed device key is a per-machine credential stored in a `0600` secrets file read through Vector's secret backend, never in `config.json`, `vector.toml`, or the process environment; it grants only the right to post events for one device and is revocable from the dashboard. Self-serve cloud-agent uploads are a separate proof-of-concept path: scoped GCS or AWS credentials are injected into the provider-managed sandbox as runtime secrets and must be rotated and access-reviewed. |
| Removal uncertainty | Endpoint uninstall removes managed service and configuration state, with explicit `--keep-logs` and `--keep-config` exceptions |
## Current boundaries
diff --git a/docs/security/data-inventory.mdx b/docs/security/data-inventory.mdx
index ea0124fa..c30720c2 100644
--- a/docs/security/data-inventory.mdx
+++ b/docs/security/data-inventory.mdx
@@ -94,7 +94,7 @@ By default, snapshots include config-file metadata, MCP server metadata, skill m
| `prompt` | Prompt text when retention allows it | `text` |
| `content` | Content handling state | `retention`, `included`, `redacted`, `truncated` |
| `destination` | Output or validation destination state | `type`, `mode`, `status` |
-| `tenant` | Added by Asymptote's ingest service to forwarded events only; never written locally | `organization_id`, `device_id`, `user_id`, `key_id`, `received_at` |
+| `tenant` | Added by Beacon's ingest service to forwarded events only; never written locally | `organization_id`, `device_id`, `user_id`, `key_id`, `received_at` |
| `health` | Endpoint or component health state | `component`, `status`, `reason` |
Top-level `model`, `repository`, `branch`, `message`, `raw`, and `field_truncated` fields can add shared context across entities. Content-bearing fields follow the configured retention mode.
diff --git a/docs/security/endpoint-operations.mdx b/docs/security/endpoint-operations.mdx
index 5fa0f26e..093de30b 100644
--- a/docs/security/endpoint-operations.mdx
+++ b/docs/security/endpoint-operations.mdx
@@ -81,9 +81,9 @@ Optional network behavior is customer configured:
| Falcon LogScale HEC | Optional collector exporter sends events to the configured Falcon LogScale HEC endpoint |
| Endpoint self-update | Optional updater mode fetches the release manifest and signed package assets when manually invoked or explicitly enabled |
| Customer-managed forwarding | Customer shipper, agent, or SIEM pipeline reads local JSONL |
-| Asymptote managed ingest (opt-in) | After a member of the organization approves the device in the browser (`beacon endpoint connect`), a Vector forwarder posts the runtime and inventory JSONL over HTTPS to Asymptote's ingest service with a per-device key; revocable from the dashboard, effective within about a minute |
+| Beacon managed ingest (opt-in) | After a member of the organization approves the device in the browser (`beacon endpoint connect`), a Vector forwarder posts the runtime and inventory JSONL over HTTPS to Beacon's ingest service with a per-device key; revocable from the dashboard, effective within about a minute |
-Beacon itself does not store Elastic cluster URLs or credentials, Datadog API keys or site configuration, Sumo Source URLs, tokens, collector configuration, or Rapid7 webhook URLs. Splunk HEC and Falcon LogScale HEC tokens are stored only in local collector configuration when those optional destinations are enabled. The Asymptote device key is stored only in `asymptote/vector-secrets.json` (mode `0600`, inside a `0700` directory) under the endpoint base directory, read by Vector through its secret backend; `config.json` holds only the non-secret device and organization ids, and the key is never printed by any command.
+Beacon itself does not store Elastic cluster URLs or credentials, Datadog API keys or site configuration, Sumo Source URLs, tokens, collector configuration, or Rapid7 webhook URLs. Splunk HEC and Falcon LogScale HEC tokens are stored only in local collector configuration when those optional destinations are enabled. The Beacon device key is stored only in `asymptote/vector-secrets.json` (mode `0600`, inside a `0700` directory) under the endpoint base directory, read by Vector through its secret backend; `config.json` holds only the non-secret device and organization ids, and the key is never printed by any command.
Endpoint package self-updates are off by default. When an admin enables
`check-only` or `auto`, the updater's network access is limited to the configured
@@ -92,7 +92,7 @@ local-only.
## Uninstall guarantees
-`beacon endpoint uninstall` unloads the local Beacon service and removes managed endpoint files. Beacon removes files listed in its install manifest, including managed config, collector config, and service files. Unless `--keep-logs` is set, it also removes the configured runtime JSONL log. A connected endpoint's Asymptote forwarder service and `asymptote/` directory (Vector config, buffer, enrollment record, device key) are removed too, except that `--keep-config` keeps the enrollment record and device key; `beacon endpoint disconnect` does only that part.
+`beacon endpoint uninstall` unloads the local Beacon service and removes managed endpoint files. Beacon removes files listed in its install manifest, including managed config, collector config, and service files. Unless `--keep-logs` is set, it also removes the configured runtime JSONL log. A connected endpoint's Beacon forwarder service and `asymptote/` directory (Vector config, buffer, enrollment record, device key) are removed too, except that `--keep-config` keeps the enrollment record and device key; `beacon endpoint disconnect` does only that part.
Use retention flags when you intentionally want to preserve evidence or configuration:
diff --git a/docs/security/index.mdx b/docs/security/index.mdx
index 6d76f1b5..04dfc9b3 100644
--- a/docs/security/index.mdx
+++ b/docs/security/index.mdx
@@ -5,7 +5,7 @@ description: "Deploy Beacon endpoint telemetry and forward events into security
Beacon gives Security and IT teams local endpoint visibility into supported [agent harnesses](/runtimes). It captures supported activity, normalizes it into a stable endpoint event schema, and writes JSONL for local inspection or customer-managed forwarding.
-Beacon is local-only by default. The endpoint agent does not require a Beacon-hosted account, remote policy fetch, or external network dependency during normal collection. Use [Asymptote Managed](/deployment/managed) when you need centralized retention, search, governance, investigations, access control, or rollout support.
+Beacon is local-only by default. The endpoint agent does not require a Beacon-hosted account, remote policy fetch, or external network dependency during normal collection. Use [Beacon Managed](/deployment/managed) when you need centralized retention, search, governance, investigations, access control, or rollout support.
## Rollout path
@@ -34,7 +34,7 @@ Before broad rollout, document these decisions:
| Install mode | Local evaluation, root-managed system install, or MDM package rollout. |
| Event destination | Local JSONL only, Wazuh localfile, supported forwarding destination, object storage, or customer-managed pipeline. |
| Access and retention | Who can read local logs, how long downstream systems retain events, and which teams own review. |
-| Managed handoff | Whether the rollout now needs centralized visibility, policy controls, investigations, SSO/RBAC, or private infrastructure. |
+| Managed handoff | Whether the rollout now needs centralized visibility, investigations, SSO/RBAC, or private infrastructure. |
## Validation signals
@@ -77,11 +77,11 @@ Also review [Agent harness integrations](/runtimes) to confirm supported runtime
## When to move to managed
-Open Source works well when your team wants local endpoint telemetry and controls the downstream destination. Consider [Asymptote Managed](/deployment/managed) when you need:
+Open Source works well when your team wants local endpoint telemetry and controls the downstream destination. Consider [Beacon Managed](/deployment/managed) when you need:
- centralized ingest, retention, search, and detections
- fleet-wide visibility across endpoints, users, and teams
-- policy controls, identity mapping, approvals, and investigation workflows
+- identity mapping, approval visibility, and investigation workflows
- SSO, RBAC, audit trails, onboarding, and rollout support
For dedicated infrastructure, stricter data boundaries, or residency requirements, ask about Private Deployment. [Contact us](https://asymptotelabs.ai/contact) to discuss Managed or Private Deployment.
diff --git a/docs/security/policy.mdx b/docs/security/policy.mdx
index b967a052..3529fd46 100644
--- a/docs/security/policy.mdx
+++ b/docs/security/policy.mdx
@@ -3,8 +3,6 @@ title: "Security Policy"
description: "Security contact, vulnerability disclosure, and release verification policy"
---
-## Policy controls
-
Use this page for security contact, vulnerability disclosure, and release verification details for Beacon endpoint deployments.
## Security contact
@@ -23,7 +21,7 @@ When reporting a vulnerability, include enough detail for the security team to r
- Expected impact and whether the issue is already being exploited.
- Any constraints on coordinated disclosure timing.
-Asymptote asks reporters to avoid accessing data that does not belong to them, disrupting customer systems, or publicly disclosing an issue before the security team has had time to investigate and coordinate remediation.
+Beacon asks reporters to avoid accessing data that does not belong to them, disrupting customer systems, or publicly disclosing an issue before the security team has had time to investigate and coordinate remediation.
## Release signing and verification
@@ -46,7 +44,7 @@ For managed macOS rollouts, deploy the signed and notarized `.pkg` through Jamf
## Related
<Columns cols={2}>
- <Card title="Asymptote Open Source" icon="download" href="/deployment/open-source">
+ <Card title="Beacon" icon="download" href="/deployment/open-source">
Install Beacon, review archive contents, and verify the CLI version.
</Card>
<Card title="MDM deployment" icon="laptop-mobile" href="/mdm">
diff --git a/docs/security/retention-redaction.mdx b/docs/security/retention-redaction.mdx
index 5ef12000..18b046b1 100644
--- a/docs/security/retention-redaction.mdx
+++ b/docs/security/retention-redaction.mdx
@@ -75,10 +75,10 @@ and customer-managed shippers read the resulting local JSONL. Supported cloud
agents upload a compressed snapshot of their sandbox-local JSONL directly to
customer-managed GCS or S3. Splunk HEC and Falcon LogScale HEC forwarding
receive the same normalized collector output according to the configured
-endpoint pipeline. Asymptote managed ingest, when a device has been connected,
+endpoint pipeline. Beacon managed ingest, when a device has been connected,
forwards the runtime and inventory JSONL lines written after approval exactly as
stored locally, so the same retention and redaction settings govern what
-reaches the Asymptote dashboard.
+reaches the Beacon dashboard.
Review runtime scope, artifact access, destination permissions, and downstream retention before rollout so retained content matches your approved telemetry policy.
diff --git a/docs/support/troubleshooting.mdx b/docs/support/troubleshooting.mdx
index 66afbb3c..6a358ccf 100644
--- a/docs/support/troubleshooting.mdx
+++ b/docs/support/troubleshooting.mdx
@@ -1,30 +1,14 @@
---
title: "Common Issues"
-description: "Solutions for common issues when setting up and using Asymptote."
+description: "Solutions for common issues when setting up and using Beacon."
---
<AccordionGroup>
- <Accordion title="Scans aren't triggering on pull requests">
- - Verify the Asymptote GitHub App is installed on the target repository.
- - Check that webhook deliveries are succeeding under your GitHub App settings → **Recent Deliveries**.
- - Confirm the `ASYMPTOTE_API_KEY` secret is set in your repository under **Settings → Secrets and variables → Actions**.
- </Accordion>
- <Accordion title="Status checks are stuck as pending">
- - Confirm your `ASYMPTOTE_API_KEY` secret is correctly set and hasn't expired.
- - Large pull requests may take a few extra minutes to process.
- - Check the Actions tab in your repository to see if the workflow is running.
- </Accordion>
- <Accordion title="Permission errors on the GitHub App">
- Re-install the Asymptote GitHub App and ensure the correct repositories are selected. See the [GitHub integration page](/deployment/hosting-options) for a full list of required permissions.
- </Accordion>
<Accordion title="My coding agent isn't being intercepted">
- Ensure Asymptote is configured for your agent. See the [Coding Agent Integrations](/runtimes/cursor) docs for setup instructions for your specific tool.
- </Accordion>
- <Accordion title="How do I disconnect a repository?">
- In GitHub: **Repository → Settings → GitHub Apps → Asymptote Security**, then suspend or uninstall the app.
+ Ensure Beacon is configured for your agent. See the [Coding Agent Integrations](/runtimes/cursor) docs for setup instructions for your specific tool.
</Accordion>
<Accordion title="How do I disconnect all repositories?">
- In GitHub: **Organization → Settings → GitHub Apps → Asymptote Security**, then suspend or uninstall the app.
+ In GitHub: **Organization → Settings → GitHub Apps → Beacon Security**, then suspend or uninstall the app.
</Accordion>
<Accordion title="How do I remove agent hooks from my local machine?">
Use `beacon endpoint hooks uninstall` for whichever hook harness you set up:
@@ -55,7 +39,7 @@ description: "Solutions for common issues when setting up and using Asymptote."
After uninstalling hooks, restart the affected agent or IDE so new sessions pick up the updated hook configuration. See the [hook command docs](/cli/hooks#beacon-endpoint-hooks-uninstall) for supported harness names and flags.
</Accordion>
<Accordion title="beacon endpoint install fails with Collector ports are not listening">
- A user-mode collector cannot run beside a system-mode one, because the collector health-check port `127.0.0.1:13133` is fixed, so the install rolls back; run `beacon endpoint install --user --no-start` or uninstall the system endpoint first. Tracked as [GitHub issue #447](https://github.com/Asymptote-Labs/agent-beacon/issues/447).
+ A user-mode collector cannot run beside a system-mode one, because the collector health-check port `127.0.0.1:13133` is fixed, so the install rolls back; run `beacon endpoint install --user --no-start` or uninstall the system endpoint first. Tracked as [GitHub issue #447](https://github.com/asymptote-labs/agent-beacon/issues/447).
</Accordion>
<Accordion title="Endpoint package self-update is not running">
For signed macOS package installs, self-update is off by default. Check the
diff --git a/docs/telemetry-schema/event-schema.mdx b/docs/telemetry-schema/event-schema.mdx
index 7a8a348b..57a9b764 100644
--- a/docs/telemetry-schema/event-schema.mdx
+++ b/docs/telemetry-schema/event-schema.mdx
@@ -119,7 +119,7 @@ This lets teams use OpenTelemetry-native data without giving up a security-focus
## Why it matters
-The normalized schema is the contract between collection, detection, investigation, and forwarding. It lets Asymptote:
+The normalized schema is the contract between collection, detection, investigation, and forwarding. It lets Beacon:
- Correlate agent activity across local endpoints, ephemeral CI jobs, and cloud agent sessions.
- Write detections once against stable fields instead of per-runtime payloads.
diff --git a/docs/telemetry-schema/normalization.mdx b/docs/telemetry-schema/normalization.mdx
index 278018e4..a5408074 100644
--- a/docs/telemetry-schema/normalization.mdx
+++ b/docs/telemetry-schema/normalization.mdx
@@ -30,7 +30,7 @@ Qwen Code is the runtime that forced the split. Its `Stop` hook reports the prom
Both halves are required before either is recorded. `input_tokens` is also the ecosystem's usual name for a genuine additive usage count, so a reported limit beside it is what distinguishes a payload describing window occupancy from one reporting spend. Without that pairing the rule would reclassify other runtimes' spend as context.
-A reported `limit_tokens` also takes precedence over Asymptote's static context-window table when computing utilization, because it reflects the tier the call actually ran under rather than the default for a model name.
+A reported `limit_tokens` also takes precedence over Beacon's static context-window table when computing utilization, because it reflects the tier the call actually ran under rather than the default for a model name.
## Source mapping