v0.11.0

• Recognises DeepSeek Harness tools. The harness names its tools in lowercase — edit,
  write, bash — where Claude Code capitalises them, so Beacon saw none of its edits and
  silently reported nothing. Tool names are now a set per harness rather than a chain of
  equality checks, and str_replace_editor is handled too: it is the one edit tool that
  calls its file argument path instead of file_path.
• Beacon now covers three harnesses. Verified against real payload shapes for each: an
  edit with file_path, a str_replace_editor with path colliding with it, and a
  destructive git checkout through bash raising the working-tree guard.

v0.10.6

• Retracts 0.10.5. Beacon's hooks do fire in Codex. 0.10.5 concluded they did not, on
  the strength of an empty daemon log and the absence of any type: "command" hook in
  OpenAI's bundled plugins. Both observations were real; the conclusion drawn from them was
  wrong.

  The activity log settles it. A live Codex session produced the matching pair:

  active | editing | ...\co\work\codex-cli-hook-trigger.txt | 01a06616
  done   | editing | (same file)                            | 01a06616
  

  PreToolUse reported the file the apply_patch was about to create, and Stop cleared
  it when the turn ended. ${PLUGIN_ROOT} does expand in a hook command, and the payload is
  exactly the patch envelope src/patch.js parses.

• Documents the two things that make working hooks look broken, because both fooled this
  project into shipping a wrong conclusion:

  • A running Codex session does not pick up newly installed hooks. Every earlier test
    edited in a session started before the install, which looks identical to hooks not
    working. Restart Codex after installing.
  • The Hooks settings page does not list plugin hooks. It reports "no hooks found"
    while they are installed and firing — the hooks OpenAI's own bundled plugins declare
    don't appear there either. beacon status is the honest check.

v0.10.5

• Corrected the README: Beacon's hooks do not fire in Codex. 0.10.0 claimed parity with
  Claude Code — warned before every edit — on the strength of the documented hook API. The
  runtime disagrees. A real Codex edit produced no report to the daemon, and Codex's log
  contains no hook evaluation whatsoever: no PreToolUse, no apply_patch, no
  hooks.json, not even a rejection.

  Nor is there a working example to copy. Of the six plugins OpenAI bundles, every hook is
  type: "mcp_tool" on Stop; none uses type: "command", none declares PreToolUse, and
  none ships a hooks/ directory — the three things the docs describe and this plugin used.
  The likely reading is that command hooks from a plugin do not run in this build.

  Codex is therefore MCP-only for now, and the README says so. The MCP server does work
  (fixed in 0.10.2) and is verified running in a live session, so Codex stays visible to
  every other agent and can query for collisions; it just is not warned automatically.

  The docs have now been wrong three times on adjacent details — ON_FIRST_USE,
  ${CLAUDE_PLUGIN_ROOT}, and command hooks — so the Codex integration is documented from
  measurement from here on.

v0.10.4

• Fixed: install.ps1 could add a PATH entry that Windows silently discards. cmd.exe
  truncates the combined machine+user PATH at ~2047 characters, and the user PATH comes
  last, so on a machine already at the limit the newly appended entry is cut off. beacon
  then reports "is not internal or external command" while the shim exists and the registry
  entry is right there — a genuinely baffling failure. The installer now measures the
  combined length first. If adding an entry would cross the limit it puts the shim in a bin
  directory already on PATH (~/.local/bin or ~/bin), which costs no length and sits
  earlier so it survives truncation; with no such directory it says so plainly and prints
  the full path to run instead of pretending the install succeeded.

v0.10.3

• npm publishes from the release too. A tag now produces the GitHub release and the npm
  version together, so the two can't disagree about what a version contains. The job runs
  after the release job — a published npm version can never be replaced, a GitHub release
  can — and it skips silently if the NPM_TOKEN secret isn't set, or if that version is
  already on npm, so re-running a release is safe.

v0.10.2

• Fixed: the Codex MCP server never started. Codex does not expand
  ${CLAUDE_PLUGIN_ROOT}, despite the docs listing it as a compatibility alias. It passed
  the literal string through as a directory name, and Codex's own log said so plainly:

  Error: Cannot find module 'C:\...\${CLAUDE_PLUGIN_ROOT}\mcp\server.js'
  MCP server tools unavailable ... server_name=beacon
  

  The plugin listed beacon under "from plugins" in the UI the whole time, which is why
  this looked like it worked. The Codex manifest now declares the server inline with a
  relative path and "cwd": "." — no variable substitution at all, matching the only form
  OpenAI's own bundled plugins use. .mcp.json keeps ${CLAUDE_PLUGIN_ROOT} for Claude
  Code, which does expand it.

• Releases are built by CI. Pushing a v* tag now runs the tests, checks the tag
  matches package.json, builds beacon-plugin.zip with git archive, takes the release
  notes from that version's CHANGELOG section, and publishes a GitHub release with the
  archive attached. The asset name carries no version so
  releases/latest/download/beacon-plugin.zip stays valid across releases.

• README documents installing from a release, both by uploading the archive to the Claude
  desktop app and with claude --plugin-url.

Beacon v0.8.7 — conflict notifications

[0.8.7] — 2026-07-25

Added

• Conflict notifications (Settings -> "Notify me on conflicts", off by default). When two agents edit the same file, the daemon fires a native OS notification — so it reaches you even when the dashboard tab is closed or backgrounded (as long as the daemon is running; pairs with start-on-login). Deduped per file with a 2-minute cooldown. Zero-dependency: Windows toast via PowerShell, macOS osascript, Linux notify-send.

Beacon v0.8.6 — conflict-first dashboard

[0.8.6] — 2026-07-25

Changed

• The dashboard leads with conflict status, not a session count. Beacon is a conflict detector (reads arent even tracked), so the empty state no longer says the misleading "No agents active." Instead: idle shows a large centered "No conflicts"; agents editing without overlap show a subtle "No conflicts · N agents editing" line at the bottom; a real overlap shows a prominent "Conflict" banner above the highlighted rows.

Beacon v0.8.5

[0.8.5] — 2026-07-25

Fixed

• The Update button now works. "Update (git pull)" used to pull and then just tell you to restart manually — which for an already-current checkout looked like it did nothing. It now pulls and auto-restarts the daemon to load the new code, so the version updates in one click.
• No more flashing black console window on Windows when updating, installing hooks, or restarting — git / node spawns now run with windowsHide.

Beacon v0.8.4

[0.8.4] — 2026-07-25

Fixed

• The "Group edits" row no longer shows a pointer cursor on its hint text — it reused the checkbox-label style (cursor: pointer), which made the plain description look clickable. It is not clickable; now it renders as normal text.