v0.5.2

What's New

Dolt Server Lifecycle

• beehive now starts a persistent beads server (bd dolt start) at launch — eliminates per-command server start/stop churn (238 cycles → 1)
• Tmux session-closed hook automatically stops the server when the session ends
• New beehive --stop flag for manual server shutdown

Bee Autonomy

• Bees no longer wait for user direction — they check their assignments and start working immediately
• If a bee has multiple assignments, it picks the highest priority item (no more asking the user to choose)
• New Session Start section in bee skill with imperative workflow

Queen Assignment Discipline

• One active assignment per bee — queen must not pre-load a bee's queue
• Explicit workflow: check bee's current load before assigning more work

Beekeeper Vocabulary

• Both skills now define unambiguous responses to common phrases:
  • "Update your plan" → update plan file + bead comment
  • "Create a plan" → run /deep-plan
  • "What's your plan?" → summarize approach (don't create a file)

Plan Context Flow

• Bees working on child tasks now read the parent plan file for full context
• Progress updates always sync both the bead and the plan file
• Explicit anti-pattern: do not use Claude Code plan mode for Beehive planning

Bug Fixes

• Dolt server port instability after laptop crash/restart (stale pid → per-command churn)

v0.5.1

Summary

• tighten Beehive-native planning docs to keep planning out of Claude Code plan mode
• require plan↔beads linkage via PLAN-META.id and Plan file: plans/<slug>.md
• improve status output with per-status issue counts and bump version to 0.5.1

Test plan

• repo-local doc audit for planning workflow guidance
• verified version bumped to 0.5.1
• pushed main and tag v0.5.1

🤖 Generated with Claude Code

v0.5.0

Summary

• migrate Beehive coordination from ad hoc markdown tracking to Beads (bd)
• move task state into a structured, dependency-aware tracker instead of fragile shared files
• establish the coordination model that later Beehive releases continue to refine

Why this change happened

The markdown-based workflow was too fragile for multi-agent coordination:

• plan/task state lived in editable files rather than a purpose-built tracker
• claiming and updating work was prone to drift and write conflicts
• dependencies and discovery relationships were hard to represent cleanly
• too much coordination context accumulated in free-form docs instead of structured state

Beads solves those problems by giving Beehive:

• atomic claims for concurrent agents
• explicit issue state and dependency tracking
• a durable audit trail for coordination changes
• a cleaner split between structured work state in Beads and spec/detail in markdown plans

What changed in the v0.5.0 release line

• Beehive adopted bd as the coordination backend
• task/epic/bug state moved into the .beads/ database
• agent workflows shifted toward bd ready, bd update --claim, bd close, and dependency linking
• scaffolding, prompts, and coordination docs were updated around the new model
• release-line follow-up fixes tightened validation, environment scoping, and workflow details

Migration impact

For users, the important shift was:

• before: coordination centered on markdown tracking files
• after: coordination centered on Beads issues, with markdown reserved for plan/spec content

That change was intended to make Beehive more reliable under real multi-agent use, especially when several agents are discovering, claiming, and completing work concurrently.

Historical note

• this GitHub release is published retrospectively
• the historical git tag v0.5.0 points to commit 3e1e06f
• additional commits in the same release line further clarified and stabilized the migration

🤖 Generated with Claude Code

v0.2.1 - Enhanced File Structure & Symlink Fix

Bug Fixes

• Fixed symlink installation (#2 by @ChristopherJHart)
  • beehive --init now works when installed via symlink
  • Resolves issue where SCRIPT_DIR pointed to symlink location instead of actual script
  • Fixes documented installation method: sudo ln -sf ~/beehive/beehive /usr/local/bin/beehive

Enhancements

File Organization

• Introduced plans/_meta/ directory to separate coordination files from plan files
  • plans/TRACKER.md → plans/_meta/TRACKER.md
  • Added plans/_meta/SESSION_LOG.md for session notes
  • Added plans/_meta/DEPENDENCIES.md for dependency tracking

Queen Maintenance

Enhanced /buzz command with automatic cleanup:

• Caps completed plans table at 20 rows
• Trims session log to last 7 days
• Regenerates dependency graph from plan files

Documentation

• Updated all file path references
• Enhanced README with workflow diagrams
• Updated CLAUDE.md development guide

Migration from v0.2.0

```bash
cd ~/myproject
beehive --init

If you have existing plan data, move it:

mv plans/TRACKER.md plans/_meta/TRACKER.md
```

The `--init` command is safe to run on existing installations. It creates the new `plans/_meta/` structure. If you have an old `TRACKER.md` with data, the move command overwrites the empty template.

Installation

```bash
git clone https://github.com/mahowlin/beehive.git ~/beehive
sudo ln -sf ~/beehive/beehive /usr/local/bin/beehive
cd ~/myproject
beehive --init
beehive
```