---
title: "Computer Use in Workflows"
canonical: https://trickest.com/docs/using-the-app/workflow-and-executions/using-computer-nodes
description: "Automate a desktop check, continue from another node, and handle human control during a run."
---

# Computer Use in Workflows

Use Computer Use when a workflow needs the desktop accessibility interface, including a native application or a browser step that must continue on the same screen. Start with a browser and desktop handoff, or follow the standalone desktop check below to learn the controls.

## Before you start

You need an Enterprise vault, workflow editing and execution access, a fleet, an available Computer Use tool, and a computer or saved snapshot you can use. Your deployment administrator must configure the interactive runtime and a computer CLI that supports desktop accessibility and same-computer continuation.

This is a workflow node. The [Agent Computer view](/docs/using-the-app/agent/using-the-computer) is a separate interaction surface with different control behavior.

## Example: change a desktop view and verify it

Connect Browser Use → Computer Use → Browser Use to check a desktop action from the browser afterward. This example opens the [practice inventory](/docs/examples/interactive-workflows/workspace.html), changes its display density through desktop accessibility, then reloads the page and checks that the choice persisted. The inventory contains synthetic data and needs no account.

<Frame editorial maxWidth="780px" darkSrc="https://res.cloudinary.com/db14crach/image/upload/v1792764749/www/docs/connectors-workflows-2026-10-23/product/browser-computer-handoff-results-dark-750a4a661fe8f134.png" caption="A completed Browser → Computer → Browser workflow. The desktop node changes the view, and the final browser node verifies it after reload. All three nodes passed.">
  <img src="https://res.cloudinary.com/db14crach/image/upload/v1792764748/www/docs/connectors-workflows-2026-10-23/product/browser-computer-handoff-results-light-73cc4411a81aa60b.png" alt="Completed workflow showing a browser inventory, the actual desktop with Compact view selected, and the browser after reload; all three nodes say Checks passed." />
</Frame>

1. **Open inventory · Browser Use.** Open the practice page and click **Reset demo**. Check that `#asset-count` equals `3 assets`, then save `inventory-start`.
2. **Change desktop view · Computer Use.** Continue the current screen. Wait for `Asset review`, click the accessible `push button` named `Compact view`, then check for the exact desktop text `Compact`. Save `compact-desktop`.
3. **Verify after reload · Browser Use.** Continue the current page and reload it. Check that `#density` equals `Compact` and `#asset-count` equals `3 assets`, then save `compact-persisted`.

<Frame editorial maxWidth="760px" caption="Computer Use saved the actual desktop after clicking Compact view. The next Browser Use node verified that Compact persisted after reload.">
  <img src="https://res.cloudinary.com/db14crach/image/upload/v1792764752/www/docs/connectors-workflows-2026-10-23/product/computer-compact-desktop-result-7099eaa2ebe9d19d.png" alt="Actual Computer Use output showing Chromium on the desktop, Compact view selected, and all three synthetic assets." />
</Frame>

### Import and configure the example

1. Download the [browser and desktop handoff workflow](/docs/examples/interactive-workflows/browser-computer-handoff.workflow.json).
2. Open an empty workflow. Right-click its canvas, select **Import workflow…**, then **Upload a .json file**. Import adds the example nodes to that workflow.
3. Choose a computer or snapshot only on **Open inventory > Setup**. In its inline steps, set **Page URL** to the practice page address for your deployment and select **Save steps**.
4. Check **Change desktop view > Continue after…** points to **Open inventory**, and **Verify after reload** continues after **Change desktop view**. Both continuation nodes have their own steps and inherit the previous computer.
5. When ready, use **Execute** to test the sequence. Inspect assertions in all three `result.jsonl` files and compare the desktop screenshot with the final browser screenshot. If the desktop target cannot be found, check that the practice page is foregrounded and its accessibility role and name match the recipe.

The first computer is intentionally unselected. The [desktop recipe](/docs/examples/interactive-workflows/desktop.recipe.json) uses the desktop role `push button`; Browser Use recipes use the browser role `button`. The [final browser recipe](/docs/examples/interactive-workflows/verify-desktop.recipe.json) checks the DOM after reload. These are deterministic steps; they do not call a model.

The graph and recipes pass the v1.2.1 import and configuration validators. This example completed on a dedicated demo computer. The desktop accessibility click and all browser assertions passed, with `passed` results in all three `result.jsonl` files. For a sequence that stays entirely in the browser, see the [Browser Use example](/docs/using-the-app/workflow-and-executions/using-browser-nodes#example-review-high-risk-assets).

## Choose a computer or continue a chain

Use **Add node** to add **Computer Use**, then open **Setup**.

For a new desktop session, choose **Choose a computer**, select **Computer**, then choose **Current state** or a saved snapshot under **Start from**. Current state uses the existing computer and leaves it running. A run started from a snapshot creates a separate computer that stops afterward.

To continue an earlier Browser Use or Computer Use node, select **Continue after…** and choose **Previous node**. The node uses the same computer and signed-in account after the earlier checks pass. Each node still needs its own steps.

<Frame editorial maxWidth="360px" darkSrc="https://res.cloudinary.com/db14crach/image/upload/v1792713997/www/docs/release-1-2-1-2026-10-23/product/computer-setup-dark-c0150d6d30e41d9b.png" caption="Continue after uses the previous node’s computer. Run the whole workflow to test the sequence.">
  <img src="https://res.cloudinary.com/db14crach/image/upload/v1792713999/www/docs/release-1-2-1-2026-10-23/product/computer-setup-light-db307555a502b1eb.png" alt="Computer Use Setup continuing after a previous node on the same computer." />
</Frame>

## Configure the steps

Select **Write steps** under **Steps**. For a standalone check, choose **Open a page** and set **Page URL** to `https://example.com`. Add these actions:

| Recipe action | What to configure |
| --- | --- |
| **Wait for text** (`wait`) | **Text:** `Example Domain` |
| **Check text** (`assert_text`) | **Text:** `Example Domain` |
| **Save screenshot** (`screenshot`) | **Screenshot name:** `desktop-check` |

Select **Save steps**. Computer Use matches desktop accessibility text; it does not use the browser CSS selector from the Browser Use recipe.

For a native application, set **Start > Open an application** and choose a supported application, such as `xterm` or `pcmanfm`. Do not paste shell commands into an application's name field.

To preserve the previous node's current screen, select **Continue current screen**. Opening a URL again can reset the state you intended to verify.

## Supply a recipe file

The [computer check recipe](/docs/examples/release-1.2.1/computer-check.recipe.json) contains the same standalone check:

```json
{
  "version": 1,
  "url": "https://example.com",
  "steps": [
    {"action": "wait", "text": "Example Domain"},
    {"action": "assert_text", "text": "Example Domain"},
    {"action": "screenshot", "name": "desktop-check"}
  ]
}
```

Select **From a file > Connect a recipe** and supply one JSON file. Recipe files are a different input from the previous node's results folder. Use **Continue after…** for the shared-computer connection.

## Run and review

Use **Execute** for a continuation chain. Check the node's desktop preview, logs, `result.jsonl` and saved screenshots. An execution-completed badge does not prove an assertion passed. Keep the outcome and evidence together when reporting the result.

A later node can use the results folder to build a report, but it cannot feed that folder directly into another node's recipe input.

## Take control when the run needs a person

In a running Computer Use node, select **Pause & take control** when it is available. Wait for **You have control · run paused** before interacting. Complete the requested interaction, then select **Resume automation**. Resuming disables viewer input before automation continues.

Closing or disconnecting the viewer leaves this workflow automation paused. It does not resume it. Verify run state before leaving the workflow unattended.

<Note>
The workflow-node pause behavior differs from the Agent desktop. Taking control of the Agent desktop does not pause the Agent turn; stop that turn before working on the same application.
</Note>

## Recover from a failure

If the computer or snapshot is unavailable, choose a usable source. If an accessibility action cannot find its target, inspect the desktop screenshot and the expected element role and name. For login failures, establish the intended session and use the signed-in-account check before later actions. A snapshot-created computer can stop on failure, so do not assume it remains available for partial retries.

The downloadable recipes pass the released validator. The example images show a completed platform workflow and its saved desktop output. The Setup screenshot shows configuration.

---
_Markdown source of https://trickest.com/docs/using-the-app/workflow-and-executions/using-computer-nodes._
