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
Merge origin/main into claude/issue-911-otlp-host-check
Claude061d6c293eef
diff --cc cli/beacon/internal/endpoint/collector/components.goindex 6b828ea5,043112eb..2f65f662--- a/cli/beacon/internal/endpoint/collector/components.go+++ b/cli/beacon/internal/endpoint/collector/components.go@@@ -9,13 -9,10 +9,13 @@@ import"gopkg.in/yaml.v3")-// requiredProcessors are the processors ConfigYAML puts in every pipeline that a collector older-// than this CLI does not have. A collector refuses a whole config that names a component it does-// not know, so one of these missing stops capture for every runtime, not just the one it serves.-var requiredProcessors = []string{"claude_api_body", "beacon_privacy"}+// requiredComponents are the components ConfigYAML always writes that a collector older than this+// CLI does not have. A collector refuses a whole config that names a component it does not know,+// so one of these missing stops capture for every runtime, not just the one it serves.+var requiredComponents = map[string][]string{- "processor": {"claude_api_body"},++ "processor": {"claude_api_body", "beacon_privacy"},+ "extension": {"loopback_host"},+}// listComponents runs `beacon-otelcol components`, which prints what the binary was built with.var listComponents = func(ctx context.Context, binary string) ([]byte, error) {diff --cc cli/beacon/internal/endpoint/collector/components_test.goindex 9a19e7d5,fe2dc33a..f44fe5d4--- a/cli/beacon/internal/endpoint/collector/components_test.go+++ b/cli/beacon/internal/endpoint/collector/components_test.go@@@ -35,8 -35,7 +35,9 @@@ func TestCheckComponentsRefusesACollect}func TestCheckComponentsAcceptsACollectorWithTheBodyProcessor(t *testing.T) {- stubComponents(t, releaseComponents+" - name: claude_api_body\n - name: beacon_privacy\n", nil)+ stubComponents(t, releaseComponents+" - name: claude_api_body\n module: github.com/asymptote-labs/agent-beacon/collector-builder/exporter/beaconjsonexporter v0.0.0\n"+++ " - name: beacon_privacy\n"++ "extensions:\n - name: loopback_host\n module: github.com/asymptote-labs/agent-beacon/collector-builder/exporter/beaconjsonexporter v0.0.0\n", nil)if err := CheckComponents("beacon-otelcol"); err != nil {t.Fatalf("CheckComponents = %v, want a collector that has claude_api_body accepted", err)}diff --cc docs/changelog/cli.mdxindex 81dd9026,8710bc98..9af6e45a--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@@ -17,8 -30,8 +30,9 @@@ Stay up to date with the latest change## October 2026+ - **Homebrew instructions refresh Homebrew first** · Every install and upgrade command in the docs, the release notes, and the update notice that `beacon`, `beacon version check` and `beacon endpoint update` print now starts with `brew update`. Without it, `brew tap` keeps whatever copy of `asymptote-labs/tap` the machine already has, so a Mac that had installed Beacon before got that older release again, and `brew upgrade beacon` reported no update for up to a day after a release. On an older Homebrew, `brew trust` also failed before anything could update Homebrew itself.- **Status and doctor recognize the hooks install writes** · Since v1.2.0, install writes hook commands with `--log` and `--config` flags in place of the `BEACON_ENDPOINT_MODE=1` prefix, but `beacon endpoint status`, `beacon endpoint doctor` and discovery still looked for the prefix. Every fresh install therefore reported Cursor, Antigravity CLI, Devin CLI, Devin Desktop and Hermes Agent as "hooks exist but endpoint hooks were not found", with telemetry disabled, though the hooks were correct and running, and inventory marked their hooks files as not Beacon-managed. They now use the same check install, repair and uninstall use, which accepts both spellings.+- **The collector's OTLP HTTP receiver rejects non-loopback Host headers** · A web page that DNS-rebinds its own hostname to `127.0.0.1` could post forged logs and spans to `127.0.0.1:4318`, which landed in the runtime log and every destination. The receiver now answers 401 unless the Host header names localhost or a loopback IP, as the dashboard and MCP server already do. Runtimes, the SDK and the browser extension send a loopback Host and are unaffected; gRPC on 4317 is unchanged. Use the `beacon-otelcol` from the same release, since an older one refuses the new config.### v1.3.44 · October 19, 2026