* security: pin build toolchain to go1.26.7 go1.26.5 carries 8 stdlib advisories, 7 of them reachable from the shipped bd binary. Verified with govulncheck in call-graph mode against ./cmd/bd, toolchain pinned so the analysis cannot drift: GO-2026-6218 net/url quadratic resolvePath GO-2026-6091 html/template JS-regexp context tracking GO-2026-6090 crypto/tls post-handshake message flood GO-2026-6089 net/http ReadHeaderTimeout on the h2c check GO-2026-6088 encoding/xml recursion depth GO-2026-5972 encoding/asn1 recursion depth GO-2026-5026 net/http vendored x/net/idna punycode GO-2026-5942 net dnsmessage SVCB/HTTPS RR (linked, uncalled) `bd serve` is a real HTTP server and bd makes TLS client connections, so these are live paths rather than dead weight: httpapi.Serve reaches four of them directly. go1.26.6 fixes all eight; 1.26.7 adds one more net/http fix. After the bump the same scan reports zero. The `go` directive stays at 1.26.5 so importers of the module keep their current floor; `toolchain` is what we actually build with. release.yml builds the shipped binaries with a bare `go build` under the default GOTOOLCHAIN=auto, which honors the toolchain line. The Makefile needed the second half of this. It pinned GOTOOLCHAIN from the `go` directive, which is the importer floor, not the build version - left alone it would have held every make target (the test suite, the npm and MCP package gates, local `make build`) at 1.26.5 while the release binaries moved to 1.26.7, which is both a silent downgrade and a split between what CI tests and what we ship. It now reads `toolchain` first and falls back to `go` when there is no toolchain directive, preserving the original reason for pinning: one exact version so the compile tools and coverage instrumentation cannot disagree. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * security: bump x/crypto, x/mod, klauspost/compress, moby/go-archive Four advisories, none reachable from the shipped bd binary; these are hygiene bumps that also clear the Dependabot board. golang.org/x/crypto v0.54.0 -> v0.55.0 GO-2026-6303 golang.org/x/mod v0.37.0 -> v0.40.0 GO-2026-6179/6180 github.com/klauspost/compress v1.18.5 -> v1.18.7 GO-2026-5841 github.com/moby/go-archive v0.2.0 -> v0.3.3 CVE-2026-17106 (#140) Reachability, from `go list -deps ./cmd/bd` plus govulncheck call-graph mode: x/crypto/ssh proper enters only through testcontainers (test-only); the compress advisory is in the s2 codec, which is not linked into bd at all (bd links zstd/gzip/flate/huff0 via dolt); the x/mod sumdb/tlog code is required but never called; go-archive is testcontainers-only and absent from the binary's package graph entirely. go-archive goes to v0.3.3, not the advisory's minimum v0.3.0: v0.3.0's hardened extraction rejected absolute symlinks and hardlinks and broke device nodes and implied directories, all fixed across v0.3.1-v0.3.3. MVS carries x/net, x/text, x/tools and x/telemetry along. No replace directives, and the dolt pin is untouched - dolt requires older versions of all three x/ modules, so beads' go.mod already wins the version selection. The examples/ modules reach the parent through a `replace` directive, so their recorded graph goes stale on any root go.mod change and both failed scripts/build-examples.sh with the documented "updates to go.mod needed". Re-tidied here rather than left for the advisory job to warn about; the diff is purely the mirror of the bumps above. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * security: bump oapi-codegen to v2.7.1 and kin-openapi to v0.144.0 Clears the board's one critical (#133, GHSA-r277-6w6q-xmqw, CVSS 9.1) plus #142, #141, #134 and the low #132. All five are codegen-tool-only: kin-openapi reaches the module graph solely through the go.mod `tool` directive for oapi-codegen, no beads source file imports kin-openapi, oapi-codegen or openapi3filter, and `go list -deps ./cmd/bd` contains none of them. The critical is a fail-open bug in openapi3filter's ValidationHandler.Load(), middleware this repo never runs - request validation in internal/httpapi is hand-rolled. Dependabot scopes the alert "runtime" because it cannot model Go tool-directive semantics. Both must move together: oapi-codegen v2.6.0 does not compile against kin-openapi v0.144.0 (pkg/codegen/schema.go:909, openapi3.MappingRef vs string). v2.7.1 is the minimum-fix pair, chosen over the latest 2.8.0/0.149.0 to keep codegen churn off a release branch. The `make api-gen` regen diff is two lines of real change: the generated BearerTokenScopes constant picks up a generated named context-key type instead of being an untyped string. The identifier has no references outside types.gen.go. `make api-check` is green - regeneration is idempotent, pinning.go's compile-time welds hold, and TestWireTagBijection passes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * security: refresh beads-mcp uv.lock (clears all 19 pip alerts) `uv lock --upgrade` with fastmcp still pinned ==3.4.5. Every one of the 19 Dependabot alerts on integrations/beads-mcp/uv.lock is a fastmcp transitive, and each lands at or above its first-patched version: mcp 1.25.0 -> 1.29.1 #129 #128 #127 (high) cryptography 48.0.0 -> 50.0.1 #137 #138 #82 #139 pyjwt 2.12.1 -> 2.13.0 #79 #136 #81 #78 #135 joserfc 1.6.5 -> 1.7.4 #113 #109 python-multipart 0.0.27 -> 0.0.32 #88 #87 #86 #85 idna 3.11 -> 3.19 #68 Real exposure was already low: beads-mcp runs stdio transport only (server.py's mcp.run_async(transport="stdio")), so the three high mcp-SDK alerts - WebSocket Host/Origin validation, HTTP session principal handling, task-handler cross-access - are all HTTP/WS-transport bugs this server never reaches, and the auth libraries ride along with fastmcp's extras rather than being used by beads-mcp's own code. The lock governs dev and CI installs; PyPI users resolve fresh and already get patched versions. mcp 1.25 -> 1.29 is the only behaviorally interesting jump. The full package gate is green: uv sync --locked, ruff, mypy, 228 passed / 5 skipped, uv build. The resolved lock is byte-identical under uv 0.9.5 and CI's uv 0.11.16. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * chore(nix): update vendorHash for go.sum changes The go.mod/go.sum bumps in this branch invalidate the proxyVendor fixed-output hash in default.nix, which fails the nix-build gate. The workflow that repairs this automatically only fires for dependabot PRs targeting main, so it does not cover this branch. Recomputed with scripts/update-nix-vendorhash.sh's flow and verified: `nix build .#default` completes green, which also confirms the new `toolchain go1.26.7` directive is compatible with default.nix's GOTOOLCHAIN = "local". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bash-agent | ||
| bd-example-extension-go | ||
| claude-desktop-mcp | ||
| compaction | ||
| contributor-workflow | ||
| formulas | ||
| library-usage | ||
| linear-workflow | ||
| multi-phase-development | ||
| multiple-personas | ||
| protected-branch | ||
| python-agent | ||
| startup-hooks | ||
| team-workflow | ||
| README.md | ||
Beads Examples
This directory contains examples of how to integrate bd with AI agents and workflows.
Examples
Agent Integration
- python-agent/ - Simple Python agent that discovers ready work and completes tasks
- bash-agent/ - Bash script showing the full agent workflow
- startup-hooks/ - Session startup scripts for automatic bd upgrade detection
- claude-desktop-mcp/ - MCP server for Claude Desktop integration
Tools & Utilities
- monitor-webui/ - Standalone web interface for real-time issue monitoring and visualization
- git-hooks/ - Pre-configured git hooks for automatic Dolt sync
Workflow Patterns
- contributor-workflow/ - OSS contributor setup with separate planning repo
- team-workflow/ - Team collaboration with shared repositories
- multi-phase-development/ - Organize large projects by phases (planning, MVP, iteration, polish)
- multiple-personas/ - Architect/implementer/reviewer role separation
- protected-branch/ - Protected branch workflow for team collaboration
Quick Start
# Try the Python agent example
cd python-agent
python agent.py
# Try the bash agent example
cd bash-agent
./agent.sh
# Install git hooks
cd git-hooks
./install.sh
# REMOVED (bd-4c74): branch-merge demo - hash IDs eliminate collision resolution
Creating Your Own Agent
The basic agent workflow:
- Find ready work:
bd ready --json --limit 1 - Claim the task:
bd update <id> --claim --json - Do the work: Execute the task
- Discover new issues:
bd create "Found bug" --json - Link discoveries:
bd dep add <new-id> <parent-id> --type discovered-from - Complete the task:
bd close <id> --reason "Done" --json
All commands support --json for easy parsing.