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
docs(changelog): v1.3.61
shukieshah5947adadc7fa
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdxindex 7e7180a3..5c5a5480 100644--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@ -11,7 +11,11 @@ Stay up to date with the latest changes to the Agent Beacon CLI.## Unreleased-Changes on `main` since v1.3.60. They ship in the next release.+Changes on `main` since v1.3.61. They ship in the next release.++## November 2026++### v1.3.61 · November 13, 2026- **Cursor cloud agents no longer leave partial sessions on the endpoint** · While the Cursor desktop app shows a cloud agent, it runs the user-level hooks on your machine for that agent's reasoning and subagent events, but not for its prompts, tool calls, replies or turn ends, which run in Cursor's VM. Beacon recorded those calls as `agent.reasoning` and `subagent.stopped` events from the machine, so a cloud agent looked like a local Cursor session with only reasoning in it, and a subagent's reasoning formed a session of its own. A Cursor hook payload that names a cloud agent (`bc-…`) or one of its subagents (`task-call-…`) and no workspace now writes nothing outside a cloud sandbox. A cloud agent on a self-hosted worker, which runs in a checkout, is still recorded, and so is everything the [Cursor Cloud Agents](/runtimes/cursor-cloud-agents) project hooks capture in the VM.- **Cursor cloud capture needs nothing committed to the repository** · `beacon cloud cursor print-setup` printed a script that installed the binary and told you to commit Beacon's hooks to `.cursor/hooks.json`, and Cursor then ran those committed hooks in every local Cursor session on the repository too. The script now writes the hooks into the checkout itself and lists them in `.git/info/exclude`, so cloud agents never see them as a change to commit. Paste it into the environment's **Install script**: Cursor runs it when it creates a Build, before any agent starts, so the hooks are in place for every agent in the environment. A repository that commits its own `.cursor/hooks.json` is left alone, `print-setup` takes `--safe-hooks`, and only `beacon-hooks` is extracted from the release. See [Cursor Cloud Agents](/runtimes/cursor-cloud-agents).@@ -25,8 +29,9 @@ Changes on `main` since v1.3.60. They ship in the next release.- **Inventory names each MCP server's package and each skill's source** · An inventory snapshot knew an MCP server or skill only by its configured name, which several Beacon Intel artifacts can share. Each MCP server record now carries `package` (`npm:<name>` or `pypi:<name>`, no version) and `package_registry` `public` when its launch command runs a package from the public registry. When the command, the server's env, or the npm, pip or uv configuration in the home, the system's locations or the project a server runs in points that ecosystem elsewhere, `package_registry` is `private` and the name stays off the record. On Windows that configuration includes the per-user `AppData` and machine `ProgramData` locations even when the scanning job's environment does not name them. A skill the skills CLI (`npx skills add`) installed from GitHub carries `intel_key`, `skill:<owner>/<repo>#<name>`, from the CLI's `~/.agents/.skill-lock.json`; a lock beside a repository's own skills is ignored, since the repository could claim any source. The system inventory job runs as root, so it reads that configuration in a short-lived child process running as the console user with their groups: what the user's own launchers cannot read, Beacon does not either, and a snapshot never reflects a file only root can see. Configuration that exists but cannot be read (a file or folder the user may not open, a folder macOS privacy protection guards, a FIFO) holds its ecosystem back as `private`. `intel_check_installed` now checks such a skill by default, by its exact key; other skills still go by name only with `include_private_names`. Every endpoint sends one fresh snapshot after upgrading.- **Redaction covers an Authorization header with any scheme** · An `Authorization` header whose scheme was not Bearer, Basic, Token or Digest kept its credential. `Authorization: ApiKey <key>` (Elasticsearch), and the same with `SSWS` (Okta), `Bot` (Discord), `Splunk`, `Negotiate` or a vendor's own scheme, was written as `Authorization: [REDACTED] <key>`: the scheme word was replaced and the key stayed, in command lines, tool output and everything else Beacon retains or forwards. The scheme and the credential are now replaced together, as `Authorization: [REDACTED]`, which is what a header quoted whole as a JSON value already became. Bearer, Basic, Token and Digest keep their scheme name as before. A scheme that sends a list of parameters (Digest, Hawk, AWS Signature V4) has every one replaced, where the scheme rules used to take the first parameter's name and leave the rest; a copy of the credential elsewhere in the same text is removed, as a labeled secret's copies are; and a base64url credential that starts with `-` is no longer mistaken for a flag and kept.- **Redacted values inside JSON-encoded commands stay valid JSON** · A command held as a JSON-encoded string, such as a tool's arguments, quotes its arguments with `\"`. An unquoted secret after a label, a URL parameter or an Authorization scheme took the backslash of the closing `\"` with it, so `"curl -d \"token=x\""` became `"curl -d \"token=[REDACTED]"`, a bare quote that ended the string, and whatever read the arguments back could not parse them. The value now ends before the backslash.--## November 2026+- **Hook events from bubblewrap sandboxes reach the log** · In a sandbox without its own user namespace, such as bubblewrap installed setuid the way sandboxing launchers run it, a hook dropped every event without a word. The client refused the bind-mounted ingest socket, because inside the sandbox the directories above it belong to the launching account, and the fallback then wrote the event into the sandbox's throwaway root, where it vanished. The client now accepts directories above the socket owned by the sending account and checks, after connecting, that root serves the socket. No writer creates the system log's directory or a missing home any more, the account spool takes events when the log is unreachable or on a read-only mount, and neither the log nor the spool is ever written to a sandbox's temporary root. See [Agents in a sandbox](/security/restricted-log-access#agents-in-a-sandbox).+- **Hooks in a workspace-only sandbox stage their events in the workspace** · Some sandboxes mount nothing of Beacon's and let hooks write only inside the session's workspace: DeepSeek Harness's own sandbox, the Gemini CLI and Qwen Code container sandboxes, or an operator sandbox that mounts only the project. When every other route fails, a hook now stages its events in `<workspace>/.beacon/spool/<harness>/<session>/`, ignored by git, and prints one note per session with the [`beacon endpoint spool drain`](/cli/endpoint-spool) command that delivers them. The session sync, the install backfill and the session's next hook that reaches the log drain them as well, and `beacon endpoint spool status` shows what is waiting. Beacon reads only the spools of sessions it has recorded, under `workspace_spool_roots` an operator configures, or in a `--workspace` you name; it admits only lines for their own harness and session, writes them again through its own redaction and size limits, and never follows links. The DeepSeek Harness spool now follows the same contract.+- **OpenCode 2.x: debug logging, the model, shadowed copies and `OPENCODE_CONFIG_DIR`** · On OpenCode 2.x `BEACON_OPENCODE_DEBUG` logged nothing; the plugin now writes JSON lines to `~/.beacon/endpoint/logs/opencode-plugin-debug.log`, starting with the hooks it registered. Events now carry the model, read from `session.step.started`, where 2.x payloads left it empty. OpenCode 2.x runs only the first plugin with a given id, so `beacon endpoint hooks status` now reports a copy OpenCode ignores as not installed and lists such copies in `ignored_plugin_paths`, and install prints the same note. Beacon honors `OPENCODE_CONFIG_DIR` for the plugin, status, discovery, inventory and `mcp connect`, and status recognizes a Windows install.### v1.3.60 · November 11, 2026