Summary

warpgrep_codebase_search consistently returned no contexts when the plugin runs inside OpenCode (Bun runtime):

Search failed: search returned no error details.

Root cause

The morphsdk WarpGrepClient.execute() with streamSteps: true is an async generator. Its final return processAgentResult(...) hands back a Promise. Per ECMAScript spec, async generators should auto-await return values, and Node.js does. Bun does not — it yields the unresolved Promise as the .next() value.

The plugin consumed the generator with:

const { value, done } = await generator.next();
if (done) {
  result = value;  // ← Promise, not WarpGrepResult
  break;
}

So result was a Promise whose .success was undefined, and formatWarpGrepResult returned the generic failure message.

Fix

One line:

result = await value as WarpGrepResult;

This is harmless on Node.js (await on a non-Promise is a no-op) and fixes Bun.

Fixes #24.

Changes

• Explicitly await the async generator return value in warpgrep_codebase_search.execute().
• Add a test that verifies the result is correctly resolved under Bun.

Diagnosis trail

Initial hypothesis (worktree pointing at OpenCode snapshot git dir) was ruled out by diagnostic logging: directory and worktree both correctly pointed at the real workspace (isWorktreeGitMetadata=false). The actual issue was found by dumping the result object, which had all fields undefined — confirming an unresolved Promise was being used as the result.

Direct SDK calls via node succeeded because Node.js auto-awaits async generator return values per spec. The failure only occurred through the plugin running inside OpenCode (Bun runtime).

Reproduction

warpgrep_codebase_search({
  "search_term": "Find README.md and CHANGELOG.md files in this repository."
})

Result before fix:

Search failed: search returned no error details.

After fix: returns contexts for README.md and CHANGELOG.md.

Validation

$ bun test
67 pass
0 fail
170 expect() calls

$ bun run typecheck
(clean)

$ bun run build
(clean)

Baseline before changes was 66 pass / 0 fail; the one new test brings it to 67 pass / 0 fail.

Verified end-to-end in OpenCode (Bun runtime): warpgrep_codebase_search now returns contexts successfully.

Environment

• @morphllm/opencode-morph-plugin: 2.0.13
• @morphllm/morphsdk: 0.2.173
• OpenCode: 1.16.2 (Bun runtime)
• OS: macOS

Notes

This is a plugin-side workaround for a Bun runtime quirk. The underlying issue is in morphsdk'"'"'s async generator (return processAgentResult(...) without await), but since morphsdk is a separate package and the one-line await works across both Node.js and Bun, the plugin-side fix is the safest minimal change.