Skip to content

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

docs(changelog): unreleased fixes from #1013–#1103 (#1104)

kyle-elliott-asymptote7b23b1543898
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdx
index cd0c786d..d3e3f2c9 100644
--- a/docs/changelog/cli.mdx
+++ b/docs/changelog/cli.mdx
@@ -9,6 +9,65 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
---
+## Unreleased
+
+- **Threat rules can match parsed shell commands** · Rules on spec `threat-rules/v1.2` can read `e.command.parsed_commands`: each command's name, arguments, environment prefixes, pipeline stage and the files it writes or deletes. `curl-pipe-to-shell`, `recursive-root-delete` and `base64-decode-piped-to-shell` use it, so they now catch `curl … | sudo -u root bash`, `| /usr/bin/env bash`, `{ curl …; } | sh`, `rm -rf "$HOME"` and `bash -lc '…'` scripts, and no longer fire on the same text inside a quoted string, a commit message or a here-document, or on `rm -rf ~/project/build`. An older Beacon skips v1.2 rules with a warning.
+- **Shared sessions stay current after more kinds of `beacon share` call** · The dashboard now recognises `beacon share` run under `sudo`, `nohup`, environment assignments or backticks, or cut off when a long command was captured, so a session that shared itself is no longer marked stale.
+- **Hook events keep a command's closing quote** · A command ending in a quoted word, such as `git commit -m "fix: thing"`, was recorded without its final `"`.
+- **`beacon git` reads shell commands with a real shell parser** · Commit links no longer credit a session with words from a `# comment`, a here-document body, or an option value (`install -m 0755`, `perl -M…`), and now follow `if`/loops, brace expansion, `sudo -u`/`env` wrappers, `cp -t DIR`, `sed -i -e`, `perl -pi -e` and macOS `sed -i ''`. A command captured incomplete no longer contributes partial paths.
+- **Destination packs work with any log path** · Datadog and Elastic configs are valid YAML on Windows and with quotes or control characters in the path, the smoke-test scripts the packs install no longer break on, or run, `$`, backticks, quotes or `}` in the log path, and `beacon endpoint wazuh` refuses a log path containing `<`, which Wazuh cannot read, instead of writing a config Wazuh rejects.
+- **Setup menus no longer pick an option on a modified arrow or function key** · Shift or Option with an arrow key, or F2, in a setup menu chose an option without Enter; modified arrows now move the selection, and Esc cancels the menu as it does in the setup wizard.
+- **Inventory content capture uses Beacon's full redaction** · With `include_contents` on, tokens in MCP args, URLs, auth headers and skill files (`Bearer`/`Basic`, `--token=…`, `--api-key VALUE`, `?api_key=…`, `docker -e`, URL passwords, provider token formats such as `ghp_` and JWTs) were sent unredacted; inventory now applies the same redaction as session telemetry, with `[REDACTED]` as the placeholder. Secret-named keys are judged by whole words, so `DB_PASS` and `passphrase` are redacted while `author`, `max_tokens: 4096` and `token_type: bearer` are kept, in telemetry too, and a `Bearer` value no longer swallows the next line.
+- **Hooks under a home path with an apostrophe stay with their own runtime** · With a home directory such as `C:\Users\O'Brien`, status, repair and uninstall treated another runtime's Beacon hook as their own, and uninstall could delete it.
+- **Inventory lists every installed skill** · Skills named `build`, `dist`, `vendor`, `tmp` or `temp` were left out of the inventory although the runtime loads them.
+- **`beacon git` works when `log.showSignature` is on** · `beacon git link`, `beacon git notes` and the post-commit hook failed or misread commits in repositories that show commit signatures, and a signed cherry-pick could be credited to the current session.
+- **File URIs are recorded as real paths** · Files that MCP tools and editors report as `file:///C:/…` are recorded as `C:/…`, and `beacon git link` now reads `file://` paths with spaces or a `localhost` host, so rules and commit links see the real file.
+- **Shell commands are recognised the same way everywhere** · Commands Codex ran through `shell_command` (Codex 0.135–0.149) now show up as commands in both live telemetry and imported sessions, the older `shell` tool and argv-style commands show the command line instead of raw JSON or brackets, Claude Code's PowerShell tool counts as a command in imported sessions, and an MCP tool with a `cmd` argument is no longer mistaken for a shell command.
+- **`beacon endpoint install` no longer breaks a commented Codex `config.toml`** · A `# comment` after a table header made install delete the user's `[mcp_servers.<name>]` table or write a second `[otel]` table Codex refuses to load.
+- **Passwords in URLs with no user name are redacted** · `redis://:password@host` and similar URLs now have the password redacted from logs.
+- **`beacon endpoint update` works on Linux .deb/.rpm installs** · It reported that no package was available and refused `--apply`; it now finds the format-specific package in the release manifest.
+- **`beacon endpoint install` no longer wipes an unreadable Claude settings file** · A `~/.claude/settings.json` Beacon couldn't parse was replaced with only Beacon's settings. Install now stops and names the file and the parse error instead, for Gemini too, and status reports say which file is invalid.
+- **Inventory heartbeats stop re-sending unchanged snapshots** · A machine where nothing changed could report a change and re-upload its full inventory when the same MCP server name was configured in several Claude Code projects. The snapshot digest no longer depends on the order entries are listed in.
+- **VS Code settings with comments are read and kept** · `beacon endpoint discover`, `status` and `doctor` reported Copilot telemetry as misconfigured for a commented `settings.json`, and `beacon endpoint integrations vscode setup` refused the file. Both now accept it, and setup changes only Beacon's telemetry keys, leaving your comments, key order and indentation as they were.
+- **Dashboard labels no longer break emoji or accented characters when shortened** · Long prompts and names are shortened between visible characters, so emoji, flags and accents at the cut stay whole.
+- **Hand-written `--platform=<name>` hooks are recognised** · `beacon endpoint hooks status` and `uninstall` now see Claude Code, Codex, Factory and Qwen hooks written with `--platform=<name>`.
+- **Google OAuth access tokens are redacted** · `ya29.…` tokens printed on their own, by `gcloud auth print-access-token` or the GCE metadata server, are now redacted from logs.
+- **Reading `.env.example` and other dotenv templates is no longer a credential read** · Templates such as `.env.example`, `.env.sample` and `.env.local.example` no longer raise credential-file-read or the read-then-egress, destructive, MCP or handoff correlations; real `.env` files still do.
+- **opencode records every file a shell `rm` deletes** · A shell `rm` that removes several files now records a delete for each, not just the first, and comments, variables or globs in the command are no longer recorded as files.
+- **`beacon scan` no longer prints broken characters** · A command or prompt shortened to fit one line of `beacon scan` output could be cut in the middle of an accented, CJK or emoji character. It is now cut between characters.
+- **Env-prefixed git history rewrites are flagged** · `GIT_SEQUENCE_EDITOR=… git rebase -i`, `GIT_EDITOR=… git commit --amend` and other `VAR=value git …` forms now raise git-history-rewrite.
+- **Context utilization uses the right window for more Claude ids** · Dotted ids from Copilot and OpenRouter (`claude-sonnet-4.6`) and Bedrock ids (`us.anthropic.claude-sonnet-4-6-v1:0`) now use the 1M window instead of 200K or none.
+- **`ssh-add -E md5 -l` is flagged as key enumeration** · Options before `-l`/`-L` no longer hide an ssh-agent key listing.
+- **Environment-dump alerts follow the data** · env-dump-piped-to-network now fires when the environment is actually piped, substituted or redirected into a network sender (including `curl --json @-` and `curl -d "$(env)"`), and no longer on unrelated commands such as `set -e; … | curl`.
+- **crontab installs are flagged when followed by another command, and backups no longer are** · `crontab <file> && …` and files under `~` now raise crontab-modification; `crontab -l > backup` no longer does.
+- **Archives piped into an upload are flagged however curl reads them** · archive-then-upload now matches any curl or wget upload of the piped archive (`-F'file=@-'`, `-d@-`, `--upload-file -`, `/dev/stdin`).
+- **PATH-injection alerts target shadowing, not tool installs** · path-injection-into-login-file now fires when a PATH line written to a startup file (by `>>` or `tee`) adds a world-writable, relative or current directory, and no longer on routine entries such as `~/.cargo/bin`.
+- **gpg secret-key exports are flagged however they're spelled** · `gpg2`, `--export-secret-key` and abbreviations such as `--export-secret-k` now raise gpg-keyring-access.
+- **Writes to sudoers through `tee` are flagged however `tee` is called** · `tee --append`, `tee -ai` and sudoers as a later `tee` target now raise sudoers-nopasswd-tampering.
+- **`modprobe` loads are flagged with parameters or a following command** · `modprobe nvidia_drm modeset=1` and `modprobe br_netfilter; sysctl --system` now raise kernel-module-load.
+- **Push redirection through git config is flagged** · `git config remote.<name>.pushurl <url>` and one-off `git -c remote.<name>.url=…`/`pushurl=…` now raise git-remote-tampering.
+- **ssh ProxyCommand shell escapes are flagged however `-o` is written** · `-oProxyCommand=…`, `-o 'ProxyCommand=…'`, `-o 'ProxyCommand …'` and the same through `scp` or `sftp` now raise shell-escape-via-interactive-tool.
+- **`rm -fr` and `rm -rfv` count as high-risk in approval rules** · The approval-abuse rules now treat any `rm` flag cluster with both `r` and `f`, such as `-fr` or `-rfv`, like `rm -rf`.
+- **`systemctl` options before `enable` no longer hide persistence** · `systemctl --now enable`, `systemctl -q enable` and `--root=… enable` now raise persistence-install-command.
+- **root-equivalent-group-add is accurate under `sudo`** · It now flags `usermod --groups` and `gpasswd --add`, and no longer fires on every `sudo usermod -aG` or `sudo adduser` regardless of the group.
+- **Base64 payloads piped to a shell by path are flagged** · `| /bin/bash`, `| /usr/bin/env bash`, `| /opt/homebrew/bin/bash` and `| sudo -E bash` now raise base64-decode-piped-to-shell.
+- **Fork bombs are flagged under any name or spacing** · fork-bomb-pattern now matches the shape of the classic `:(){ :|:& };:`, so `:(){ :|: & };:` and renamed versions such as `f(){ f|f& };f` raise it too.
+- **`dd` disk fills are flagged in either operand order** · `dd of=… if=/dev/zero` now raises disk-fill-attempt, as `dd if=/dev/zero of=…` already did.
+- **Root bind mounts are flagged however they're written** · `docker run --volume=/:…`, `--mount source=/` (or `src=/`) and their quoted forms now raise privileged-container-run.
+- **Wide `ps` scrapes for secrets are flagged** · `ps auxww` and `ps -eo args` piped into a search for tokens or passwords now raise process-table-secret-scrape.
+- **Browser-session rules cover Edge on macOS and pre-release channels** · Reading cookies or saved logins from Microsoft Edge on macOS, or from the Beta, Dev and Canary channels of Edge and Chrome, now raises the browser-session findings.
+- **Less common git hooks are flagged** · Planting a `reference-transaction`, `post-index-change` or other git hook missing from the list now raises git-hook-installed.
+- **`codex -s danger-full-access` is flagged** · Permission-bypass detection now catches codex's short `-s` sandbox flag, not just `--sandbox`.
+- **SSH tunnels are flagged wherever the forward flag appears** · `ssh -N -R …`, `ssh -fNL …` and `ssh host -R …` now raise ssh-tunnel-egress.
+- **Refspec force-pushes to a protected branch are flagged** · `git push --force origin HEAD:main` and similar `src:dst` pushes now raise the protected-branch finding, and a branch such as `main-backup` no longer does.
+- **world-writable-chmod catches 666-style modes** · Any octal mode that grants write to others, such as `chmod 666` or `chmod 1777`, now raises world-writable-chmod, and a numbered file name such as `chmod +x 007.sh` no longer does.
+- **More setuid forms detected** · `chmod +s`, `chmod 6755` and `chmod 04755` now raise setuid-or-root-shell-escalation, and a numbered file name such as `chmod 644 2024.csv` no longer does.
+- **Grok session sync no longer duplicates events after a partial sync** · A sync that stopped partway through a session re-sent prompts, replies and tool calls it had already written under new ids, so they appeared twice.
+- **Session syncs no longer lose their own events to log rotation** · Every `beacon endpoint <runtime> sync` except Claude Code's and Devin CLI's could write past the runtime log's rotation window, so rotation deleted the sync's first events while it still reported success. Syncs now stop before that, exit non-zero, and leave the rest for the next sync; `--rotate-bytes` sets the window. The install backfill reports a runtime that stops this way as limited rather than failed.
+- **`curl … | sudo -E bash` is detected** · Piping a download into `sudo` with flags, such as NodeSource's `sudo -E bash -`, now raises curl-pipe-to-shell.
+- **Root-wipe commands are detected** · `rm -rf /*`, `rm -rf --no-preserve-root /` and `rm -r -f /` now raise recursive-root-delete.
+- **`beacon handoff resume --launch` no longer reports a started launch as cancelled** · When the new terminal picked up the launch just as the wait timed out, Beacon said the launch was cancelled while the runtime started anyway, so a retry could start a second one.
+
## October 2026
### v1.3.46 · October 22, 2026
diff --git a/docs/changelog/sdk.mdx b/docs/changelog/sdk.mdx
index c0232847..1c0bdbd0 100644
--- a/docs/changelog/sdk.mdx
+++ b/docs/changelog/sdk.mdx
@@ -9,6 +9,11 @@ Stay up to date with the latest changes to the Beacon Observe SDK.
---
+## Unreleased
+
+- **Anthropic `instrumentModules` example fixed** · The documented `import Anthropic from` example crashed `Observe.initialize()`; pass the module namespace (`import * as Anthropic`) instead, and a clear error now says so.
+- **Empty environment variables are ignored** · A declared but empty `ASYMPTOTE_BASE_URL` made `Observe.initialize()` throw `Invalid URL`, and an empty `OTEL_SERVICE_NAME` exported spans with a blank service name. Empty values now fall back to the defaults.
+
## October 2026
### v0.2.0 · October 22, 2026