Skip to content

Beadhive changelog

io.github.beadhive/beadhive

32 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • server.json 1 field changed
    version
    0.35.11 0.37.1

  • server.json 1 field changed
    version
    0.35.9 0.35.11
  • server.json 1 field changed
    version
    0.35.8 0.35.9

  • server.json 1 field changed
    version
    0.35.7 0.35.8
  • server.json 1 field changed
    version
    0.35.6 0.35.7
  • server.json 1 field changed
    version
    0.35.4 0.35.6

  • server.json 1 field changed
    version
    0.35.3 0.35.4

  • server.json 1 field changed
    version
    0.35.2 0.35.3
  • llms.txt +15 −4

    https://beadhive.ai/llms.txt

    − CLI; there is no server to run.− - [Frames](https://beadhive.ai/frame-model/): A current-state and proposal-aware map of Beadhive roles, dispatcher loops, Bead Frame provisioning, and deployment topologies.− - [The ladder](https://beadhive.ai/data/): Agents can't plan against data they can't query. The commitment ladder: sync the tracker, move the docs, record the reviews, hook the telemetry — each rung pays off on its own, and retiring the old tools is a conclusion you reach, not a demand we make.− - [Configuration reference](https://github.com/beadhive/beadhive/blob/main/docs/CONFIGURATION.md)+ CLI; there is no server you have to run.+ - [Frames](https://beadhive.ai/frame-model/): A current-state and proposal-aware map of Beadhive host roles, dispatcher loops, HQ modes, leases and failover, Bead Frame provisioning, and deployment topologies.+ - [The ladder](https://beadhive.ai/data/): Agents can't plan against data they can't query. The commitment ladder: pull the tracker, move the docs, record the reviews, hook the telemetry — each rung pays off on its own, and retiring the old tools is a conclusion you reach, not a demand we make. Plus what keeps the graph honest and recoverable: backfill behind a preview-first safety envelope, the BeadLog history archive, the opt-in XTDB store, and backups proven by restoring them.+ - [Intake](https://beadhive.ai/intake/): How a GitHub issue becomes a held report in a hive, is triaged with the ordinary verbs, tracks the work that addresses it, and is kept informed through a supervised outbox — every stage opt-in, nothing posted to GitHub without an operator approving the exact text, and no LLM call made by bh.+ - [Configuration reference, including the plugin switches and install extras](https://github.com/beadhive/beadhive/blob/main/docs/CONFIGURATION.md)+ - [Upgrading: what each release turns on (nothing, until a switch is set)](https://github.com/beadhive/beadhive/blob/main/docs/UPGRADING.md)+ - [HQ: the authoritative fleet store, authority modes, placement and failover](https://github.com/beadhive/beadhive/blob/main/docs/HQ.md)+ - [Frames: fleet membership, HQ modes, lifecycle and eligibility](https://github.com/beadhive/beadhive/blob/main/docs/FRAME-FLEET-MEMBERSHIP.md)+ - [Where bead data lives: two stores per repository](https://github.com/beadhive/beadhive/blob/main/docs/TWO-STORES.md)+ - [Decision: HQ declares a Dolt remote, the host authenticates](https://github.com/beadhive/beadhive/blob/main/docs/design/hq-dolt-remote-descriptor-adr.md)+ - [External intake: GitHub issues and the supervised triage loop](https://github.com/beadhive/beadhive/blob/main/docs/design/external-intake-module-adr.md)+ - [Intake templates and the information-sufficiency checklist](https://github.com/beadhive/beadhive/blob/main/docs/INTAKE-TEMPLATES.md)+ - [Backfill: passes, plans and the safety envelope](https://github.com/beadhive/beadhive/blob/main/docs/BACKFILL.md)+ - [The opt-in XTDB BeadLog store](https://github.com/beadhive/beadhive/blob/main/docs/XTDB-STORE.md)+ - [Worktrees: admission, automatic reclaim and the live-count cap](https://github.com/beadhive/beadhive/blob/main/docs/WORKTREES.md)
  • server.json 1 field changed
    version
    0.35.0 0.35.2

  • server.json 1 field changed
    version
    0.34.0 0.35.0

  • server.json 1 field changed
    version
    0.31.0 0.34.0

  • server.json 1 field changed
    version
    0.30.0 0.31.0

  • server.json 1 field changed
    version
    0.29.5 0.30.0
  • server.json 1 field changed
    version
    0.29.4 0.29.5

  • server.json 1 field changed
    version
    0.29.3 0.29.4
  • server.json 1 field changed
    version
    0.29.2 0.29.3

  • server.json 1 field changed
    version
    0.29.0 0.29.2
  • server.json 1 field changed
    version
    0.28.4 0.29.0

  • server.json 1 field changed
    version
    0.28.3 0.28.4

  • server.json 1 field changed
    version
    0.28.1 0.28.3
  • server.json 1 field changed
    version
    0.28.0 0.28.1
  • server.json 1 field changed
    version
    0.27.0 0.28.0

  • server.json 1 field changed
    version
    0.26.0 0.27.0

  • server.json 1 field changed
    version
    0.25.4 0.26.0

  • server.json 1 field changed
    version
    0.25.3 0.25.4
  • server.json 1 field changed
    version
    0.25.2 0.25.3

  • server.json 1 field changed
    version
    0.25.1 0.25.2

  • server.json 1 field changed
    version
    0.25.0 0.25.1
  • server.json 1 field changed
    version
    0.24.4 0.25.0

  • server.json 1 field changed
    version
    0.24.2 0.24.4

  • server.json 1 field changed
    version
    0.24.1 0.24.2