opencode-beads 0.2.1 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-beads",
3
- "version": "0.2.1",
3
+ "version": "0.3.0",
4
4
  "type": "module",
5
5
  "description": "A plugin for OpenCode that provides integration with the beads issue tracker.",
6
6
  "author": "Josh Thomas <josh@joshthomas.dev>",
@@ -0,0 +1,28 @@
1
+ ---
2
+ description: Log and label agent interactions (append-only JSONL)
3
+ argument-hint: record|label
4
+ ---
5
+
6
+ Append-only audit logging for agent interactions (prompts, responses, tool calls) in `.beads/interactions.jsonl`.
7
+
8
+ Each line is one event. Labeling is done by appending a new `"label"` event referencing a previous entry.
9
+
10
+ ## Usage
11
+
12
+ - **Record an interaction**:
13
+ - `bd audit record --kind llm_call --model "claude-3-5-haiku" --prompt "..." --response "..."`
14
+ - `bd audit record --kind tool_call --tool-name "go test" --exit-code 1 --error "..." --issue-id bd-42`
15
+
16
+ - **Pipe JSON via stdin**:
17
+ - `cat event.json | bd audit record`
18
+
19
+ - **Label an entry**:
20
+ - `bd audit label int-a1b2 --label good --reason "Worked perfectly"`
21
+ - `bd audit label int-a1b2 --label bad --reason "Hallucinated a file path"`
22
+
23
+ ## Notes
24
+
25
+ - Audit entries are **append-only** (no in-place edits).
26
+ - `bd sync` includes `.beads/interactions.jsonl` in the commit allowlist (like `issues.jsonl`).
27
+
28
+
@@ -13,5 +13,5 @@ Use the beads MCP `stats` tool to retrieve project metrics and present them clea
13
13
 
14
14
  Optionally suggest actions based on the stats:
15
15
  - High number of blocked issues? Run `/bd-blocked` to investigate
16
- - No in-progress work? Run `/bd-ready` to find tasks
16
+ - No in_progress work? Run `/bd-ready` to find tasks
17
17
  - Many open issues? Consider prioritizing with `/bd-update`