Skip to content

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

docs(changelog): the dashboard prints its launch URL only once the port is bound (#1253)

Kyle Elliottd8e01807f7c8
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdx
index cf07e291..62967651 100644
--- a/docs/changelog/cli.mdx
+++ b/docs/changelog/cli.mdx
@@ -13,6 +13,8 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
Changes on `main` since v1.3.58. They ship in the next release.
+- **The dashboard prints its launch URL only once the port is bound** · `beacon endpoint dashboard` and `beacon lenses preview` printed the `?token=` launch URL, and with `--open` started the browser, before binding their port. When the port was taken, the command printed a URL that served nothing and exited with `bind: address already in use`, and `--open` sent the browser to whatever was already listening there. Both commands now bind first: a taken port prints only the bind error and opens no browser. With `--addr 127.0.0.1:0`, the URL names the port the system picked.
+
- **A URL password after a word ending in `_` is redacted** · The URL rule needed its scheme to start a word, and `_` is a word character, so in `lsv2_sk_mysql://user:pw@host` the scheme `mysql` started no word and the password was kept. A scheme glued to a word that ends in `_` now counts too: `lsv2_sk_mysql://user:[REDACTED]@host`.
- **Codex tool results carry their output live, and MCP calls are MCP calls** · Codex's OpenTelemetry `codex.tool_result` sends a shell command's output, but Beacon kept it only in `raw.attributes`, so rules matching `command.output` saw Codex output only after `beacon endpoint codex sync`. The live event now records `command.output`, the exit code from the header Codex writes above the output (`Process exited with code N`, or `Exit code: N` for `shell` and `shell_command`), and the content marker, with `content.truncated` set when Codex cut the output itself. A nonzero exit or a reported failure raises the severity to `medium`. An MCP server's tool, which Codex reports by its bare name beside an `mcp__<server>` namespace, is now `mcp.tool_invoked` with `mcp.server`, `mcp.tool` and the name `mcp__<server>__<tool>`, and its reply is `gen_ai.tool.call.result`, so indirect-prompt-injection rules read it on both paths. Any other tool's result is `tool.completed` or `tool.failed` rather than `tool.invoked`, with its output as `gen_ai.tool.call.result`, and `tool.command` is the command line rather than the arguments JSON. The live collector and `codex sync` now read a tool result through one shared definition, so their two copies of a call agree. Both copies are still written when the sync runs, as before.