Skip to content

Doc Bridge v1.2.6 — deterministic handoffs for Claude Desktop

Choose a tag to compare

@github-actions github-actions released this 31 Jul 23:52
· 7 commits to master since this release
c5548ff

Agents should not have to guess which package they may edit, where the relevant documentation lives, or which checks prove a change is safe.

Doc Bridge turns repository docs, ownership metadata, and human documentation into deterministic handoffs that work from the CLI, MCP, and CI. Its core runs locally without an LLM, API key, hosted service, or model-provider dependency.

What ships in 1.2.6

  • Claude Desktop MCP Bundle: the release includes doc-bridge-1.2.6.mcpb, exposing eight read-only tools behind an explicit project configuration boundary.
  • Executable repository handoffs: agents receive startHere, allowed editRoots, required checks, and the matching human documentation instead of guessing.
  • Secure release recovery: dependency overrides now work with pnpm 11, with patched Next.js, Sharp, and brace-expansion versions. The release gate completed with no known vulnerabilities.
  • Two installation paths: use the npm package for CLI, CI, and custom MCP clients, or the MCPB artifact for the Claude Desktop connector workflow.

Try the deterministic path

npm i -D @agentskit/doc-bridge@1.2.6
npx ak-docs demo --text

Then configure a repository:

npx ak-docs init
npx ak-docs index
npx ak-docs query package example --agent

The packaged bundle currently declares macOS compatibility. Its manifest, privacy boundary, archive inventory, and all eight read-only tools passed automated validation; installation verification inside Claude Desktop remains the next distribution gate.

Artifact integrity

  • doc-bridge-1.2.6.mcpb — SHA-256 9136d4a487b44f0a56731fac89d880525ad5e216d376940dff949477cd741905
  • npm provenance — SLSA attestation

Documentation: doc-bridge.agentskit.io
Implementation: PR #69
Full changelog: v1.2.5...v1.2.6

If your repository has a workflow Doc Bridge cannot express yet, open an issue with the handoff you expected. That feedback directly shapes the next contracts and adapters.