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
Bring the docs in line with what onboarding now does
shukieshah634aff9ab45d
diff --git a/README.md b/README.mdindex 3d6c1780..e8a7c6a2 100644--- a/README.md+++ b/README.md@@ -46,9 +46,10 @@ Beacon is an open-source memory layer for AI coding agents that learns from your## 🚀 Quick StartBeacon is open source and local-first. Interactive endpoint setup signs in through-beacon.sh and preselects Beacon Managed, with an explicit Local opt-out. Nothing is-forwarded until the separate connect step. System, package, MDM, and CI installation-paths remain noninteractive and account-free.+beacon.sh and preselects Beacon Managed, with an explicit Local opt-out. Signing in+forwards nothing; confirming Managed installs Beacon and connects this machine in+the same command, and the confirm screen says so before you accept. System, package,+MDM, and CI installation paths remain noninteractive and account-free.### 1. Install Beacondiff --git a/docs/cli/endpoint-install.mdx b/docs/cli/endpoint-install.mdxindex 354cb514..9b1bfb95 100644--- a/docs/cli/endpoint-install.mdx+++ b/docs/cli/endpoint-install.mdx@@ -27,6 +27,7 @@ By default, Beacon configures Claude Code and Codex CLI telemetry for local or c| `--otlp-http-port <port>` | Local OTLP HTTP port. Defaults to `4318` || `--collector <path>` | Path to a `beacon-otelcol` binary || `--no-start` | Write files without starting the collector service |+| `--no-browser` | During interactive setup, print the sign-in URL instead of opening a browser. Useful where no browser can be opened, though the URL still has to be opened on this machine || `--service <kind>` | Service manager to use: `auto` (default), `launchd`, `systemd`, or `none` for a supervised collector process || `--dry-run` | Print planned actions without changing endpoint files or services || `--include-runtime-metrics` | Include generic process, runtime, and harness operational OTLP metrics in Beacon JSONL. By default, low-signal metrics such as process CPU, memory, Node.js event loop, V8 heap, GitHub Copilot CLI, and OpenClaw operational metrics are filtered out |diff --git a/docs/cli/endpoint-onboarding.mdx b/docs/cli/endpoint-onboarding.mdxindex 80a6df88..f20829eb 100644--- a/docs/cli/endpoint-onboarding.mdx+++ b/docs/cli/endpoint-onboarding.mdx@@ -77,8 +77,9 @@ The explicit `beacon endpoint install --connect` flag is unchanged: it presets Mand skips the destination question.The wizard never appears non-interactively. Package postinstall scripts, MDM-deployments, `--system` installs, CI, `--dry-run`, and any piped or redirected stdin-skip it silently. These paths remain account-free.+deployments, `--system` installs, CI, `--dry-run`, `TERM=dumb`, and any piped or+redirected stdin skip it silently, including a redirect to `/dev/null`. These paths+remain account-free.## Flags@@ -122,7 +123,10 @@ beacon endpoint onboarding```The answer is stored as `onboarding.destination` in `~/.beacon/profile.json`;-managed selections also store `onboarding.privacy_mode`. `--json` exposes both:+managed selections also store `onboarding.privacy_mode`. Setup completed through an+account records `onboarding.outcome` as `authenticated` with the signed-in email;+setup finished without one after a failed sign-in records `skipped` and no email,+since no account authorized that run. `--json` exposes all of them:| Value | Printed as ||-------|------------|diff --git a/docs/log-forwarding/asymptote.mdx b/docs/log-forwarding/asymptote.mdxindex 2f728a2c..870bf7ac 100644--- a/docs/log-forwarding/asymptote.mdx+++ b/docs/log-forwarding/asymptote.mdx@@ -7,7 +7,7 @@ description: "Forward Beacon endpoint events to Beacon's managed ingest serviceBeacon 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 a Beacon-run endpoint. It is preselected during interactive onboarding, but nothing is forwarded until the separate connect command mints a device key and starts the forwarder. Choosing Local explicitly opts out. 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. It is preselected during interactive onboarding, and confirming it mints a device key and starts the forwarder in the same command, once the local install has succeeded. Signing in alone forwards nothing. Choosing Local explicitly opts out. 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.diff --git a/docs/security/data-flow-threat-model.mdx b/docs/security/data-flow-threat-model.mdxindex 6d79fc27..44b8f515 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. 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 |+| Unintended hosted telemetry | Account sign-in forwards nothing. Managed is preselected, and confirming it starts forwarding within the same command, which the confirm screen states before the choice is accepted, naming what the selected privacy mode sends. Choosing Local forwards nothing, and `beacon endpoint disconnect` stops a connected endpoint. 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 |