The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
refresh beacon docs
Justin D'Souza79256188873d
diff --git a/CLAUDE.md b/CLAUDE.mdindex 550a3f45..a82da3d9 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -25,7 +25,7 @@ Do not recreate or depend on removed `asymptote` mirror trees. Keep new work foc- Beacon is visibility-first endpoint telemetry for local AI agent runtimes, not a hosted policy service or general endpoint protection product.- Preserve the local-only default. The public Beacon build must not require a hosted account, remote policy fetch, hosted dashboard, or external network dependency during normal hook execution, and hooks themselves never touch the network.- `beacon login` is the account-identity channel for interactive users and is required by the interactive `beacon endpoint install` wizard. It uses browser PKCE against beacon.sh and stores the scoped CLI token only in `~/.beacon/auth/session.json` (0600 under a 0700 directory). Signing in alone never starts forwarding. User-mode `beacon endpoint connect` may send that token once to `POST /api/cli/enroll/account` to authorize minting a separate device ingest key; never copy the account token into endpoint config, Vector, hook environments, logs, or command output. System/root/package/MDM/CI/piped-stdin/dry-run installs stay noninteractive and account-free.-- Beacon Managed forwarding (`cli/beacon/internal/endpoint/asymptote`, `beacon endpoint connect`, `beacon endpoint asymptote`) is Vector-shaped: Beacon writes local JSONL, Vector ships only new lines after connection, and the `bcn_device_*` key stays only in `<BaseDir>/asymptote/vector-secrets.json` via Vector's secret backend. The onboarding wizard preselects Managed but connect remains a separate action. Standard mode ships locally sanitized retained content; metadata-only uses local Vector transforms to remove prompts, responses, reasoning, tool arguments/results, command output, raw fields, diffs, inventory content, and MCP definitions before buffering/upload. Keep the ingest URL `https://`, the wire contract aligned with `beacon-ingest` (`/v1/ingest/{runtime,inventory}` and `/v1/ingest/health`), and do not add another endpoint network channel. The cloud-sandbox shuttle is the bounded exception: only with `BEACON_ORIGIN=cloud`, it can upload new runtime lines to GCS, S3, or the same Beacon ingest contract because no Vector/service manager/browser/persistent disk exists there.+- Beacon Managed forwarding (`cli/beacon/internal/endpoint/asymptote`, `beacon endpoint connect`, `beacon endpoint asymptote`) is Vector-shaped: Beacon writes local JSONL, Vector ships runtime lines only from the connection point forward and reads inventory from the beginning to establish the endpoint's current baseline, and the `bcn_device_*` key stays only in `<BaseDir>/asymptote/vector-secrets.json` via Vector's secret backend. The onboarding wizard preselects Managed but connect remains a separate action. Standard mode ships locally sanitized retained content; metadata-only uses local Vector transforms to remove prompts, responses, reasoning, tool arguments/results, command output, raw fields, diffs, inventory content, and MCP definitions before buffering/upload. Keep the ingest URL `https://`, the wire contract aligned with `beacon-ingest` (`/v1/ingest/{runtime,inventory}` and `/v1/ingest/health`), and do not add another endpoint network channel. The cloud-sandbox shuttle is the bounded exception: only with `BEACON_ORIGIN=cloud`, it can upload new runtime lines to GCS, S3, or the same Beacon ingest contract because no Vector/service manager/browser/persistent disk exists there.- `beacon endpoint install` has a full-screen onboarding wizard on interactive user TTYs. It signs in, preselects Beacon Managed, requires an explicit choice to opt out to Local, and asks Managed users to choose Standard or Metadata-only privacy. Accepting Managed still only records intent and prints `beacon endpoint connect`, so no telemetry moves during onboarding. Explicit `install --connect` still enrolls after installation. The wizard is skipped for system/root/CI/piped-stdin/dry-run or `BEACON_ONBOARDING=0`; those unattended paths must never gain an account or browser dependency. Legacy `BEACON_ONBOARDING_EMAIL`/`USAGE` submissions remain only for fleet compatibility. Implementation lives in `cli/beacon/internal/onboarding` and `cli/beacon/cmd/endpoint_onboarding.go`; keep `docs/cli/endpoint-onboarding.mdx` in sync.- Do not add dependency vulnerability scanning, OSV/GHSA lookups, package remediation, or other vulnerability-enforcement flows to the public hook path.- Do not add broad runtime enforcement unless explicitly requested. Current control behavior is limited to hook-native approvals/denials exposed by supported agent runtimes.diff --git a/README.md b/README.mdindex e1d74964..882da034 100644--- a/README.md+++ b/README.md@@ -23,7 +23,10 @@<a href="https://docs.beacon.sh/cli">Commands</a></p>-Beacon captures **agent session history** across Claude Code, Cursor, Codex, OpenCode, and 20+ other harnesses, then turns useful workflows, corrections, and debugging patterns into reusable knowledge for future agents.+Beacon captures the **session telemetry each configured runtime exposes** across+Claude Code, Cursor, Codex, OpenCode, and 20+ other harnesses. Its explicit,+review-gated memory workflow can turn selected workflows, corrections, and+debugging patterns into reusable knowledge for future agents.**A problem solved by one agent shouldn't need to be learned from scratch by another.**@@ -31,14 +34,18 @@ Beacon captures **agent session history** across Claude Code, Cursor, Codex, Ope## Beacon Overview-Beacon is an open-source memory layer for AI coding agents that learns from your work across Claude Code, Cursor, Codex, OpenCode, and 20+ other harnesses. It captures full session history, identifies useful workflows, corrections, and debugging patterns, and makes that knowledge reusable by future agents. Built for developers who want agent knowledge to compound across tools instead of disappearing when a session ends.+Beacon is an open-source memory layer for AI coding agents that collects available+session telemetry across Claude Code, Cursor, Codex, OpenCode, and 20+ other+harnesses. Developers can evaluate selected traces, review candidate workflows,+corrections, and debugging patterns, and approve useful knowledge for reuse by+future agents.**Key Capabilities:**- **Cross-harness history** - sessions from Claude Code, Cursor, Codex, OpenCode, Cline, and 20+ harnesses in one place-- **Knowledge that compounds** - workflows, corrections, debugging patterns, and repo conventions that survive beyond a single session+- **Knowledge that compounds** - explicitly evaluated and approved workflows, corrections, debugging patterns, and repo conventions that survive beyond a single session- **Shared agent memory** - reviewed knowledge future agents can retrieve through MCP or Agent Skills-- **Exact session replay** - prompts, responses, tools, commands, edits, approvals, MCP activity, and tokens in one trace+- **Runtime-aware trace review** - prompts, responses, tools, commands, edits, approvals, MCP activity, and tokens where the configured runtime surface exposes them- **Local-first portability** - durable JSONL, explicit destinations, and no harness lock-in---@@ -101,9 +108,11 @@ msiexec /i BeaconEndpointAgent-<version>-x64.msi /qn### 2. Use your agents normally-Open Claude Code, Cursor, Codex, or any other supported harness.+Open a configured runtime. The default endpoint install configures Claude Code+and Codex CLI; Cursor and other supported harnesses may require their documented+hook, plugin, OTLP, or session-sync setup.-Beacon continuously captures your session history in the background.+Beacon captures the telemetry that runtime exposes through its configured surface.### 3. Explore your history@@ -124,7 +133,10 @@ Or inspect the raw event stream:```> [!NOTE]-> Local until connected: signing in or accepting the preselected Managed option does not enable forwarding. The separate connect step offers Standard or Metadata-only upload privacy.+> Local until connected: signing in or accepting the preselected Managed option+> does not enable forwarding. The onboarding wizard records Standard or+> Metadata-only privacy; `beacon endpoint connect` uses that choice, or+> `--privacy-mode` overrides it.Inspect the account used during interactive setup:diff --git a/cli/beacon/README.md b/cli/beacon/README.mdindex 3be98db6..a10eab3d 100644--- a/cli/beacon/README.md+++ b/cli/beacon/README.md@@ -529,8 +529,10 @@ device key in a `0600` secrets file and runs Vector as theJSONL producer and Vector does the network. Standard privacy forwards locallysanitized retained content; `--privacy-mode metadata-only` strips retained text,raw fields, diffs, inventory content, and MCP definitions locally before upload.-Only lines written after connection are shipped, and revoking the device stops ingestion within-about a minute. Vector 0.50 or newer is required: `/opt/beacon/bin/vector` from+Runtime forwarding starts at the end of the existing runtime log, while inventory+starts at the beginning of `inventory_state.jsonl` to send the endpoint's current+inventory baseline. Revoking the device stops ingestion within about a minute.+Vector 0.50 or newer is required: `/opt/beacon/bin/vector` fromthe signed package, the `beacon-vector` keg that `brew install beacon` pulls in onmacOS, any other Vector 0.50+ already on the machine, or the Linux package fromvector.dev. The Homebrew mirror is named `beacon-vector` rather than `vector`, anddiff --git a/cli/beacon/cmd/endpoint.go b/cli/beacon/cmd/endpoint.goindex dc1ffa3d..350075a0 100644--- a/cli/beacon/cmd/endpoint.go+++ b/cli/beacon/cmd/endpoint.go@@ -423,7 +423,7 @@ func init() {endpointInstallCmd.Flags().BoolVar(&endpointOpts.noStart, "no-start", false, "Write files without starting the collector service")endpointInstallCmd.Flags().StringVar(&endpointOpts.serviceKind, "service", "", "Service manager to use: auto (default), launchd, systemd, or none for a supervised collector process")endpointInstallCmd.Flags().BoolVar(&endpointOpts.dryRun, "dry-run", false, "Print planned actions without changing endpoint files or services")- endpointInstallCmd.Flags().BoolVar(&endpointOpts.connect, "connect", false, "After installing, connect this endpoint to Asymptote managed ingest (opens a browser to approve the device)")+ endpointInstallCmd.Flags().BoolVar(&endpointOpts.connect, "connect", false, "After installing, attempt to connect this endpoint to Beacon Managed (user mode uses the signed-in account; system mode opens browser approval)")endpointOnboardingCmd.Flags().BoolVar(&endpointOpts.onboardingReset, "reset", false, "Clear the onboarding record so the question is asked again")endpointOnboardingCmd.Flags().BoolVar(&endpointOpts.onboardingResend, "resend", false, "Retry a signup that could not be delivered")endpointOnboardingCmd.Flags().BoolVar(&endpointOpts.jsonOutput, "json", false, "Print the onboarding record as JSON")diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdxindex 041ed157..427bee65 100644--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@ -28,6 +28,10 @@ Stay up to date with the latest changes to the Agent Beacon CLI.filters, paging, and event detail. Redirected input or output falls back to abounded tab-separated list, while `beacon endpoint traces` remains the stableJSON and scripting interface.+- **Safer relayed memory project resolution** · Dashboard and MCP memory lookups+ resolve relayed paths only against projects already stored in local memory,+ choose the most-specific matching project, avoid filesystem and Git reads, and+ fail closed when no known project matches.- **Account sign-in and safer first-run onboarding** · `beacon login`, `whoami`,and `logout` add browser PKCE account authentication without enabling forwarding.Interactive user installs now use a full-screen wizard that requires sign-in,diff --git a/docs/cli/account-auth.mdx b/docs/cli/account-auth.mdxindex 217bbbf8..3f98c142 100644--- a/docs/cli/account-auth.mdx+++ b/docs/cli/account-auth.mdx@@ -23,12 +23,18 @@ beacon logoutbeacon login```-For SSH sessions or terminals that cannot open a browser:+For a terminal that cannot open a browser automatically:```bashbeacon login --no-browser```+This is still a loopback-callback PKCE flow, not a device-code flow. Open the URL+in a browser that can reach the same machine's callback listener. For a remote SSH+session, use a browser on the remote host or forward the callback port shown in+the printed URL; opening it on an unrelated workstation without port forwarding+redirects to that workstation's localhost and cannot complete the remote login.+The session is stored at `~/.beacon/auth/session.json` in a `0700` directory with file mode `0600`. Human and JSON command output never includes the access token. Tokens expire rather than refreshing indefinitely; run `beacon login` again after expiry.Use `--auth-url` or `BEACON_AUTH_URL` only for a self-hosted or development authentication service. Non-loopback authentication URLs must use HTTPS.diff --git a/docs/cli/asymptote.mdx b/docs/cli/asymptote.mdxindex 334ef240..bd51dae7 100644--- a/docs/cli/asymptote.mdx+++ b/docs/cli/asymptote.mdx@@ -11,7 +11,13 @@ The hand-run pack uses Standard privacy and forwards locally sanitized linesunchanged. Use [`beacon endpoint connect --privacy-mode metadata-only`](/cli/endpoint-connect#privacy-modes)when Beacon should render the local metadata-only transforms for you.-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.+This is the one destination that sends telemetry to a Beacon-run endpoint. It is+opt-in and revocable: nothing is forwarded until enrollment has issued a device+key and Vector has started. In user mode, `beacon endpoint connect` uses the+signed-in CLI account to authorize that key without another browser approval;+system mode uses browser approval. `beacon endpoint connect` performs 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.diff --git a/docs/cli/endpoint-config.mdx b/docs/cli/endpoint-config.mdxindex 4bfd80f9..2431db22 100644--- a/docs/cli/endpoint-config.mdx+++ b/docs/cli/endpoint-config.mdx@@ -1,17 +1,19 @@---title: "beacon endpoint config"-description: "Inspect, validate, and update Beacon endpoint configuration"+description: "Inspect Beacon endpoint configuration and validate destination settings"---## Command overview-`beacon endpoint config` inspects and safely updates the local Beacon endpoint configuration.+`beacon endpoint config` inspects the local Beacon endpoint configuration and+validates its destination settings. It does not edit the configuration.```bash title="Command syntax"beacon endpoint config [command]```-Use this command group when you need to review the effective endpoint configuration or validate config file contents without reinstalling the endpoint agent.+Use this command group when you need to review the effective endpoint configuration+or validate configured destinations without reinstalling the endpoint agent.## Commands@@ -58,13 +60,19 @@ sudo beacon endpoint config show --system## beacon endpoint config validate-`beacon endpoint config validate` validates the endpoint configuration file.+`beacon endpoint config validate` loads the effective endpoint configuration and+validates its destination settings.```bash title="Run the validation check"beacon endpoint config validate```-Validation checks endpoint and destination configuration. For example, Splunk HEC and Falcon LogScale HEC forwarding require both an endpoint URL and token when configured.+Validation checks destination configuration. For example, Splunk HEC and Falcon+LogScale HEC forwarding require both an endpoint URL and token when configured.+If the endpoint config file is missing, unreadable, or malformed, Beacon currently+falls back to the default effective configuration; this command does not prove that+the file itself parsed successfully. Use `beacon endpoint doctor` when checking an+installed endpoint's overall health.### Examplesdiff --git a/docs/cli/endpoint-connect.mdx b/docs/cli/endpoint-connect.mdxindex 9bbfa53e..3f92d64f 100644--- a/docs/cli/endpoint-connect.mdx+++ b/docs/cli/endpoint-connect.mdx@@ -7,7 +7,12 @@ description: "Connect a Beacon endpoint to Beacon managed ingest, or disconnect`beacon endpoint connect` forwards this endpoint's telemetry to Beacon so it appears on the Beacon dashboard. For a user endpoint, the signed-in CLI account authorizes a device-specific ingest key without another browser approval. The account token is never copied into endpoint state or given to Vector. System mode retains browser approval because unattended/system installs are account-free.-Forwarding is opt-in and revocable. Nothing recorded before connection 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.+Forwarding is opt-in and revocable. Runtime telemetry starts at the end of the+existing runtime log, so pre-connect runtime events are not sent. Inventory starts+at the beginning of `inventory_state.jsonl` so the dashboard receives the endpoint's+current inventory baseline, including inventory records written before connection.+Revoking the device from the dashboard stops ingestion within about a minute.+`beacon endpoint disconnect` stops the forwarder and removes the local credentials.```bash title="Command syntax"beacon endpoint connect [flags]diff --git a/docs/cli/endpoint-dsh.mdx b/docs/cli/endpoint-dsh.mdxnew file mode 100644index 00000000..bd90d3e8--- /dev/null+++ b/docs/cli/endpoint-dsh.mdx@@ -0,0 +1,94 @@+---+title: "beacon endpoint dsh"+description: "Collect endpoint telemetry from DeepSeek Harness session records"+---++## Command overview++`beacon endpoint dsh` reads the native session records DeepSeek Harness commits+under `$DSH_HOME/sessions` (default `~/.dsh/sessions`) and maps them into Beacon+[endpoint events](/concepts/core-concepts#endpoint-event).++```bash title="Command syntax"+beacon endpoint dsh [command]+```++This complements the live [DeepSeek Harness hooks](/runtimes/deepseek-harness).+Hooks observe current tool activity and optional policy decisions. Session sync+backfills assistant text and reasoning, tool failure status, persisted+command/file/MCP detail, and token usage that the hook bridge does not expose.++Every event from this command is marked+`harness.collection_method=poll`. Beacon reads committed records after the fact,+so this path cannot hold, approve, deny, or delay a tool call and does not+synthesize approval events. Reading is local and offline.++## Commands++| Command | Description |+|---------|-------------|+| `beacon endpoint dsh sync` | Read new DeepSeek Harness session records into the runtime log |+| `beacon endpoint dsh status` | Show DeepSeek Harness sessions and collection progress |++## Flags++Both subcommands accept:++| Flag | Description |+|------|-------------|+| `--dsh-home <path>` | DeepSeek Harness home. Defaults to `$DSH_HOME` or `~/.dsh` |+| `--state <path>` | Collector cursor file. Defaults to `~/.beacon/endpoint/state/dsh.json` |+| `--workspace <path>` | Only include sessions whose recorded cwd matches this workspace |+| `--session-id <id>` | Only include one DeepSeek Harness session id |+| `--json` | Print the result as JSON |+| `--user` | Use per-user endpoint paths. Enabled by default |+| `--system` | Use system endpoint paths |++`sync` also accepts:++| Flag | Description |+|------|-------------|+| `--log-path <path>` | Runtime JSONL log path. Defaults to the resolved endpoint log |+| `--print` | Print mapped events without writing them or advancing the cursor |+| `--watch` | Sweep continuously on `--interval` |+| `--interval <duration>` | Sweep interval for `--watch`. Defaults to `1m`, with a 5-second floor |++## Sweeping++```bash title="Sweep once"+beacon endpoint dsh sync+```++```bash title="Preview without writing or advancing the cursor"+beacon endpoint dsh sync --print+```++```bash title="Sweep continuously"+beacon endpoint dsh sync --watch --interval 5m+```++Nothing schedules a sweep automatically. Run `sync` from the scheduler used on+the endpoint, or leave `--watch` running in the account that owns `$DSH_HOME`.+A partly written trailing record is left for the next sweep rather than treated+as corruption.++## Status++```bash title="Show sessions and collection progress"+beacon endpoint dsh status+```++The cursor prevents scheduled sweeps from re-appending a session's complete+history. Re-reading is safe: the same source record maps to the same deterministic+event id.++## Related++<Columns cols={2}>+ <Card title="DeepSeek Harness" icon="code" href="/runtimes/deepseek-harness">+ Hook installation, telemetry coverage, and known limitations.+ </Card>+ <Card title="beacon endpoint hooks" icon="plug" href="/cli/hooks">+ Install and inspect the live DeepSeek Harness hook integration.+ </Card>+</Columns>diff --git a/docs/cli/endpoint-install.mdx b/docs/cli/endpoint-install.mdxindex 17a51d47..2b0dea3f 100644--- a/docs/cli/endpoint-install.mdx+++ b/docs/cli/endpoint-install.mdx@@ -22,7 +22,7 @@ By default, Beacon configures Claude Code and Codex CLI telemetry for local or c| `--user` | Use per-user endpoint paths. Enabled by default || `--system` | Use system endpoint paths and launch daemon. Requires root || `--log-path <path>` | Runtime JSONL log path |-| `--harness <list>` | Comma-separated harnesses to configure. Defaults to `claude,codex`; include `gemini` for Gemini CLI or `vscode` for VS Code Copilot OTLP telemetry. Hook harnesses can be listed alongside them: `claude-hooks` (Claude Code hooks), `cursor`, `factory`, `opencode`, `cline`, `pi`, `omp`, `openclaw`, `grok`, `qwen`, `hermes`, `antigravity`, `devin-cli`, and `devin-desktop`, for example `beacon endpoint install --harness claude,codex,cursor`. `beacon endpoint hooks install` adds the same hooks to an existing install later, and is the only way to add VS Code hook telemetry. GitHub Copilot CLI and Factory Droid OTLP endpoints are managed through their launch environments |+| `--harness <list>` | Comma-separated harnesses to configure. Defaults to `claude,codex`; include `gemini` for Gemini CLI or `vscode` for VS Code Copilot OTLP telemetry. Hook harnesses can be listed alongside them: `claude-hooks` (Claude Code hooks), `cursor`, `factory`, `opencode`, `cline`, `pi`, `omp`, `openclaw`, `grok`, `qwen`, `hermes`, `antigravity`, `devin-cli`, `devin-desktop`, `dsh`, and `kimi`, for example `beacon endpoint install --harness claude,codex,cursor,kimi`. DeepSeek Harness and Kimi Code are user-level only. `beacon endpoint hooks install` adds the same hooks to an existing install later, and is the only way to add VS Code hook telemetry. GitHub Copilot CLI and Factory Droid OTLP endpoints are managed through their launch environments || `--otlp-grpc-port <port>` | Local OTLP gRPC port. Defaults to `4317` || `--otlp-http-port <port>` | Local OTLP HTTP port. Defaults to `4318` || `--collector <path>` | Path to a `beacon-otelcol` binary |@@ -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 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 |+| `--connect` | After a successful install, attempt to connect this endpoint to Beacon managed ingest. User mode uses the signed-in CLI account; system mode opens browser approval. A connection failure does not roll back or fail the completed local install; verify with `beacon endpoint status --json` and retry with [`beacon endpoint connect`](/cli/endpoint-connect) |## Interactive onboarding wizard@@ -57,7 +57,10 @@ signs in through beacon.sh, then asks where this machine's telemetry should go:| Beacon Managed (default) | Shows what will be sent, asks for Standard or Metadata-only privacy, records both choices, and prints `beacon endpoint connect` as a separate next step. Nothing is forwarded during the wizard. || Local only | Explicitly opts out of managed forwarding. Nothing is sent anywhere. |-`--connect` presets Beacon Managed and runs the connect flow after installation.+`--connect` presets Beacon Managed and attempts the connect flow after installation.+If connect fails, the completed local install still exits successfully and prints+`beacon endpoint connect` as the retry command. Automation should verify+`.managed_ingest.connected` with `beacon endpoint status --json`.`BEACON_MANAGED_INGEST=0` hides the managed answer. The wizard is never shownfor system/root, package, MDM, CI, dry-run, or redirected-input installs.Customer-managed destinations remain available through thediff --git a/docs/cli/endpoint-onboarding.mdx b/docs/cli/endpoint-onboarding.mdxindex a18811b4..1d4c2d70 100644--- a/docs/cli/endpoint-onboarding.mdx+++ b/docs/cli/endpoint-onboarding.mdx@@ -41,9 +41,13 @@ diffs, and optional inventory content locally before upload. See[`beacon endpoint connect`](/cli/endpoint-connect#privacy-modes) for the exact contract.Completing the wizard records managed intent and prints that next step; it does not-connect automatically. Existing local history is not uploaded. The explicit+connect automatically. Pre-connect runtime history is not uploaded. On the first+connection, inventory is read from the beginning of `inventory_state.jsonl` so the+hosted dashboard receives the endpoint's current inventory baseline. The explicit`beacon endpoint install --connect` flag remains the exception: it presets Managed-and runs device enrollment after installation.+and attempts device enrollment after installation. If that enrollment fails, the+local install still succeeds and prints `beacon endpoint connect` as the retry+command; verify forwarding with `beacon endpoint status --json`.The wizard never appears non-interactively. Package postinstall scripts, MDMdeployments, `--system` installs, CI, `--dry-run`, and any piped or redirected stdin@@ -124,6 +128,6 @@ To have your record deleted, email the install ID shown by this command toConfigure endpoint telemetry and collector service files.</Card><Card title="Endpoint config" icon="gear" href="/cli/endpoint-config">- Inspect, validate, and update endpoint configuration.+ Inspect endpoint configuration and validate destination settings.</Card></Columns>diff --git a/docs/cli/endpoint-repair.mdx b/docs/cli/endpoint-repair.mdxindex 3b26ba31..a76a07b8 100644--- a/docs/cli/endpoint-repair.mdx+++ b/docs/cli/endpoint-repair.mdx@@ -22,7 +22,7 @@ During repair, Beacon removes the existing managed service before reinstalling i| `--user` | Use per-user endpoint paths. Enabled by default || `--system` | Use system endpoint paths and launch daemon || `--log-path <path>` | Runtime JSONL log path |-| `--harness <list>` | Comma-separated harnesses to configure. Defaults to `claude,codex`; include `gemini` for Gemini CLI or `vscode` for VS Code Copilot OTLP telemetry. Hook harnesses can be listed alongside them: `claude-hooks` (Claude Code hooks), `cursor`, `factory`, `opencode`, `cline`, `pi`, `omp`, `openclaw`, `grok`, `qwen`, `hermes`, `antigravity`, `devin-cli`, and `devin-desktop`, for example `beacon endpoint repair --harness claude,codex,cursor`. `beacon endpoint hooks install` adds the same hooks to an existing install later, and is the only way to add VS Code hook telemetry. GitHub Copilot CLI and Factory Droid OTLP endpoints are managed through their launch environments |+| `--harness <list>` | Comma-separated harnesses to configure. Defaults to `claude,codex`; include `gemini` for Gemini CLI or `vscode` for VS Code Copilot OTLP telemetry. Hook harnesses can be listed alongside them: `claude-hooks` (Claude Code hooks), `cursor`, `factory`, `opencode`, `cline`, `pi`, `omp`, `openclaw`, `grok`, `qwen`, `hermes`, `antigravity`, `devin-cli`, `devin-desktop`, `dsh`, and `kimi`, for example `beacon endpoint repair --harness claude,codex,cursor,kimi`. DeepSeek Harness and Kimi Code are user-level only. `beacon endpoint hooks install` adds the same hooks to an existing install later, and is the only way to add VS Code hook telemetry. GitHub Copilot CLI and Factory Droid OTLP endpoints are managed through their launch environments || `--otlp-grpc-port <port>` | Local OTLP gRPC port. Defaults to `4317` || `--otlp-http-port <port>` | Local OTLP HTTP port. Defaults to `4318` || `--collector <path>` | Path to a `beacon-otelcol` binary |diff --git a/docs/cli/endpoint.mdx b/docs/cli/endpoint.mdxindex 1ccb65f8..aacf877f 100644--- a/docs/cli/endpoint.mdx+++ b/docs/cli/endpoint.mdx@@ -38,7 +38,7 @@ 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 Beacon dashboard and start the Vector forwarder.+ Enroll this device with the signed-in CLI account and start the Vector forwarder. System mode uses browser approval.</Card><Card title="beacon endpoint disconnect" icon="link-slash" href="/cli/endpoint-connect">Stop the Beacon forwarder and remove the local device key.@@ -53,7 +53,7 @@ beacon endpoint [command]Stop services and remove managed endpoint files.</Card><Card title="beacon endpoint config" icon="gear" href="/cli/endpoint-config">- Inspect, validate, and update endpoint configuration.+ Inspect endpoint configuration and validate destination settings.</Card><Card title="beacon endpoint onboarding" icon="envelope" href="/cli/endpoint-onboarding">Show, reset, or resend the one-time onboarding record.@@ -61,6 +61,12 @@ beacon endpoint [command]<Card title="beacon endpoint fx" icon="rotate" href="/cli/endpoint-fx">Collect telemetry from fx session records on this machine.</Card>+ <Card title="beacon endpoint copilot" icon="rotate" href="/cli/endpoint-copilot">+ Collect telemetry from GitHub Copilot CLI session records.+ </Card>+ <Card title="beacon endpoint dsh" icon="rotate" href="/cli/endpoint-dsh">+ Collect telemetry from DeepSeek Harness session records.+ </Card><Card title="beacon endpoint traces" icon="magnifying-glass" href="/cli/endpoint-traces">Index, list, search, and show local traces from runtime logs.</Card>diff --git a/docs/cli/hooks.mdx b/docs/cli/hooks.mdxindex e3e13512..30e36199 100644--- a/docs/cli/hooks.mdx+++ b/docs/cli/hooks.mdx@@ -35,9 +35,11 @@ beacon endpoint hooks [command]| Cursor | `~/.cursor/hooks.json` | `./.cursor/hooks.json` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || Devin CLI | `~/.config/devin/config.json` | `./.devin/hooks.v1.json` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || Devin Desktop | `~/.codeium/windsurf/hooks.json` | `./.windsurf/hooks.json` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` |+| DeepSeek Harness | `$DSH_HOME/beacon-endpoint-hooks.json` plus `$DSH_HOME/cordis.patch.yml` (default `~/.dsh`) | Not supported | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || Factory Droid | `~/.factory/settings.json` | `./.factory/settings.json` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || Grok Build | `~/.grok/hooks/beacon-endpoint.json` | `./.grok/hooks/beacon-endpoint.json` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || Hermes Agent | `~/.hermes/config.yaml` | Not supported | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` |+| Kimi Code | `$KIMI_CODE_HOME/config.toml` (default `~/.kimi-code/config.toml`) | Not supported | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || OpenCode | `~/.config/opencode/plugins/beacon.ts` | `./.opencode/plugins/beacon.ts` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || Cline | `~/.cline/plugins/beacon.ts` | `./.cline/plugins/beacon.ts` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` || Pi | `~/.pi/agent/extensions/beacon.ts` | `./.pi/extensions/beacon.ts` | `~/.beacon/endpoint/hooks/beacon-hooks` | `~/.beacon/endpoint/logs/runtime.jsonl` |@@ -50,7 +52,7 @@ In system mode, the hook binary is written under `/Library/Application Support/B| Flag | Description ||------|-------------|-| `--harness <list>` | Comma-separated hook harnesses, such as `antigravity`, `claude`, `cline`, `codex`, `cursor`, `devin-cli`, `devin-desktop`, `factory`, `grok`, `hermes`, `omp`, `openclaw`, `opencode`, `pi`, `qwen`, or `antigravity,claude,cline,codex,cursor,devin-cli,devin-desktop,factory,grok,hermes,omp,openclaw,opencode,pi,qwen`. `devin` remains a legacy alias for `devin-cli`; `hermes-agent` maps to `hermes`; `qwen-code` maps to `qwen`; `pi-cli` and `pi_cli` map to `pi`; `oh-my-pi` and `ohmypi` map to `omp`; `openclaw-gateway` maps to `openclaw`. Defaults to `cursor` |+| `--harness <list>` | Comma-separated hook harnesses, such as `antigravity`, `claude`, `cline`, `codex`, `cursor`, `devin-cli`, `devin-desktop`, `dsh`, `factory`, `grok`, `hermes`, `kimi`, `omp`, `openclaw`, `opencode`, `pi`, or `qwen`. `deepseek` and `deepseek-harness` map to `dsh`; `kimi-code`, `kimi_code`, and `moonshot` map to `kimi`; `devin` remains a legacy alias for `devin-cli`; `hermes-agent` maps to `hermes`; `qwen-code` maps to `qwen`; `pi-cli` and `pi_cli` map to `pi`; `oh-my-pi` and `ohmypi` map to `omp`; `openclaw-gateway` maps to `openclaw`. Defaults to `cursor` || `--level <level>` | Hook install level: `user` or `project` || `--user` | Use per-user endpoint paths. Enabled by default || `--system` | Use system endpoint paths and launch daemon |@@ -60,7 +62,7 @@ In system mode, the hook binary is written under `/Library/Application Support/B| `--dry-run` | Print planned install or uninstall actions without changing hook files. Install and uninstall only |<Note>- Restart Antigravity CLI, Claude Code, Cline, Codex CLI, Cursor, Devin CLI, Devin Desktop, Factory Droid, Grok Build, Hermes Agent, or OpenCode after installing or removing hooks so the updated hook configuration is picked up by new sessions.+ Restart Antigravity CLI, Claude Code, Cline, Codex CLI, Cursor, DeepSeek Harness, Devin CLI, Devin Desktop, Factory Droid, Grok Build, Hermes Agent, Kimi Code, or OpenCode after installing or removing hooks so the updated hook configuration is picked up by new sessions.</Note>Beacon validates the embedded `beacon-hooks` binary before writing hook configuration. If install fails with an architecture validation error, upgrade Beacon or reinstall the platform-specific release archive for the host, then run the hook install command again.diff --git a/docs/cli/index.mdx b/docs/cli/index.mdxindex 7e2b2705..65d306e7 100644--- a/docs/cli/index.mdx+++ b/docs/cli/index.mdx@@ -46,6 +46,7 @@ Top-level Agent Beacon CLI commands.| [`beacon scan`](/cli/scan) | Run threat-detection rules over local endpoint telemetry. || [`beacon status`](/cli/endpoint-status) | Alias for `beacon endpoint status`. || [`beacon token-usage`](/cli/token-usage) | Report token usage and attribution from Beacon runtime logs. |+| [`beacon traces`](/cli/endpoint-traces) | Open the interactive local trace browser; redirected I/O falls back to a bounded trace list. || [`beacon version`](/cli/version) | Display the installed Agent Beacon CLI version. || [`beacon whoami`](/cli/account-auth#inspect-the-account) | Show the current Beacon account and session expiry. |@@ -149,7 +150,7 @@ Manage the local endpoint agent and inspect supported agent harness telemetry.|---------|-------------|| [`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 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 connect`](/cli/endpoint-connect) | Enroll this device with the signed-in CLI account and start the Vector forwarder; system mode uses browser approval. || [`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. |@@ -159,7 +160,7 @@ Manage the local endpoint agent and inspect supported agent harness telemetry.| [`beacon endpoint repair`](/cli/endpoint-repair) | Repair Beacon endpoint service files, telemetry configuration, and optional collector forwarding destinations. || [`beacon endpoint uninstall`](/cli/endpoint-uninstall) | Remove Beacon endpoint service files, with an option to keep local logs. || [`beacon endpoint update`](/cli/upgrade#self-updating-endpoint-packages) | Check for, enable, or apply signed endpoint package updates. |-| [`beacon endpoint config`](/cli/endpoint-config) | Inspect, validate, and update endpoint configuration. |+| [`beacon endpoint config`](/cli/endpoint-config) | Inspect endpoint configuration and validate destination settings. || [`beacon endpoint onboarding`](/cli/endpoint-onboarding) | Show, reset, or resend the one-time onboarding record. || [`beacon endpoint dashboard`](/cli/dashboard#beacon-endpoint-dashboard) | Run the local dashboard over Beacon runtime logs for endpoint inspection. || [`beacon endpoint traces`](/cli/endpoint-traces) | Index, list, search, and show local traces from Beacon runtime logs. |@@ -176,6 +177,8 @@ Manage the local endpoint agent and inspect supported agent harness telemetry.| [`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. |+| [`beacon endpoint copilot`](/cli/endpoint-copilot) | Collect endpoint telemetry from GitHub Copilot CLI session records on this machine. |+| [`beacon endpoint dsh`](/cli/endpoint-dsh) | Collect endpoint telemetry from DeepSeek Harness session records on this machine. || [`beacon endpoint fx`](/cli/endpoint-fx) | Collect endpoint telemetry from fx session records on this machine. || [`beacon endpoint integrations openclaw`](/cli/openclaw) | Set up and validate OpenClaw Gateway OTLP export. || [`beacon endpoint integrations claude-cowork`](/cli/claude-cowork) | Set up and validate Claude Cowork OTLP export. |@@ -186,7 +189,7 @@ Manage the local endpoint agent and inspect supported agent harness telemetry.beacon endpoint config [command]```-Inspect, validate, and update endpoint configuration.+Inspect endpoint configuration and validate destination settings.| Command | Description ||---------|-------------|diff --git a/docs/cli/token-usage.mdx b/docs/cli/token-usage.mdxindex 49421780..bf2e42b2 100644--- a/docs/cli/token-usage.mdx+++ b/docs/cli/token-usage.mdx@@ -30,7 +30,9 @@ 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 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.+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.**Collected and verified against captured payloads:**@@ -45,6 +47,7 @@ Token coverage is not uniform, and the reason is almost always the runtime rathe| Pi | input, output, cache read, cache creation, reasoning | Reported (`cost_usd`) | Yes | Yes || Oh My Pi | input, output, cache read, cache creation, reasoning | Reported (`cost_usd`) | Yes | Yes || Prime Agent | input, output, cache read, cache creation, reasoning | Reported (`cost_usd`) | Yes | Yes |+| DeepSeek Harness | input, output, cache read, cache creation | Not reported | Yes, from committed session records | Yes || fx (Vercel Labs) | input, output, cache read, cache creation | Reported (`cost_usd`) | Yes | Yes || GitHub Copilot CLI | input, output, cache read, cache creation, reasoning | Not reported | Yes | Yes || OpenClaw Gateway | input, output, cache read, cache creation | Not reported on the hook | Yes, per model response | Yes |diff --git a/docs/deployment/hosting-options.mdx b/docs/deployment/hosting-options.mdxindex 720529d3..24167058 100644--- a/docs/deployment/hosting-options.mdx+++ b/docs/deployment/hosting-options.mdx@@ -86,12 +86,21 @@ See [Local](/deployment/open-source) for setup details and [Security & IT RollouUse Managed when you want hosted visibility, governance, and enterprise rollout support for agent activity.1. [Create a Beacon account](https://beacon.sh/sign-up).-2. Connect each endpoint to your account:+2. Sign the CLI in on each user endpoint:++```bash+beacon login+```++3. Connect the endpoint to your account:```bashbeacon endpoint connect --dashboard-url https://beacon.sh```+Interactive `beacon endpoint install` performs the sign-in step when needed.+System-mode connect remains account-free and uses browser approval instead.+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 a Beacon API key:diff --git a/docs/docs.json b/docs/docs.jsonindex 5138ac32..50f79451 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -298,6 +298,7 @@"cli/endpoint-opencode","cli/endpoint-pi","cli/endpoint-copilot",+ "cli/endpoint-dsh","cli/endpoint-fx","cli/endpoint-traces","cli/dashboard",diff --git a/docs/get-started/quickstart.mdx b/docs/get-started/quickstart.mdxindex b8b26dbb..88219e53 100644--- a/docs/get-started/quickstart.mdx+++ b/docs/get-started/quickstart.mdx@@ -76,9 +76,13 @@ second browser approval. Use `--privacy-mode metadata-only` to override Standard## 3. Run an agent-Start a new Claude Code, Codex, Cursor, or other supported agent session and use it normally.+Start a session in a runtime you configured. The default endpoint install+configures Claude Code and Codex CLI. Cursor and other supported runtimes require+their documented hook, plugin, OTLP, or session-sync setup; see [Agent+harnesses](/runtimes).-Beacon captures the session automatically.+Once that runtime surface is configured, Beacon captures the telemetry the+runtime exposes through it.## 4. View your sessionsdiff --git a/docs/guides/local-testing/mcp.mdx b/docs/guides/local-testing/mcp.mdxindex a5072768..89938f1c 100644--- a/docs/guides/local-testing/mcp.mdx+++ b/docs/guides/local-testing/mcp.mdx@@ -55,11 +55,26 @@ beacon mcp doctor```bash title="Sample output"$ beacon mcp doctor-runtime log: readable-transport: stdio-tools: search_activity, summarize_activity, get_activity_event, list_activity_filters- search_memory, get_memory, get_memory_context-sample events: found+Beacon MCP doctor++Transport: stdio+Runtime log: /Users/you/.beacon/endpoint/logs/runtime.jsonl+Runtime log source: user endpoint log+Runtime log check: ok+Sampled events: 1+Malformed lines: 0+Readable archives: 0+MCP tools: search_activity, summarize_activity, get_activity_event, list_activity_filters, search_memory, get_memory, get_memory_context++MCP client config:+{+ "mcpServers": {+ "beacon": {+ "command": "beacon",+ "args": ["mcp", "serve", "--transport", "stdio"]+ }+ }+}```</Accordion>diff --git a/docs/log-forwarding/asymptote.mdx b/docs/log-forwarding/asymptote.mdxindex 592e0985..2f728a2c 100644--- a/docs/log-forwarding/asymptote.mdx+++ b/docs/log-forwarding/asymptote.mdx@@ -13,7 +13,17 @@ Generate the pack with [`beacon endpoint asymptote`](/cli/asymptote). `beacon en## What leaves the machine-Standard mode forwards every line written after the forwarder starts exactly as Beacon wrote it locally. Metadata-only mode applies a local Vector transform first, removing retained prompts, responses, reasoning, tool arguments/results, command output, raw fields, diffs, inventory content, and MCP definitions while preserving stable ids, hashes, counts, actions, paths, token usage, and other structured metadata. Beacon's [retention and redaction](/security/retention-redaction) controls still run before either mode. The ingest service adds tenant identity server-side.+For runtime telemetry, Standard mode forwards every line written after the+forwarder starts exactly as Beacon wrote it locally; pre-connect runtime history is+not sent. Inventory is read from the beginning of `inventory_state.jsonl` so a+newly connected endpoint sends its current inventory baseline, including inventory+records written before connection. Metadata-only mode applies a local Vector+transform first, removing retained prompts, responses, reasoning, tool+arguments/results, command output, raw fields, diffs, inventory content, and MCP+definitions while preserving stable ids, hashes, counts, actions, paths, token+usage, and other structured metadata. Beacon's [retention and+redaction](/security/retention-redaction) controls still run before either mode.+The ingest service adds tenant identity server-side.Nothing else is sent. The forwarder does not read prompts, files, environment variables, or shell history beyond what the events already contain.diff --git a/docs/log-forwarding/index.mdx b/docs/log-forwarding/index.mdxindex c3e16c00..2a7c9fad 100644--- a/docs/log-forwarding/index.mdx+++ b/docs/log-forwarding/index.mdx@@ -31,7 +31,10 @@ Use system mode for MDM deployments so endpoint events land in the shared system### Beacon Managed-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.+Use this path when Beacon events should appear on the Beacon dashboard. In user+mode, the signed-in CLI account authorizes a device key without another browser+approval. System mode uses browser approval. Revoking the device stops ingestion+within a minute.<Columns cols={2}><Card title="Beacon Managed" icon="tower-broadcast" href="/log-forwarding/asymptote">diff --git a/docs/runtimes/deepseek-harness.mdx b/docs/runtimes/deepseek-harness.mdxindex b6ce8f11..b11b01b2 100644--- a/docs/runtimes/deepseek-harness.mdx+++ b/docs/runtimes/deepseek-harness.mdx@@ -236,7 +236,7 @@ Confirm status, then generate one event and check the log:beacon endpoint hooks status --harness dshbeacon endpoint dsh statusbeacon endpoint dsh sync-beacon endpoint doctor --system+beacon endpoint doctorgrep '"name":"deepseek_harness"' ~/.beacon/endpoint/logs/runtime.jsonl | tail -3```@@ -254,8 +254,8 @@ If DeepSeek Harness telemetry is missing:## Related<Columns cols={2}>- <Card title="Supported agent harnesses" icon="list-check" href="/runtimes">- Return to the runtime support overview.+ <Card title="beacon endpoint dsh" icon="rotate" href="/cli/endpoint-dsh">+ Sync committed sessions and inspect collection progress.</Card><Card title="Agent harness integration model" icon="plug" href="/runtimes/integration-model">See how Beacon discovers and configures each runtime.diff --git a/docs/runtimes/integration-model.mdx b/docs/runtimes/integration-model.mdxindex 259b18d5..a770c429 100644--- a/docs/runtimes/integration-model.mdx+++ b/docs/runtimes/integration-model.mdx@@ -17,6 +17,8 @@ Beacon supports multiple [runtime surfaces](/concepts/core-concepts#runtime-surf| [Codex CLI](/runtimes/codex-cli) | Looks for the `codex` executable and `~/.codex/config.toml` || [Gemini CLI](/runtimes/gemini-cli) | Looks for the `gemini` executable and `~/.gemini/settings.json` || [GitHub Copilot CLI](/runtimes/github-copilot-cli) | Looks for the `copilot` executable or `~/.copilot/config.json`, then validates Copilot OTel environment variables |+| [DeepSeek Harness](/runtimes/deepseek-harness) | Looks for the `dsh` executable or `$DSH_HOME` (default `~/.dsh`), then checks both Beacon's owned hook file and its mount row in `cordis.patch.yml` |+| [Kimi Code](/runtimes/kimi-code) | Looks for the `kimi` executable or `$KIMI_CODE_HOME` (default `~/.kimi-code`), then parses `config.toml` and checks for Beacon's `--platform kimi` hook commands || [VS Code](/runtimes/vscode) | Looks for the `code` executable or VS Code user settings, then validates Copilot Chat OTel settings || [Grok Build](/runtimes/grok-build) | Checks for Beacon's managed Grok hook file at `~/.grok/hooks/beacon-endpoint.json` or `./.grok/hooks/beacon-endpoint.json` || [OpenCode](/runtimes/opencode) | Looks for the `opencode` executable or `~/.config/opencode`, then checks the managed Beacon plugin |@@ -50,7 +52,7 @@ During install, Beacon configures the runtime surfaces it can safely manage:| [Factory Droid](/runtimes/factory-droid) | Droid's OTLP endpoint remains under its launch environment, commonly managed through MDM or another customer-owned policy. Committed sessions can be backfilled with `beacon endpoint factory sync`. || [OpenClaw Gateway](/runtimes/openclaw-gateway) | Configure OpenClaw with the `diagnostics-otel` plugin. Beacon prints local OTLP/HTTP setup guidance and validates observed events. Committed session files can be backfilled with `beacon endpoint integrations openclaw sessions sync`. || [fx (Vercel Labs)](/runtimes/vercel-fx) | Nothing is installed or configured. fx has no hook file, plugin directory, or OTLP endpoint, so collection is an action: run or schedule [`beacon endpoint fx sync`](/cli/endpoint-fx). |-| Hook-based runtimes | [Antigravity CLI](/runtimes/antigravity-cli), [Claude Code](/runtimes/claude-code), [Cline](/runtimes/cline), [Cursor](/runtimes/cursor), [Devin CLI](/runtimes/devin), [Devin Desktop](/runtimes/devin-desktop), [Factory](/runtimes/factory-droid), [Grok Build](/runtimes/grok-build), [goose](/runtimes/goose), [Hermes Agent](/runtimes/hermes-agent), [Kiro](/runtimes/kiro), [Muse Code](/runtimes/muse-code), [Oh My Pi](/runtimes/oh-my-pi), [OpenCode](/runtimes/opencode), [OpenHands](/runtimes/openhands), [Pi](/runtimes/pi), and [Qwen Code](/runtimes/qwen-code) hooks and managed plugins are installed separately with [`beacon endpoint hooks`](/cli/hooks), because hooks are per-user or per-project runtime configuration rather than base collector service configuration. |+| Hook-based runtimes | [Antigravity CLI](/runtimes/antigravity-cli), [Claude Code](/runtimes/claude-code), [Cline](/runtimes/cline), [Cursor](/runtimes/cursor), [DeepSeek Harness](/runtimes/deepseek-harness), [Devin CLI](/runtimes/devin), [Devin Desktop](/runtimes/devin-desktop), [Factory](/runtimes/factory-droid), [Grok Build](/runtimes/grok-build), [goose](/runtimes/goose), [Hermes Agent](/runtimes/hermes-agent), [Kimi Code](/runtimes/kimi-code), [Kiro](/runtimes/kiro), [Muse Code](/runtimes/muse-code), [Oh My Pi](/runtimes/oh-my-pi), [OpenCode](/runtimes/opencode), [OpenHands](/runtimes/openhands), [Pi](/runtimes/pi), and [Qwen Code](/runtimes/qwen-code) hooks and managed plugins are installed separately with [`beacon endpoint hooks`](/cli/hooks), because hooks are per-user or per-project runtime configuration rather than base collector service configuration. DeepSeek Harness and Kimi Code support user scope only. |## Integration paths@@ -60,6 +62,8 @@ During install, Beacon configures the runtime surfaces it can safely manage:| [Codex CLI](/runtimes/codex-cli) | Local OTLP logs, selective turn traces, SessionStart hook, and poll of `~/.codex/sessions` | Beacon writes structured Codex OTLP config, filters noisy internal spans, and joins OS-user context to per-turn usage. `beacon endpoint codex sync` backfills committed sessions as poll events. || [Gemini CLI](/runtimes/gemini-cli) | Opt-in local OTLP logs, traces, and metrics | Beacon writes Gemini telemetry settings and maps Gemini prompts, tool calls, MCP activity, file operations, and approval events into endpoint events. || [GitHub Copilot CLI](/runtimes/github-copilot-cli) | MDM-managed OTLP HTTP export plus poll of `~/.copilot/session-state` | Beacon validates Copilot's effective launch environment and maps Copilot spans into prompt, session, tool, and approval-like endpoint events. `beacon endpoint copilot sync` backfills committed session records as poll events with assistant text, complete tool results, commands, file activity, and token usage. |+| [DeepSeek Harness](/runtimes/deepseek-harness) | Native hook bridge plus poll of `$DSH_HOME/sessions` | Beacon installs an owned hooks file and a mount row in the runtime's home-level `cordis.patch.yml`. `beacon endpoint dsh sync` backfills assistant text/reasoning, failures, persisted tool detail, and token usage as poll events. There is no project scope. |+| [Kimi Code](/runtimes/kimi-code) | Native hook payloads through `beacon-hooks` | Beacon appends a verified `[[hooks]]` block to the runtime's existing `config.toml` without reserializing the file. Hooks cover lifecycle, prompts, tools, commands, files, MCP, subagents, compaction, and observed permission decisions. Kimi exposes no token usage on hooks and has no project scope. || [VS Code](/runtimes/vscode) | Copilot Chat OTel plus optional preview hooks | Beacon writes VS Code Copilot OTel settings and maps Copilot prompts, sessions, model metadata, and tool activity into endpoint events. Hooks are optional for extra lifecycle and cross-agent detail. || [Antigravity CLI](/runtimes/antigravity-cli) | Native hook payloads through `beacon-hooks` | Beacon writes a managed Antigravity hook block and maps prompt, pre-tool, post-tool, invocation, command, file edit, and diff telemetry into endpoint events. || [Grok Build](/runtimes/grok-build) | Native hook payloads through `beacon-hooks`, plus poll of `~/.grok/sessions` | Beacon writes an owned Grok hook file and maps session, prompt, tool, command, file, and failed-tool events into endpoint events. `beacon endpoint grok sync` backfills committed sessions as poll events. |@@ -85,13 +89,18 @@ During install, Beacon configures the runtime surfaces it can safely manage:## Hook telemetry-Antigravity CLI, Claude Code, Cline, Cursor, Devin CLI, Devin Desktop, Factory, goose, Grok Build, Hermes Agent, Muse Code, Oh My Pi, OpenCode, OpenHands, Pi, Qwen Code, and optional VS Code hooks cover activity that is better represented as runtime events than generic OTLP spans.+Antigravity CLI, Claude Code, Cline, Cursor, DeepSeek Harness, Devin CLI, Devin+Desktop, Factory, goose, Grok Build, Hermes Agent, Kimi Code, Muse Code, Oh My+Pi, OpenCode, OpenHands, Pi, Qwen Code, and optional VS Code hooks cover activity+that is better represented as runtime events than generic OTLP spans.| Runtime | Hook telemetry ||---------|----------------|| [Antigravity CLI](/runtimes/antigravity-cli) | Prompt submission, pre-tool and post-tool activity, invocation stop events, command activity, file edits, and diffs where payloads are available. || [Claude Code](/runtimes/claude-code) | Session lifecycle, prompt submission, pre-tool and post-tool activity, failed tool calls, subagent start and stop, permission requests, and session-end events where payloads are available. || [Cursor](/runtimes/cursor) | Session lifecycle, prompt submission, tool invocation, shell command execution, MCP-like tool activity, approval decisions, and file edits where payloads are available. |+| [DeepSeek Harness](/runtimes/deepseek-harness) | Session lifecycle, prompts, tools, commands, files, MCP and subagent activity through the Claude-shaped bridge. The live bridge does not expose assistant text/reasoning, failures, or token usage; session sync fills those gaps. |+| [Kimi Code](/runtimes/kimi-code) | Session lifecycle, prompts, tool invocation and failures, commands with output and exit code, file reads and edits with diffs, MCP calls, subagents, context compaction, and observed permission decisions. No hook payload exposes token usage. || [VS Code](/runtimes/vscode) | Preview only and may be disabled by organization policy. When enabled, hooks add lifecycle, prompt, pre-tool, post-tool, stop, and subagent detail across VS Code agent surfaces. || [Devin CLI](/runtimes/devin) | Session lifecycle, prompt submission, pre-tool and post-tool activity, permission requests, stop events, session-end events, approvals, and file telemetry where payloads are available. || [Devin Desktop](/runtimes/devin-desktop) | Prompt submission, command execution, MCP tool use, file reads, and file writes where Cascade/Windsurf hook payloads are available. |diff --git a/docs/runtimes/kimi-code.mdx b/docs/runtimes/kimi-code.mdxindex d108db82..b49e07f8 100644--- a/docs/runtimes/kimi-code.mdx+++ b/docs/runtimes/kimi-code.mdx@@ -66,12 +66,12 @@ Beacon **refuses** rather than writing:# Beacon endpoint telemetry. Managed by `beacon endpoint hooks install --harness kimi`.[[hooks]]event = 'SessionStart'-command = "'/opt/beacon/bin/beacon-hooks' --platform kimi --log '/var/log/beacon/runtime.jsonl' session-start"+command = "'/opt/beacon/bin/beacon-hooks' --platform kimi --log '/var/log/beacon-agent/runtime.jsonl' session-start"timeout = 10[[hooks]]event = 'UserPromptSubmit'-command = "'/opt/beacon/bin/beacon-hooks' --platform kimi --log '/var/log/beacon/runtime.jsonl' prompt-submit"+command = "'/opt/beacon/bin/beacon-hooks' --platform kimi --log '/var/log/beacon-agent/runtime.jsonl' prompt-submit"timeout = 30```@@ -246,7 +246,7 @@ Confirm status, then generate one event and check the log:```bashbeacon endpoint hooks status --harness kimi-beacon endpoint doctor --system+beacon endpoint doctorgrep '"name":"kimi_code"' ~/.beacon/endpoint/logs/runtime.jsonl | tail -3```diff --git a/docs/security/data-flow-threat-model.mdx b/docs/security/data-flow-threat-model.mdxindex 85a86b68..6d79fc27 100644--- a/docs/security/data-flow-threat-model.mdx+++ b/docs/security/data-flow-threat-model.mdx@@ -34,7 +34,7 @@ flowchart LR| Risk | Design response ||------|-----------------|-| Unintended hosted telemetry | Managed is preselected in interactive onboarding, but selection and account sign-in do not forward anything. Forwarding starts only after the separate connect command, sends only new lines, records the active privacy mode, and stops within a minute of revocation |+| Unintended hosted telemetry | Managed is preselected in interactive onboarding, but selection and account sign-in do not forward anything. Forwarding starts only after the separate connect command. Runtime forwarding starts at the end of the existing log; inventory starts at the beginning so the service receives the endpoint's current inventory baseline. The active privacy mode is recorded, and forwarding 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 | Standard applies local sanitization and size controls. Metadata-only additionally strips retained prompts, responses, reasoning, tool arguments/results, command output, raw fields, diffs, inventory content, and MCP definitions in Vector before buffering or upload || Secret leakage in retained content | Beacon applies redaction, sanitization, truncation, and event-size limits before writing supported content fields |diff --git a/docs/security/data-inventory.mdx b/docs/security/data-inventory.mdxindex ef87867b..cb48abf9 100644--- a/docs/security/data-inventory.mdx+++ b/docs/security/data-inventory.mdx@@ -23,6 +23,9 @@ Beacon writes normalized endpoint events only when supported runtimes provide te| Devin Desktop | Cascade/Windsurf hooks | Prompt, command, MCP tool, file read, and file write telemetry where Desktop exposes Cascade hook payloads || Factory Droid | OTLP HTTP plus optional hooks plus local session-store sync | Session, prompt, assistant messages, reasoning, tool calls/results, write/edit/create hook payloads, token usage, stop, session-end, and available OTLP telemetry || Cursor | Native hooks | Prompt, tool, shell command, MCP-like, approval, and file edit telemetry |+| DeepSeek Harness | Managed native hooks plus local session-store sync | Live session, prompt, tool, command, file, MCP, subagent, and policy activity; committed assistant text/reasoning, failed tools, persisted results, and token usage from session backfill |+| GitHub Copilot CLI | Customer-managed OTLP HTTP plus local session-store sync | Live session, prompt, tool, and approval-like activity; committed assistant text/reasoning, complete tool results, commands, file activity, and token usage from session backfill |+| Kimi Code | Managed native hooks | Session, prompt, tool and failed-tool activity, commands with output and exit code, file reads/edits with diffs, MCP calls, subagents, compaction, and observed permission decisions; no token usage because hooks do not expose it || Claude Cowork | Admin-configured OTLP | Prompt and assistant response content; approvals; command, tool, file, and MCP activity; session lifecycle; model and token usage; runtime-reported cost; source user identifier and cloud origin when emitted through Cowork OTLP || OpenClaw Gateway | Managed plugin, plus gateway-configured OTLP/HTTP | Prompts (the inbound chat message, with the sender and the chat channel), tool inputs and results, commands with exit code and output, file activity and diffs, MCP calls, agent response text, token usage, session and subagent lifecycle, and compaction; the verbatim hook envelope is retained under `raw.openclaw`. Gateway traces and metrics come separately from OpenClaw's own diagnostics export || [Claude.ai](/runtimes/claude-web) (`claude_web`) | Managed browser extension over local OTLP | Prompt text, assistant response text, request and response model, tool call id/name/arguments/results, conversation id, and token usage when the stream carries it, from the claude.ai chat stream |diff --git a/docs/security/endpoint-operations.mdx b/docs/security/endpoint-operations.mdxindex 093de30b..d40f18d1 100644--- a/docs/security/endpoint-operations.mdx+++ b/docs/security/endpoint-operations.mdx@@ -81,7 +81,7 @@ 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 |-| 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 managed ingest (opt-in) | In user mode, `beacon endpoint connect` uses the signed-in CLI account to authorize a separate per-device key; system mode uses browser approval. A Vector forwarder posts runtime and inventory JSONL over HTTPS to Beacon's ingest service; the device is 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 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.