Skip to content

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

share: reach api.beacon.sh, respect Metadata-only, redact Beacon CLI tokens and AWS secrets (#930)

Shukan Shah5044aaa18d03
diff --cc docs/changelog/cli.mdx
index 7b1daed2,efa5a028..ca2c8d60
--- a/docs/changelog/cli.mdx
+++ b/docs/changelog/cli.mdx
@@@ -12,10 -12,10 +12,13 @@@ Stay up to date with the latest change
## October 2026
- **Setup ends at the dashboard** · Confirming Beacon Cloud in the `beacon endpoint install` wizard used to end on some forty lines of file paths, connect details, an MCP table and per-runtime steps, and nothing pointed to the hosted dashboard. It now ends on four lines: the account, device and privacy mode; the session backfill; the dashboard URL; and where Beacon Cloud MCP was added. Beacon then opens the dashboard in your browser, except with `--no-browser`, over SSH, or on Linux without a display. The sign-in wait screen now also asks you to open the URL in the browser where you are signed in to beacon.sh, and cancelling the wizard says that nothing was installed and how to start again. `beacon endpoint connect` and `beacon mcp connect` print the same output as before. See [Onboarding](/cli/endpoint-onboarding#when-setup-finishes).
+ - **`beacon share` reaches beacon.sh's API** · Sharing sent its requests to `https://beacon.sh/v1/traces`, which the beacon.sh web host does not serve, so every share from a beacon.sh sign-in or key failed with "the trace does not exist on https://beacon.sh (HTTP 404)". A beacon.sh credential now shares through `https://api.beacon.sh`, and `BEACON_API_URL` names another API host. A 404 that is a web page rather than the API's own reply now stops the share with `<url> has no trace API (HTTP 404: endpoint not found)` instead of being read as a trace that does not exist yet. See [Where the requests go](/cli/share#where-the-requests-go).
+ - **Sharing follows Metadata-only privacy** · On an endpoint that forwards to Beacon Cloud in Metadata-only mode, `beacon share`, `refresh`, `--follow` and the git pre-push hook uploaded the session's prompts, answers, command output and diffs anyway. They now leave out exactly what forwarding leaves out, including on a machine connected in system mode, whose enrollment only root can read, and share as Metadata-only when the mode cannot be read at all. They take no title from the session, whose title is usually its first prompt; `--title` still sets one. Event ids are unchanged, so re-sharing upserts the same events. See [Metadata-only endpoints](/cli/share#metadata-only-endpoints).
+ - **Redaction catches Beacon's sign-in token and AWS secret keys beside their key id** · Redaction already removed `bcn_api_`, `bcn_device_`, `bcn_mcp_` and `bcn_enfdev_` keys. It now also removes the `beacon login` token (`bcn_cli_…`), MCP refresh tokens (`bcn_mcprt_…`) and the sign-in's `bcn_code_…`, `bcn_client_…` and `bcn_exchange_…` values, and the 40-character AWS secret key that follows an `AKIA…` or `ASIA…` key id, as in a credentials CSV. Both used to reach the log and Beacon Cloud unredacted. See [What is redacted](/security/retention-redaction#what-is-redacted).
- **Self-update installs only Beacon-signed packages, over https** · The macOS self-updater took the Apple team a package must be signed by from `update-manifest.json`, which is unsigned, matched it as a substring of the signature output, and skipped the check when the manifest named no team. Whoever could rewrite the manifest could have any notarized package installed as root. The team is now built into `beacon` (Asymptote Labs, `3A98D35XJR`) and must match the package's installer signer exactly, for self-update and the enterprise edition install alike. The manifest and the package must also be fetched over `https`, plain `http` only to a loopback mirror and never through a redirect, so a `managed.json` that names an `http://` update URL on another host stops updating until it is changed to `https`.
+- **Beacon Cloud shows new sessions within seconds** · The forwarder held runtime events for up to 60 seconds before sending a batch, so right after `beacon endpoint connect` the dashboard stayed empty for a minute and looked broken. It now sends a partial batch after 10 seconds, and paces runtime requests at one a second, the rate the ingest service allows each device, so a backfill or a backlog after an offline period goes out in full batches without being turned away. Install, repair and package upgrades rewrite a connected forwarder's config and restart it; what it has already read is kept. See [Beacon Cloud](/log-forwarding/asymptote).
+- **Backfilled Claude Code sessions keep their own times** · Claude Code writes some transcript records (the permission mode, the session title, the last prompt and similar) without a timestamp, and the first of them is often where a session starts. Session sync stamped those with the time of the sync, so every backfilled session appeared to run until Beacon was installed. They now take the session's earliest recorded time, or the transcript's modification time when no record has one. Events already written keep their old time.
+- **Backfilled Codex sessions are named after what you typed** · Codex records the environment it runs in, the repository's AGENTS.md and your configured instructions as user messages, and session sync recorded them as prompts. Every backfilled Codex session was then titled `<environment_context>` or `# AGENTS.md instructions for …`, and the dashboard grouped them all as recurring. Those messages are no longer prompts, using the block kinds newer Codex builds record and the text older ones open with.
- **The Jamf hook repair script no longer hands the console user root** · `jamf/claude/common/repair-hooks.sh` runs as root. It granted the console user permission to add and delete entries in `/var/log/beacon-agent`, which let them replace the runtime log with a link that the root collector then opened, and it ran `chown -R` on `~/.beacon` as root, which a planted hard link turned into ownership of a root-run binary. The directory grant is gone, and the script now removes every grant that adds or deletes entries there, including ones earlier runs gave a previous console user and the one the Jamf guide's snippet used to add. It creates and fixes up `~/.beacon` as the user, refuses a symlinked directory, and moves aside one the user does not own. The Jamf guide explains how to remove the old grant by hand.
- **The scheduled inventory job follows every moved runtime directory** · The job starts without your shell's environment, so a per-user install or repair records the variables that move a runtime's user directory into it. It recorded `CODEX_HOME`, `HERMES_HOME`, `CLINE_DIR`, `GEMINI_CLI_HOME` and `CLAUDE_CONFIG_DIR`, and now also `KIRO_HOME`, `KIMI_CODE_HOME`, `DSH_HOME`, `OH_PERSISTENCE_DIR`, `OPENCLAW_STATE_DIR`, `XDG_CONFIG_HOME` (Muse, and VS Code on Linux), `PI_CODING_AGENT_DIR`, `OMO_CODING_AGENT_DIR`, `SENPI_CODING_AGENT_DIR`, `PRIME_AGENT_CODING_AGENT_DIR`, and Oh My Pi's `PI_CONFIG_DIR`, `OMP_PROFILE` and `PI_PROFILE`. With one of these set only in your shell, the job used to inventory the default directory while the runtime read the moved one. See [Inventory heartbeats](/cli/endpoint-inventory#inventory-heartbeats).
- **Pi extension follows `PI_CODING_AGENT_DIR`** · `beacon endpoint hooks install --harness pi`, `beacon endpoint discover` and inventory now use `$PI_CODING_AGENT_DIR/extensions/beacon.ts` when `PI_CODING_AGENT_DIR` is set, as Pi does, including a leading `~`. They previously always used `~/.pi/agent`, so with the variable set the extension went where Pi never loads it while discovery reported Pi as enabled, and live capture silently recorded nothing. Session status and sync already followed the variable; all of them now resolve the directory the same way.