You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run `taskwing doctor` to verify your OpenCode installation:
329
+
```bash
330
+
taskwing doctor
331
+
# ✅ MCP (OpenCode): taskwing-mcp registered in opencode.json
332
+
# ✅ Skills (OpenCode): 6 skills validated
288
333
```
289
334
290
335
**Integration Testing:**
@@ -297,8 +342,20 @@ go test -v ./tests/integration/... -run "TestOpenCode"
297
342
```
298
343
299
344
**Development Notes:**
300
-
- During development, use `taskwing-local-dev-mcp` for testing
301
-
- The production MCP uses the Homebrew-installed binary
345
+
346
+
> ⚠️ **CRITICAL**: When developing or testing TaskWing code changes, you **MUST use `taskwing-local-dev-mcp`** instead of the production MCP. The production `taskwing-mcp` uses the Homebrew-installed binary, which won't reflect your code changes.
347
+
348
+
```bash
349
+
# Development workflow:
350
+
# 1. Make code changes
351
+
# 2. Build: make build
352
+
# 3. Test via local dev MCP (uses ./bin/taskwing)
353
+
# 4. Run tests: make test-opencode
354
+
```
355
+
356
+
For OpenCode development specifically:
357
+
- During development, configure `taskwing-local-dev-mcp` in your opencode.json
358
+
- The production MCP (`taskwing-mcp`) uses the Homebrew-installed binary
0 commit comments