Skip to content

For the complete documentation index, see llms.txt. Markdown versions are available by appending .md to documentation page URLs. Read the agent handbook.

Zortex Docs
Start searching Install Vision
Use your computer

Use your computer

Discover your installed desktop controls, inspect the right application, and invoke an operation through the CLI or agent.

On this page

Computer tools operate desktop applications through an installed provider. Use them when your task needs an application's interface and a connected-app or browser operation cannot supply the required result.

Installed provider

The available desktop methods depend on the provider and operating system. Indra does not promise one universal screenshot, window, or keyboard command across installations.

Before you start

You need a working computer provider, access to the target app, and the operating-system permissions required by that provider. On macOS these can include Accessibility and screen-recording access. An installed executable alone does not prove that access is working.

Keep your chosen application, document, and account explicit. If you want background work, the selected route must support it. A foreground-only provider needs your direction before it takes over the active desktop.

Inspect and control an application

  1. Find the available methods

    In a terminal, use your existing Vault path. Commands can start the configured background host; review Sync information first if you want automatic full collection disabled:

    Shell
    indra_root='/absolute/path/to/your-existing-vault'
    indra --root "$indra_root" actions --json '{"source":"cua"}'
    

    Read the returned names and descriptions. Start with a method that can inspect applications, windows, or the current screen. Use an actual returned name; do not substitute a command from another computer-use product.

    If the catalog is unavailable, inspect the installed component state:

    Shell
    indra --root "$indra_root" manage --json '{"what":"plugins","about":"cua","limit":25,"offset":0}'
    

    An absent component, an inactive component, and denied OS permission require different fixes. Follow the returned error and Permissions.

  2. Inspect the chosen method

    Shell
    indra --root "$indra_root" actions --json '{"source":"cua","method":"<returned-method>"}'
    

    Replace the placeholder with the exact name from the catalog. Read required arguments and the method's effect. Supply the actual window, application, or other identifiers from an observation rather than guessing them.

  3. Invoke it

    Desktop methods run through connector.invoke. This is a template: replace the method name and fill input.params using the method's schema before running it. An empty object is valid only if the selected method has no required arguments.

    Shell
    indra --root "$indra_root" action --json '{"name":"connector.invoke","params":{"source":"cua","method":"<returned-method>","input":{"params":{}}}}'
    

    The agent equivalent is:

    Text
    indra.action({"name":"connector.invoke","params":{"source":"cua","method":"<returned-method>","input":{"params":{}}}})
    

    The returned result should establish which application or window you are looking at. If the wrong document is open, correct the target before sending input. A successful catalog lookup has not exercised the desktop provider.

  4. Act, then inspect again

    Choose the next method from the installed catalog, inspect its schema, and supply the observed target. After navigation, a dialog, a window move, or a focus change, obtain a fresh observation. Coordinates from an earlier window layout may point somewhere else.

    Verify the requested result in the app. For document work, continue with Work in desktop apps to save and inspect the output.

Delegate a desktop task

Give the agent a concrete target and result:

Agent host

Example request

In the specified document, correct the date in the heading and save a separate copy in the requested folder. Preserve the original. Inspect the saved copy and report its location. Use a background route if available; tell me if the installed provider requires foreground control.

What to expect

The agent should discover its actual methods and keep your unrelated work intact. It should not treat a computer provider as access to every personal browser profile or account.

When the route fails

  • No cua source or methods: repair or install the supported provider using your installation's setup guidance.
  • Permission denied: grant only the operating-system access the provider actually requests, then recheck the observation operation.
  • Target app or window missing: open or locate the intended app and inspect again.
  • Action response lost: check the current app state before repeating the action.
  • Foreground behavior conflicts with your request: use another capable route or keep the unmet background requirement explicit.

A missing desktop provider does not establish that browser tools are unavailable; they are separate capabilities.

Suggested