git:20260918.b7543ae to git:20260923.b2a6af5

---

name: computer-use

description: Control local desktop applications through Computer Use for tasks that require reading or operating app UI. Prefer purpose-built connectors, APIs, or CLIs when available.

---

## node_repl + @qwen-code/cua-sdk (Computer Use)

- Use `node_repl` (JavaScript) for all Computer Use actions.

- Do not use other technologies besides `node_repl` for computer interactions, unless specifically requested by the user (e.g. AppleScript, `osascript`, JXA, System Events, synthesized input).

- Prefer a dedicated plugin or skill when it can complete the task; use Computer Use for app interactions that are not exposed through a more specific interface.

- `node_repl` state is persistent across calls.

- For text output, use `nodeRepl.write(...)`. It takes a string; use `JSON.stringify(...)` only for textual metadata. For an observation, write its `.text` and emit its screenshots as images; do not stringify an observation or driver result containing image bytes.

- Omit `yield_time_ms` for ordinary UI calls to use the default 10-second wait. A shorter yield does not speed up the action and can add a `node_repl_wait` round. Use a shorter yield only when you need control back before completion; if a cell is still running, collect its result with `node_repl_wait` before issuing dependent actions.

## Forwarding results in Codex code mode

When calling `node_repl` through `tools.*` inside Codex's outer `functions.exec`,

forward each returned `content` block by its type. `nodeRepl.emitImage(...)`

produces an MCP image block; the outer script must pass that block to `image()`

for the model to receive an image. Use the tool name exposed by your MCP server:

```js

const result = await tools.mcp__node_repl__node_repl({ code });

for (const block of result.content ?? []) {

if (block.type === 'text') {

text(block.text);

} else if (block.type === 'image') {

image(block);

}

}

```

Here `code` is the JavaScript to run in the persistent Node REPL. Keep the

forwarding loop in the outer code-mode script, outside that `code` string.

Apply the same loop to `node_repl_wait` results: images may arrive only when a

running cell completes. Forward text blocks too, including running-cell IDs and

errors. Direct MCP tool calls do not need this outer forwarding loop.

Do not use `text(result)`, `text(block)`, or `JSON.stringify(result)` to forward

an MCP result containing images: this turns image base64 into text, consuming

context without showing the image. `image()` accepts one image block, not the

whole result, so do not use `image(result)` either.

## Bootstrap

If `node_repl` is unavailable, run:

```bash

qwen mcp add --scope user node-repl npx -y @qwen-code/node-repl-mcp@0.1.6

```

Tell the user to restart Qwen Code, then stop. If only the SDK import is missing,

run the second command and retry.

Reuse an existing `computer` connected to the intended desktop. Otherwise import

```js

globalThis.computer = await (

await import('@qwen-code/cua-sdk/computer-use')

).ComputerUse.create();

var platform = await computer.getPlatform();

nodeRepl.write(`Connected platform: ${platform}`);

```

```ts

type ComputerUse = {

>;

},

};

mode: 'full' | 'diff' | 'no_change';

text: string;

screenshot?: { images: Array<{ mimeType: string; dataBase64: string }> };

};

```

```js

```

```js

```

```js

nodeRepl.write(state.text);

for (const image of state.screenshot?.images ?? []) {

await nodeRepl.emitImage(`data:${image.mimeType};base64,${image.dataBase64}`);

}

```