opencode-beads 0.5.2 → 0.5.4

package/README.md

@@ -2,6 +2,13 @@
 
 [Beads](https://github.com/steveyegge/beads) issue tracker integration for [OpenCode](https://opencode.ai).
 
+> [!NOTE]
+> This plugin is intentionally small in scope. The [beads](https://github.com/steveyegge/beads) project is moving quickly and is a moving target — any additional layers on top of it add churn.
+>
+> To minimize maintenance, this plugin defers to beads and limits its scope to bug fixes and syncing upstream vendor plugin content. Feature requests and additional customization are generally out of scope.
+>
+> If you want to customize behavior, the plugin surface area is small — forking or copying it locally is encouraged.
+
 ## Installation
 
 Install the beads CLI:
@@ -26,7 +33,7 @@ Optionally, pin to a specific version for stability:
 
 ```json
 {
-  "plugin": ["opencode-beads@0.5.2"]
+  "plugin": ["opencode-beads@0.5.4"]
 }
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-beads",
-  "version": "0.5.2",
+  "version": "0.5.4",
   "type": "module",
   "description": "A plugin for OpenCode that provides integration with the beads issue tracker.",
   "author": "Josh Thomas <josh@joshthomas.dev>",

package/vendor/agents/task-agent.md

@@ -39,7 +39,7 @@ You are a task-completion agent for beads. Your goal is to find ready work and c
 
 # Important Guidelines
 
-- Always update issue status (`in_progress` when starting, close when done)
+- Always claim before working (MCP: set status to `in_progress`; CLI: `--claim` for atomic assignee + status) and close when done
 - Link discovered work with `discovered-from` dependencies
 - Don't close issues unless work is actually complete
 - If blocked, use `update` to set status to `blocked` and explain why

package/vendor/commands/dep.md

@@ -71,7 +71,7 @@ The diagram colors are determined by your Mermaid theme (default, dark, forest,
 
 ## Examples
 
-- `bd dep add bd-10 bd-20 --type blocks`: bd-10 blocks bd-20
+- `bd dep add bd-10 bd-20 --type blocks`: bd-10 depends on bd-20 (bd-20 blocks bd-10)
 - `bd dep tree bd-20`: Show what blocks bd-20 (dependency tree going UP)
 - `bd dep tree bd-1 --reverse`: Show what was discovered from bd-1 (dependent tree going DOWN)
 - `bd dep tree bd-1 --reverse --max-depth 3`: Show discovery tree with depth limit

package/vendor/commands/epic.md

@@ -19,7 +19,8 @@ Manage epics (large features composed of multiple issues).
 ## Epic Workflow
 
 1. Create epic: `bd create "Large Feature" -t epic -p 1`
-2. Link subtasks: `bd dep add bd-10 bd-20 --type parent-child` (epic bd-10 is parent of task bd-20)
+2. Link subtasks: `bd dep add bd-20 bd-10 --type parent-child` (task bd-20 is child of epic bd-10)
+   - Or at creation: `bd create "Subtask title" -t task --parent bd-10`
 3. Track progress: `bd epic status`
 4. Auto-close when done: `bd epic close-eligible`
 

package/vendor/commands/export.md

@@ -15,7 +15,7 @@ Issues are sorted by ID for consistent diffs, making git diffs readable.
 
 ## Automatic Export
 
-The daemon automatically exports to `.beads/issues.jsonl` after any CRUD operation (5-second debounce). Manual export is rarely needed unless you need a custom output location or filtered export.
+The Dolt server automatically exports to `.beads/issues.jsonl` after any CRUD operation (5-second debounce). Manual export is rarely needed unless you need a custom output location or filtered export.
 
 Export is used for:
 - Git version control

package/vendor/commands/import.md

@@ -28,7 +28,7 @@ bd import -i issues.jsonl --dry-run
 
 ## Automatic Import
 
-The daemon automatically imports from `.beads/issues.jsonl` when it's newer than the database (e.g., after `git pull`). Manual import is rarely needed.
+The Dolt server automatically imports from `.beads/issues.jsonl` when it's newer than the database (e.g., after `git pull`). Manual import is rarely needed.
 
 ## Options
 

package/vendor/commands/sync.md

@@ -51,4 +51,4 @@ The merge command includes safety checks:
 
 ## Note
 
-Most users should rely on the daemon's automatic sync (`bd daemon --auto-commit --auto-push`) instead of running manual sync. This command is useful for one-off syncs or when not using the daemon.
+Most users should rely on the Dolt server's automatic sync (with `dolt.auto-commit` enabled) instead of running manual sync. This command is useful for one-off syncs or when not using the Dolt server.

package/vendor/commands/update.md

@@ -19,6 +19,6 @@ Use the beads MCP `update` tool to apply the changes. Show the updated issue to
 **Note:** Comments are managed separately with `bd comments add`. The `update` command is for singular, versioned properties (title, status, priority, etc.), while comments form a discussion thread that's appended to, not updated.
 
 Common workflows:
-- Start work: Update status to `in_progress`
+- Start work: `bd update <id> --claim` (atomic claim + `in_progress`)
 - Mark blocked: Update status to `blocked`
 - Reprioritize: Update priority (0-4)

package/vendor/commands/workflow.md

@@ -12,8 +12,8 @@ Beads is an issue tracker designed for AI-supervised coding workflows. Here's ho
 Use `/beads:ready` or the `ready` MCP tool to see tasks with no blockers.
 
 ## 2. Claim Your Task
-Update the issue status to `in_progress`:
-- Via command: `/beads:update <id> in_progress`
+Claim the issue atomically (assignee + `in_progress` in one step):
+- Via command: `/beads:update <id> --claim`
 - Via MCP tool: `update` with `status: "in_progress"`
 
 ## 3. Work on It