Environment
- OS: Windows
- plannotator version: v0.17.4
- Context: OpenCode
Issue
When calling submit_plan in a workspace without Obsidian vault configured, getting Bun server error:
Steps to Reproduce
- Have multiple workspaces, some with Obsidian vault configured
- Switch to a workspace WITHOUT vault configured
- Call
submit_plan in OpenCode
- Error appears
Expected Behavior
submit_plan should work regardless of vault configuration
Suspected Cause
PR #526 (sidebar consolidation) added new vault API endpoints that may not handle "no vault in current workspace" case correctly.
Workaround
Rollback to v0.17.3

Environment
Issue
When calling
submit_planin a workspace without Obsidian vault configured, getting Bun server error:Steps to Reproduce
submit_planin OpenCodeExpected Behavior
submit_planshould work regardless of vault configurationSuspected Cause
PR #526 (sidebar consolidation) added new vault API endpoints that may not handle "no vault in current workspace" case correctly.
Workaround
Rollback to v0.17.3
v0.17.7 is out with the fix.
Root cause: OpenCode's
@hono/node-serveradapter (added for Node.js support) patchesglobal.Responsewith a polyfill class. This happens inopencode web,opencode serve, and any mode that starts the HTTP server (--port,--hostnameflags, orserver.*config). Bun.serve() validates return types using internal type tags, notinstanceofso the polyfilled Response objects were rejected, producing the "fetch(req) did not return a Response object" page. The error handler added in v0.17.6 also usednew Response(...), which is why it didn't fire either.Plain
opencodeTUI without flags was never affected in that mode, OpenCode uses an internal RPC bridge instead of the…