opencode completion output is truncated, producing an unparseable zsh script (unmatched ") #30831

Activity

1. github-actions

   assigned

   kitlangton

   on Jun 5, 2026
2. ben181231 commented on Jun 5, 2026

   

   ben181231

   on Jun 5, 2026

   Last edited by ben181231

   Author

   More actions

   Quick source dive — the likely culprit is in packages/opencode/src/index.ts:

   opencode/packages/opencode/src/index.ts

   Lines 202 to 208 in 9211ef7

   	} finally {
   	// Some subprocesses don't react properly to SIGTERM and similar signals.
   	// Most notably, some docker-container-based MCP servers don't handle such signals unless
   	// run using `docker run --init`.
   	// Explicitly exit to avoid any hanging subprocesses.
   	process.exit()
   	}

   } finally {
     // Some subprocesses don't react properly to SIGTERM and similar signals.
     // ...
     // Explicitly exit to avoid any hanging subprocesses.
     process.exit()
   }

   The try { await cli.parse() } block runs yargs, which for the completion subcommand writes the generated shell script directly to process.stdout. Control then falls into finally, which calls process.exit() unconditionally. Node's process.exit() does not wait for writable streams to drain — when stdout is a pipe (as with eval "$(opencode completion)"), the kernel-side pipe buffer isn't fully consumed before the process is torn down, so the tail of the output is dropped. That's how the script ends mid-string with the unmatched ".

   This is consistent with the other reports of this race (#29866 JSON stream, #26114/#28606 --help newline, #29330 export | jq, #26399 debug skill), and looks like exactly what closed PR #29340 ("fix(opencode): flush stdio before cli exit") was attempting to address.

   Suggested fix

   Drain stdio before exiting, e.g.:

   } finally {
     await Promise.all(
       [process.stdout, process.stderr].map(
         (s) => new Promise<void>((resolve) =>
           s.write("") ? resolve() : s.once("drain", () => resolve()),
         ),
       ),
     )
     process.exit()
   }

   Setting process.exitCode and letting Node exit naturally would also work, but conflicts with the existing rationale for the explicit process.exit() (hanging subprocesses), so an explicit drain-then-exit is the safer change.

   ---

   (Posted by Claude Code on behalf of @ben181231)
3. kagura-chen commented on Jun 5, 2026

   

   kagura-chen

   on Jun 5, 2026

   Contributor

   More actions

   I'd like to work on this. The fix should drain stdout/stderr before the process.exit() in the finally block of packages/opencode/src/index.ts. I'll add a drain-then-exit pattern as suggested, with a regression test.
4. github-actions commented on Aug 5, 2026

   

   github-actionsBot

   on Aug 5, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
5. github-actions

   closed this as not plannedon Aug 5, 2026