Fork notice: claude-protocol — ground-up rewrite, active development

[weselow]

Hi Aviv,

I forked this project and rewrote it from scratch as claude-protocol (published on npm as claude-protocol).

Submitted PRs to this repo went unreviewed. The underlying tools (beads CLI, Claude Code hooks API) changed significantly since the original release, so I continued independently.

What changed in v3

Solves open issues here:

• Windows support — all 8 hooks rewritten in Node.js (.cjs), cross-platform. Solves Windows support #3 (cc @joshmouch) and Windows support? #1 (cc @Inrego).
• Hook reliability — complete rewrite with proper matcher logic and shared utilities. Addresses PreToolUse Hooks Not Reliably Detecting Subagent Context #2 (cc @StreamlinedStartup).
• Plan mode control — removed multi-agent hierarchy, orchestrator works directly with Task(). Relates to EnterPlanMode not blocked — Claude hijacks orchestration with native plan mode #4 (cc @simon-77).

Architecture:

• Removed 5 specialized agents (Scout, Detective, Architect, Scribe, Discovery) — duplicate built-in Claude Code capabilities
• Removed per-tech supervisor generation — 500+ lines of context with no benefit
• Removed agent personas — outdated prompting pattern
• 19 bash hooks → 8 Node.js hooks (cross-platform)
• Trigger-based rules instead of reference documents
• Checklist verification hook — blocks completion if requirements aren't met
• Session-start dashboard — surfaces open tasks, stale beads, recent knowledge
• Safe merge into existing projects — CLAUDE.md appended, settings.json merged, nothing overwritten

Install: npx claude-protocol init

Full rationale: docs/decisions-en.md

Open invitation

If you return to active development, happy to collaborate. Your original concept is the foundation — credit preserved in README and LICENSE.

[TPreece101]

Thanks for picking this up @weselow - I was thinking of doing something similar as this seems like a cool setup - just needs some love. Does the kanban ui work with your new version? And would you be open to allowing issues on your fork? (I was going to leave one to ask about the kanban ui but it doesn't seem like issues are enabled on the repo 😁)

[Inrego]

Thanks for picking this up @weselow - I was thinking of doing something similar as this seems like a cool setup - just needs some love. Does the kanban ui work with your new version? And would you be open to allowing issues on your fork? (I was going to leave one to ask about the kanban ui but it doesn't seem like issues are enabled on the repo 😁)

I would think it works. The Kanban UI works with Beads, independently from this. And from my findings it worked with Windows already.

[weselow]

Thanks for picking this up @weselow - I was thinking of doing something similar as this seems like a cool setup - just needs some love. Does the kanban ui work with your new version? And would you be open to allowing issues on your fork? (I was going to leave one to ask about the kanban ui but it doesn't seem like issues are enabled on the repo 😁)

Hi! Yes, it works with kanban fork and last dolt update - https://github.com/weselow/beads-web - try new kanban themes))
I started working on it because I use it myself. If any bugs pop up, let me know)
Issues are open now.

[ospector]

@weselow - Thanks for picking this up. looks cool...but does not read beads on my setting.
Would love to help you debug this.
Issues still closed in your repo - so here is what I found:

I have 3 closed beads and also created an open test bead:

$ bd info

Beads Database Information
===========================
Database: /home/omri/Documents/work/_SelfEmployed/customer-docs/leap/git/po-tracker/.beads/dolt
Mode: direct

Issue Count: 4

$ bd list
○ pot-t1r ● P2 Test task

--------------------------------------------------------------------------------
Total: 1 issues (1 open, 0 in progress)

Status: ○ open  ◐ in_progress  ● blocked  ✓ closed  ❄ deferred

I ran beads-web-linux-x64 and create a workspace in the UI pointing to my project folder (/home/omri/Documents/work/_SelfEmployed/customer-docs/leap/git/po-tracker)

UI shows an empty project. no beads

[weselow]

@omri Thanks for the report — found and fixed the bug.

Root cause

beads-web reads beads in three steps:

1. Connects to Dolt SQL server (port 3307) — you don't run one, that's normal
2. Runs bd list --json — fails here
3. Reads .beads/issues.jsonl — file doesn't exist in direct mode

Step 2 fails because the server can't find bd. Your terminal has ~/.cargo/bin in PATH. The server process does not.

Fix

The server now searches for bd automatically:

• ~/.cargo/bin/bd
• ~/.local/bin/bd
• /usr/local/bin/bd
• ~/.beads/bin/bd

At startup it prints the result: bd CLI found: /path/to/bd or a warning if nothing found.

Test build

Download: https://github.com/weselow/beads-web/releases/tag/v0.6.1-rc1

chmod +x beads-web-linux-x64
./beads-web-linux-x64

Check the first lines of output. If bd is found — beads should load. If not — tell me where bd is installed (which bd), and I'll add that path.

Please let me know if this fixes the issue for you!

[ospector]

@Weslow - Thank you for the fast response! Unfortunately this does not fix the issue - still no beads displayed. Here is the console output: $ beads-web-linux-x64 2026-03-10T16:21:32.075727Z INFO beads_server: Database initialized 2026-03-10T16:21:32.076150Z INFO beads_server: Dolt server not detected — will use bd CLI / JSONL fallback 2026-03-10T16:21:32.078796Z INFO beads_server::routes: Found bd CLI in PATH: /home/omri/.nvm/versions/node/v22.17.1/bin/bd 2026-03-10T16:21:32.078830Z INFO beads_server: bd CLI found: /home/omri/.nvm/versions/node/v22.17.1/bin/bd 2026-03-10T16:21:32.079660Z INFO beads_server: Server starting on http://localhost:3008 2026-03-10T16:21:34.671803Z INFO beads_server::routes::watch: Starting file watcher for: "/home/omri/Documents/work/_SelfEmployed/customer-docs/leap/git/po-tracker/.beads/issues.jsonl" 2026-03-10T16:21:34.672391Z INFO beads_server::routes::watch: File watcher active on: "/home/omri/Documents/work/_SelfEmployed/customer-docs/leap/git/po-tracker/.beads" 2026-03-10T16:23:36.749587Z INFO beads_server::routes::watch: Starting file watcher for: "/home/omri/Documents/work/_SelfEmployed/customer-docs/leap/git/po-tracker/.beads/issues.jsonl" 2026-03-10T16:23:36.750105Z INFO beads_server::routes::watch: File watcher active on: "/home/omri/Documents/work/_SelfEmployed/customer-docs/leap/git/po-tracker/.beads"

…

On Tue, Mar 10, 2026 at 6:06 PM weselow ***@***.***> wrote: *weselow* left a comment (AvivK5498/The-Claude-Protocol#7) <#7 (comment)> @omri <https://github.com/omri> Thanks for the detailed report! I was able to reproduce and identify the root cause. *What's happening:* beads-web reads beads through a 3-tier fallback: 1. *Dolt SQL server* (MySQL connection on port 3307) — you don't have one running, which is fine 2. *bd CLI* (bd list --json) — this is where it breaks 3. *JSONL file* (.beads/issues.jsonl) — doesn't exist in your setup because you use Dolt direct mode The problem: when beads-web runs bd list --json, it uses the system PATH of the *server process*, which may not include the directory where bd is installed (e.g. ~/.cargo/bin/). So bd works in your terminal but not from the server. *The fix (v0.6.1-rc1):* The server now auto-discovers bd by searching common install locations: - ~/.cargo/bin/bd - ~/.local/bin/bd - /usr/local/bin/bd - ~/.beads/bin/bd It also logs a clear warning at startup if bd is not found. *Test build:* Download the Linux binary from the pre-release: https://github.com/weselow/beads-web/releases/tag/v0.6.1-rc1 chmod +x beads-web-linux-x64 ./beads-web-linux-x64 Check the terminal output — you should see either: - bd CLI found: /home/omri/.cargo/bin/bd (or wherever it is) - ⚠ bd CLI not found — means we need to add another search path Let me know if this fixes it! — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJIMZFFHKSKFBTYFAJ6AIL4QA4QVAVCNFSM6AAAAACWKTTWPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMZSGY2DKMZWGM> . You are receiving this because you commented.Message ID: ***@***.***>

[Inrego]

Could you please move this bug and debugging to a separate issue, so we don't all get an email for every comment?

[weselow]

@omri bd is found, but bd list --json fails silently. I pushed a fix — errors now show in the console.

New test build (rc2): https://github.com/weselow/beads-web/releases/tag/v0.6.1-rc2

Run it and share the console output. Look for WARN lines — they will show the exact error.

Tracking in weselow/beads-web#1. Please report results there so we don't spam this thread.

[ospector]

@weselow here is the output: $ bd list --json ○ pot-d1r ● P2 Test: Fix: numeric validation in offer fields ○ pot-egr ● P2 Fix: numeric validation in offer fields ? pot-xe9 ● P2 Develop: Fix: numeric validation in offer fields

…

-------------------------------------------------------------------------------- Total: 3 issues (2 open, 0 in progress) Status: ○ open ◐ in_progress ● blocked ✓ closed ❄ deferred I suggest you move this conversation to a new issue in your repo (and tag me, of course) so that we do not bother the people in this repo. Thanks.

On Tue, Mar 10, 2026 at 6:47 PM weselow ***@***.***> wrote: *weselow* left a comment (AvivK5498/The-Claude-Protocol#7) <#7 (comment)> @omri <https://github.com/omri> Good news: bd is found ( /home/omri/.nvm/versions/node/v22.17.1/bin/bd). The auto-discovery works. Bad news: bd list --json fails silently. The error was logged at debug level — invisible in the default config. I pushed a fix: - Errors now print at warn level — you'll see the exact reason in the console - Also fixed a logic bug that could skip the CLI fallback entirely Building a new test binary now. Will update this comment with the download link in ~7 minutes. In the meantime, could you check what bd list --json outputs in your terminal? cd /home/omri/Documents/work/_SelfEmployed/customer-docs/leap/git/po-tracker bd list --json This will help narrow down whether the issue is in the JSON format or something else. — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJIMZF5M2TUWX4HSS6OGVD4QBBJ3AVCNFSM6AAAAACWKTTWPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMZSHEYDSNBTGA> . You are receiving this because you commented.Message ID: ***@***.***>