Add stdout to command execution results

[vijit-lark]

Summary

• Capture buffered stdout from CommandHandler.execute() and include it in CommandResult so the full command output is available in the final result, not just via the real-time streaming callbacks.
• Thread the new stdout field through the wire protocol (CommandExecutionResultItem) and the Python client (CommandResultItem).
• Bump both runtimeuse and runtimeuse-client to 0.12.0.

Test plan

• TypeScript unit tests pass (npm test — 143 tests)
• Python unit tests pass (pytest test/test_client.py — 44 tests)
• E2E tests pass (pytest test -m e2e — 36 tests)
• E2B sandbox tests (require E2B_API_KEY)

Made with Cursor

---

Note

Medium Risk
Changes the command execution wire protocol and result types to include buffered stdout, which may affect clients expecting the old schema and increases returned payload size. Logic is straightforward but touches runtime execution and cross-language compatibility (TS server + Python client).

Overview
Command-only execution results now include buffered stdout. CommandHandler.execute() captures the final stdout (with secret redaction) and returns it alongside exitCode, and InvocationRunner.runCommandsOnly threads this through the command_execution_result_message payload.

The wire type CommandExecutionResultItem and the Python client model CommandResultItem add an optional stdout field, with tests updated/added to assert stdout presence on success and absence on failures. Package versions are bumped to 0.12.0 in both runtimeuse and runtimeuse-client.

^{Reviewed by Cursor Bugbot for commit ccdcc96. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ccdcc96. Configure here.}

[cursor]

Error path resolves without stdout, losing captured output

Medium Severity

When a command fails (non-zero exit code), exec's callback fires with an error and the Promise resolves at line 61 with { exitCode: code, error } — omitting stdout. Since Node.js execFile internally registers its close handler before the external one, the error resolve fires first, and the subsequent close handler's resolve (which does include stdout) becomes a no-op. This means any command that produces output before failing (e.g. a build tool that prints logs then exits non-zero) will have its stdout silently discarded from CommandResult, despite capturedStdout being correctly set on the line above.

Additional Locations (1)

• packages/runtimeuse/src/command-handler.ts#L84-L91

 

^{Reviewed by Cursor Bugbot for commit ccdcc96. Configure here.}