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): unreleased fixes from #1098–#1142 (#1145)
kyle-elliott-asymptote0f39026ce341
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdxindex 1ca5a02b..b20e9805 100644--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@ -9,6 +9,21 @@ Stay up to date with the latest changes to the Agent Beacon CLI.---+## Unreleased++- **Inherited per-signal OTLP settings no longer divert Claude telemetry** · An `OTEL_EXPORTER_OTLP_{LOGS,METRICS,TRACES}_ENDPOINT`, protocol or headers setting in the environment or Claude's settings sent Claude's telemetry past Beacon's collector, in `beacon ci` and with `beacon endpoint`, which still reported telemetry as enabled. Beacon now overrides them, and `beacon endpoint status` flags one that points elsewhere.+- **`beacon git` links symlinks a session creates** · When a session's directory ran through a symlink, such as `/tmp` on macOS, a link the session created was resolved to its target: `ln -s ../shared/config.json cfg.json` linked nothing, and `ln -s a.txt alias.txt` was credited as `a.txt`. The link itself is now recorded.+- **Local MCP server follows JSON-RPC more closely** · `beacon mcp serve` changed large numeric request ids (above 2^53, or forms like `1e3`) when echoing them, left out `id` on parse errors, and rejected MCP `ping`; ids are now returned exactly, errors carry `"id": null`, and `ping` is answered.+- **CI uploads no longer overwrite each other within a workflow run** · `beacon ci --upload s3|gcs` and the GitHub Action's artifact upload used one name for every job, matrix leg and session in a run, so only the last survived (and Action matrix legs after the first failed). Each session now uploads under its own name: objects are keyed `<prefix>/<repo>/<run_id>/<attempt>/<job>/<session>/runtime.jsonl`, which changes the layout for anyone reading these buckets.+- **Local ingest and lens manifests reject stray closing brackets** · A line or manifest that ended with an extra `}` or `]` after a valid object was accepted and the extra text silently dropped; it is now rejected as malformed.+- **Codex CLI and Codex Desktop are told apart everywhere** · Codex CLI 0.158 and newer report the same service name as the desktop app, so live capture recorded every terminal session as `codex_desktop`, while `beacon endpoint codex sync` and the install backfill recorded every Desktop session as `codex_cli`. Live capture, imports and token usage now all use the `originator` Codex records for each conversation: terminal, `codex exec` and VS Code extension sessions are `codex_cli`, and desktop app sessions are `codex_desktop`.+- **Git linking, sharing and handoff work in directories whose path ends in a space** · Beacon trimmed whitespace from the work-tree root, session directory and recorded file paths, so `beacon git link` and the post-commit hook failed with "cannot change to …", files like `sub /notes.md ` were attributed to `sub/notes.md`, `beacon share --list` found no session there, and `--cwd` for `beacon share` and `beacon handoff resume` pointed at the wrong directory. Paths are now kept exactly as recorded.+- **`beacon git` follows links, copies and moves into a directory** · `ln -s ../shared/config.json`, `cp a b out/`, `ln -s ../a ../b links`, `git mv a b dir` and GNU's `--target=` abbreviation now record the files they actually create (`config.json`, `out/a`, `links/a`, `dir/a`), so commit links no longer miss them or record the directory itself; `git mv -n` no longer counts as a move.+- **Hook setup recognises Beacon's own hooks more precisely** · `beacon endpoint hooks` status, repair and uninstall, and Cursor's duplicate-event check, treated any command containing `beacon-hooks` as Beacon's, such as a wrapper script or a folder named `beacon-hooks backup`; they now match only Beacon's hook binary, including at paths with spaces.+- **Egress rules agree on what sends data, and catch netcat uploads** · The eight rules that flag uploads and exfiltration each had their own idea of a network sender, so uploads with `nc`, `ncat`, `netcat`, `socat` or bash's `/dev/tcp` (including to termbin) were missed by some, and a commit message or `grep` that only mentioned a tool and a host could trigger them. They now share one check that sees through `sudo`, full paths and `bash -c`, and no longer fire on mentions. `credentials-in-curl-data` counts only a credential sent as the request body, and also reads wget's `--post-data`/`--post-file`.+- **Cursor IDE records each event once** · Cursor also runs the Claude Code hooks in `~/.claude/settings.json`, so with both runtimes set up every Cursor session start, prompt, approval and stop was recorded twice and a policy provider was asked twice. The Claude Code copy now steps aside when Beacon's Cursor hook already covers that event.+- **Copied and renamed Hermes profiles keep their own event ids** · When two Hermes profiles held copies of the same history (after `hermes profile export`/`import` or a manual copy) and both continued a session, their new messages got the same event ids and one was dropped. Each copy's events now have their own ids, while a profile that was renamed, moved, or is the only copy left keeps the ids already uploaded.+## October 2026### v1.3.50 · October 30, 2026