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
Work in desktop apps

Work in desktop apps

Take a document task from the correct application through a saved, inspected output.

On this page

Use this workflow to edit a document, export a file, or change an application setting. It works with the desktop methods your installation actually exposes; first complete Use your computer.

Define the output

Name the app or document, the change, and where the result should go. Say whether to update the original or create a copy when that choice matters.

For example:

Open the selected report, replace the obsolete date in its heading, and export a PDF to the specified output folder. Keep the source document. Check the PDF's heading before returning its location.

The agent can recover routine paths and document identity from authorized context. If two different documents plausibly match, it should resolve that ambiguity before editing.

Follow the task in the application

Step What you do, or ask the agent to do What establishes progress
Open Locate the exact document in its app. Correct title, location, and relevant contents.
Inspect Read the portion that will change and any relevant dialog. The starting value and intended target are clear.
Edit Perform the requested change with current controls. The new content appears in the intended place.
Save Use the app's save or apply operation. The app reports the saved/applied state for that target.
Export, if requested Choose the requested format and destination. The export finishes and the file exists at that location.
Check Open the saved result or inspect it through a supported file reader. The required content, format, and change are present.

When operating directly, use the application's own visible controls for these steps. When operating through Indra, discover and invoke the provider's matching methods as described in Use your computer. The names and arguments are provider-specific.

Check a saved or exported file

A change visible in an editor can still be unsaved. An export dialog closing does not establish that the exported file contains the right content.

Check the exact output file and the part affected by the task. For the example above, open the PDF and inspect its heading. If layout matters, inspect the rendered result as well as its text. For a setting change, revisit the setting or observe the behavior it controls.

Use Work with local files to locate and inspect an output through an installed file provider. Do not treat a temporary path on the agent host as a file automatically delivered to your computer.

Recover after an interruption

If an action may already have happened, inspect current state first. Repeating Save as, a submission, or a transformation can create a second file or duplicate a change.

If the app closes or the provider disconnects:

  1. Locate any verified saved output.
  2. Reopen the intended document through a supported route.
  3. Inspect which edits survived.
  4. Continue only the missing work.

Keep unsaved or uncertain changes explicit. A missing window is not proof that the work was saved or lost. If the next step requires an unavailable device challenge or OS permission, identify that exact step and retain the rest of the task.

Deliver the result

Return the actual file or application reference, the completed change, and the check that established it. If the task requested a copy, distinguish it from the original. If it requested sharing, follow Save and share results; saving locally and sharing with another person are separate actions.

Close only task-owned resources when their work is finished. Preserve the person's unrelated windows, documents, and active pointer. If another person or agent must continue, provide the document identity, verified saved state, remaining step, and destination.

Suggested