opencodekit 0.14.0 → 0.14.1

package/dist/template/.opencode/command/new-feature.md

@@ -142,10 +142,34 @@ Key risks identified:
 - [Risk 1]: Mitigation: [...]
 - [Risk 2]: Mitigation: [...]
 
-Proceed with spec? (yes/modify/explore-more)
 ```
 
-**STOP and wait for approval** before proceeding.
+**STOP. Use question tool to get user approval:**
+
+```typescript
+question({
+  questions: [
+    {
+      header: "Approve",
+      question:
+        "Should I proceed with creating the specification for $ARGUMENTS?",
+      options: [
+        {
+          label: "Yes, proceed",
+          description: "Approach looks good, create spec",
+        },
+        {
+          label: "Modify approach",
+          description: "Need changes to brainstorming",
+        },
+        { label: "Explore more", description: "Need more research first" },
+      ],
+    },
+  ],
+});
+```
+
+**Wait for user's answer before proceeding to spec creation.**
 
 ---
 
@@ -398,8 +422,17 @@ skill({ name: "using-git-worktrees" });
 # Ensure .gitignore has worktree directory
 grep -q "^\.worktrees/$" .gitignore || echo ".worktrees/" >> .gitignore
 
-# Create worktree for the epic
-git worktree add .worktrees/[epic-id] -b feature/[feature-name]
+# Get current branch (parent branch)
+PARENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
+
+# Create readable branch name from feature name
+FEATURE_SLUG=$(echo "[feature-name]" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | cut -c1-40)
+
+# Create branch: <parent>/feat/<epic-id>-<description>
+BRANCH_NAME="${PARENT_BRANCH}/feat/[epic-id]-${FEATURE_SLUG}"
+
+# Create worktree for the epic with readable branch
+git worktree add ".worktrees/[epic-id]" -b "$BRANCH_NAME"
 
 # Setup in worktree
 cd .worktrees/[epic-id]

package/dist/template/.opencode/command/plan.md

@@ -186,7 +186,25 @@ Decomposition: [Single bead | X tasks | X tasks with subtasks]
 
 Save to `.beads/artifacts/$ARGUMENTS/design.md`.
 
-**STOP. Wait for user to pick an option.**
+**STOP. Use question tool to ask user to pick an option:**
+
+```typescript
+question({
+  questions: [
+    {
+      header: "Design",
+      question: "Which implementation approach should I use for $ARGUMENTS?",
+      options: [
+        { label: "Option A (Recommended)", description: "[Option A summary]" },
+        { label: "Option B", description: "[Option B summary]" },
+        { label: "Option C", description: "[Option C summary]" },
+      ],
+    },
+  ],
+});
+```
+
+Wait for user's answer before proceeding.
 
 ---
 

package/dist/template/.opencode/command/pr.md

@@ -120,23 +120,33 @@ git log origin/$(git branch --show-current)..HEAD --oneline 2>/dev/null || git l
 git diff --stat origin/$(git branch --show-current)..HEAD 2>/dev/null || git diff --stat HEAD~3..HEAD
 ```
 
-**Present to user:**
+**Use question tool to get push/PR decision:**
 
+```typescript
+question({
+  questions: [
+    {
+      header: "Push",
+      question: "Ready to push and create PR for $ARGUMENTS. What should I do?",
+      options: [
+        {
+          label: "Push & create PR (Recommended)",
+          description: "Push branch and create PR",
+        },
+        { label: "Push & draft PR", description: "Create as draft for review" },
+        {
+          label: "Show diff first",
+          description: "Review changes before pushing",
+        },
+        {
+          label: "Skip (I'll push manually)",
+          description: "Handle PR creation manually",
+        },
+      ],
+    },
+  ],
+});
 ```
-Ready to Push & Create PR
-━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Branch: [current branch]
-Commits: [N commits ahead of origin]
-
-Would you like me to:
-1. Push and create PR
-2. Push and create draft PR
-3. Show full diff first
-4. Skip (I'll push manually)
-```
-
-**Wait for user confirmation before proceeding.**
 
 If user confirms, push:
 

package/dist/template/.opencode/command/revert-feature.md

@@ -99,7 +99,7 @@ Before reverting, check what depends on this:
 
 ### Downstream Report
 
-```
+````
 Downstream Impact Analysis
 ━━━━━━━━━━━━━━━━━━━━━━━━━━
 
@@ -119,8 +119,20 @@ Feature flags:
 - AUTH_ENABLED flag in production
 
 CAUTION: Reverting may break dependent features.
-Proceed? (yes/abort/revert-cascade)
-```
+
+```typescript
+question({
+  questions: [{
+    header: "Confirm",
+    question: "Ready to revert $ARGUMENTS? Breaking changes detected.",
+    options: [
+      { label: "Proceed with revert", description: "Execute revert with backups" },
+      { label: "Abort", description: "Cancel this operation" },
+      { label: "Revert cascade", description: "Revert dependent features too" }
+    ]
+  }]
+});
+````
 
 ---
 

package/dist/template/.opencode/command/skill-optimize.md

@@ -150,7 +150,37 @@ Rules:
 
 ### Clarification Techniques
 
-```
+````
+BEFORE (vague):
+──────────────
+"Check that the configuration is correct."
+
+AFTER (specific):
+────────────────
+"Verify config:
+1. Run: `npm run config:check`
+2. Confirm output shows: 'Configuration valid'
+3. If errors, check [specific file] for [specific issue]"
+
+Rules:
+- Replace "check" with specific verification command
+- Include expected output
+- Add troubleshooting for failures
+
+Use question tool to confirm:
+```typescript
+question({
+  questions: [{
+    header: "Verify",
+    question: "Configuration verified. Ready to continue?",
+    options: [
+      { label: "Yes, continue", description: "Proceed with optimization" },
+      { label: "No, fix issues", description: "Address validation errors first" }
+    ]
+  }]
+});
+````
+
 BEFORE (vague):
 ───────────────
 "Check that the configuration is correct."
@@ -158,19 +188,23 @@ BEFORE (vague):
 AFTER (specific):
 ─────────────────
 "Verify config:
+
 1. Run: `npm run config:check`
 2. Confirm output shows: 'Configuration valid'
 3. If errors, check [specific file] for [specific issue]"
 
 Rules:
+
 - Replace "check" with specific verification command
 - Include expected output
 - Add troubleshooting for failures
+
 ```
 
 ### Hardening Techniques
 
 ```
+
 BEFORE (soft):
 ──────────────
 "You should generally avoid committing directly to main."
@@ -180,20 +214,24 @@ AFTER (hardened):
 "NEVER commit directly to main. ALWAYS use feature branches.
 
 If tempted to commit to main because 'it's just a small fix':
+
 - STOP
 - Create branch anyway: git checkout -b fix/small-fix
 - This is NOT optional"
 
 Rules:
+
 - Add MUST/NEVER to critical rules
 - Anticipate rationalizations
 - Explicitly reject common excuses
 - Name the anti-pattern
+
 ```
 
 ### Expansion Techniques
 
 ```
+
 BEFORE (incomplete):
 ────────────────────
 "Handle errors appropriately."
@@ -203,23 +241,28 @@ AFTER (comprehensive):
 "Error Handling:
 
 Network Errors:
+
 - Retry 2x with exponential backoff
 - If still failing, log and surface to user
 
 Validation Errors:
+
 - Display specific field errors
 - Do NOT proceed with invalid data
 
 Permission Errors:
+
 - Log with full context
 - Display user-friendly message
 - Do NOT expose internal details"
 
 Rules:
+
 - List specific error categories
 - Provide handling for each
 - Include what NOT to do
-```
+
+````
 
 ## Phase 5: Test Optimizations
 
@@ -232,9 +275,9 @@ task({
   description: "Test original skill",
   prompt: `
     Load skill: skill({ name: "$ARGUMENTS" })
-    
+
     Scenario: [test scenario]
-    
+
     Follow the skill and report each step.
   `,
 });
@@ -245,13 +288,13 @@ task({
   description: "Test optimized skill",
   prompt: `
     Load skill: skill({ name: "$ARGUMENTS" })
-    
+
     Scenario: [same test scenario]
-    
+
     Follow the skill and report each step.
   `,
 });
-```
+````
 
 ### Compare Results
 
@@ -367,6 +410,27 @@ write({
 skill({ name: "$ARGUMENTS" });
 ```
 
+```typescript
+question({
+  questions: [
+    {
+      header: "Verify",
+      question: "Skill optimized and saved. Ready to deploy?",
+      options: [
+        {
+          label: "Yes, deploy (Recommended)",
+          description: "All verifications passed",
+        },
+        {
+          label: "No, fix issues",
+          description: "Need to address verification failures",
+        },
+      ],
+    },
+  ],
+});
+```
+
 Confirm:
 
 - [ ] Skill loads without error

package/dist/template/.opencode/command/start.md

@@ -75,14 +75,40 @@ bd update $ARGUMENTS --status in_progress
 
 ## Workspace Setup
 
-### Option A: Feature Branch (default)
+### Create Feature Branch
 
-If not already on a feature branch:
+Extract task info and parent branch for a readable branch name:
 
 ```bash
-git checkout -b $ARGUMENTS
+# Get current branch (parent branch)
+PARENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
+
+# Get task title and type from bead
+BEAD_INFO=$(bd show $ARGUMENTS --json 2>/dev/null)
+BEAD_TITLE=$(echo "$BEAD_INFO" | jq -r '.title // ""' | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | cut -c1-40)
+BEAD_TYPE=$(echo "$BEAD_INFO" | jq -r '.type // "task"')
+
+# Map bead type to branch prefix
+case "$BEAD_TYPE" in
+  "bug") PREFIX="fix" ;;
+  "feature"|"epic") PREFIX="feat" ;;
+  "refactor") PREFIX="refactor" ;;
+  "chore") PREFIX="chore" ;;
+  *) PREFIX="feat" ;;
+esac
+
+# Create branch: <parent>/<type>/<bead-id>-<description>
+BRANCH_NAME="${PARENT_BRANCH}/${PREFIX}/$ARGUMENTS-${BEAD_TITLE}"
+git checkout -b "$BRANCH_NAME" 2>/dev/null || echo "Branch already exists or already on it"
 ```
 
+**Branch naming convention:**
+| Parent Branch | Bead Type | Example |
+|---------------|-----------|---------|
+| main | bug | `main/fix/bd-a1b2-login-error` |
+| develop | feature | `develop/feat/bd-c3d4-user-auth` |
+| release-v2 | chore | `release-v2/chore/bd-e5f6-update-deps` |
+
 ### Option B: Git Worktree (if --worktree flag)
 
 For isolated work that won't conflict with main workspace:
@@ -101,11 +127,30 @@ skill({ name: "using-git-worktrees" });
 **Worktree setup:**
 
 ```bash
+# Get current branch (parent branch)
+PARENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
+
+# Get task title for readable worktree name
+BEAD_INFO=$(bd show $ARGUMENTS --json 2>/dev/null)
+BEAD_TITLE=$(echo "$BEAD_INFO" | jq -r '.title // ""' | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | cut -c1-40)
+BEAD_TYPE=$(echo "$BEAD_INFO" | jq -r '.type // "task"')
+
+# Map bead type to branch prefix
+case "$BEAD_TYPE" in
+  "bug") PREFIX="fix" ;;
+  "feature"|"epic") PREFIX="feat" ;;
+  "refactor") PREFIX="refactor" ;;
+  *) PREFIX="feat" ;;
+esac
+
+# Create branch: <parent>/<type>/<bead-id>-<description>
+BRANCH_NAME="${PARENT_BRANCH}/${PREFIX}/$ARGUMENTS-${BEAD_TITLE}"
+
 # Verify .gitignore has worktree directory
 grep -q "^\.worktrees/$" .gitignore || echo ".worktrees/" >> .gitignore
 
-# Create worktree
-git worktree add .worktrees/$ARGUMENTS -b $ARGUMENTS
+# Create worktree with readable branch name
+git worktree add ".worktrees/$ARGUMENTS" -b "$BRANCH_NAME"
 
 # Navigate to worktree
 cd .worktrees/$ARGUMENTS

package/dist/template/.opencode/dcp.jsonc

@@ -14,28 +14,32 @@
 			// Nudge every 8 tool calls (slightly more aggressive than default 10)
 			"nudgeFrequency": 8,
 			// Protect state-modifying and critical workflow tools
+			// Updated for v1.1.8: Added question tool, removed legacy bd_* (use CLI)
 			"protectedTools": [
 				"write",
 				"edit",
+				"question",
 				"memory-read",
 				"memory-update",
 				"memory-search",
 				"observation",
 				"skill",
 				"skill_mcp",
+				"task",
+				"batch",
+				"todowrite",
+				"todoread",
+				"lsp",
 				"lsp_lsp_rename",
 				"lsp_lsp_find_references",
 				"lsp_lsp_goto_definition",
 				"lsp_lsp_code_actions",
 				"lsp_lsp_code_action_apply",
 				"lsp_lsp_organize_imports",
-				"bd_init",
-				"bd_claim",
-				"bd_done",
-				"bd_show",
-				"bd_reserve",
-				"bd_reservations",
-				"bd_sync"
+				"bd-reserve",
+				"bd-release",
+				"bd-msg",
+				"bd-inbox"
 			]
 		},
 		"discard": {

package/dist/template/.opencode/memory/observations/2026-01-09-pattern-ampcode-mcp-json-includetools-pattern.md

@@ -0,0 +1,42 @@
+---
+type: pattern
+created: 2026-01-09T08:04:40.257Z
+confidence: high
+valid_until: null
+superseded_by: null
+concepts: ["mcp", "includeTools", "ampcode", "skill", "token-optimization", "lazy-load", "filtering"]
+---
+
+# 🔄 Ampcode mcp.json includeTools pattern
+
+🟢 **Confidence:** high
+
+Learned from Ampcode's ui-preview skill (https://github.com/ampcode/amp-contrib/tree/main/.agents/skills/ui-preview):
+
+## Pattern: Lazy-load MCP with includeTools filtering
+
+1. **mcp.json file** (separate from SKILL.md):
+```json
+{
+  "chrome-devtools": {
+    "command": "npx",
+    "args": ["-y", "chrome-devtools-mcp@latest"],
+    "includeTools": ["navigate_page", "take_screenshot", "new_page", "list_pages"]
+  }
+}
+```
+
+2. **SKILL.md documents ONLY filtered tools**:
+- "Available Tools" section lists only the filtered tools
+- Workflow examples use only those tools
+- Note at bottom explains how to expand filter if needed
+
+3. **Token savings**: ~90% reduction (4 tools vs 26+ for chrome-devtools)
+
+## Applied to OpenCodeKit:
+- chrome-devtools: 11 tools (from 26+) 
+- playwright: 8 tools (from 17+)
+- Other MCP skills already minimal (2-4 tools), no filtering needed
+
+## Key insight:
+SKILL.md and mcp.json must be synchronized - don't document tools that aren't in includeTools filter, or agents get confused.

package/dist/template/.opencode/memory/project/gotchas.md

@@ -1,12 +1,46 @@
 ---
 purpose: Footguns, edge cases, and "don't forget this" warnings
-updated: 2025-01-05
+updated: 2025-01-09
 ---
 
 # Project Gotchas
 
 ## Configuration Quirks
 
+### OpenCode v1.1.7 → v1.1.8 Changes
+
+**v1.1.7 Features:**
+
+- **Question tool**: New interactive tool for gathering user preferences/clarifying instructions
+- **Config precedence fix**: Local `.opencode/opencode.json` now correctly overrides remote/global config
+- **`.claude` loading toggle**: Can disable via `--no-claude-prompts` / `--no-claude-skills` flags
+- **Task tool filtering**: Simplified subagent filtering
+
+**v1.1.8 Features:**
+
+- **Multi-select questions**: Question tool now supports `multiple: true` for multi-select
+- **Performance**: Chunked message loading, lazy diff rendering
+- **Full path fuzzy matching**: Autocomplete uses full file paths
+- **OpenTUI v0.1.70**: UI improvements
+
+**Plugin SDK Update Required:**
+
+```json
+"@opencode-ai/plugin": "^1.1.8"  // Was ^1.1.2
+```
+
+### DCP Protected Tools (v1.1.8)
+
+Legacy `bd_*` tool names don't exist - use actual custom tool names:
+
+| Old (Wrong)       | New (Correct) |
+| ----------------- | ------------- |
+| `bd_init`         | N/A (use CLI) |
+| `bd_claim`        | N/A (use CLI) |
+| `bd_reserve`      | `bd-reserve`  |
+| `bd_reservations` | `bd-release`  |
+| `bd_sync`         | N/A (use CLI) |
+
 ### DCP v1.1.3 Schema Breaking Changes
 
 1. **Legacy `strategies.onIdle` removed**: v1.1.2+ no longer supports this field
@@ -35,10 +69,23 @@ updated: 2025-01-05
 
 ### Protected Tools in DCP
 
-v1.1.3 recognizes more tool variants. Ensure these are protected:
-
-- `lsp_lsp_find_references`, `lsp_lsp_goto_definition` (plugin-specific naming)
-- `memory-search`, `skill_mcp`, `bd_sync` (often forgotten)
+v1.1.8 recognizes more tool variants. Ensure these are protected:
+
+```jsonc
+"protectedTools": [
+  // State-modifying
+  "write", "edit", "question",
+  // Memory/observation
+  "memory-read", "memory-update", "memory-search", "observation",
+  // Skills/tasks
+  "skill", "skill_mcp", "task", "batch", "todowrite", "todoread",
+  // LSP
+  "lsp", "lsp_lsp_rename", "lsp_lsp_find_references", "lsp_lsp_goto_definition",
+  "lsp_lsp_code_actions", "lsp_lsp_code_action_apply", "lsp_lsp_organize_imports",
+  // Beads (custom tools only - CLI uses bash)
+  "bd-reserve", "bd-release", "bd-msg", "bd-inbox"
+]
+```
 
 ## Time Wasters