THE FIELD GUIDE / 08Desktop controls

Keep your hands on the work that matters.

Use supported Windows controls, inspect visible context and work with connected applications.

5 capabilities3 practical walkthroughs
A cream desktop monitor and an indigo audio control pebble
ONE LITTLE REQUESTShow my available audio outputs and switch the default to my headphones.
JARVIS / IN EVERYDAY LIFEIllustrated possibilities. Your tools do the work.
01 / THE POSSIBILITIES

A little more
within reach.

A useful desktop assistant needs to know what is available before it acts. Jarvis exposes supported Windows controls alongside application adapters, screen capture and local text recognition, with capability checks for the machine it is actually running on.

See it in your day
01

Windows & window layout

Inspect supported windows and apply available layout operations using actual window identities.

02

Screen capture & text

Capture a screenshot or recognize visible text locally in an identified foreground window. Model-based image interpretation needs vision support.

03

Audio & display controls

Inspect and adjust supported volume and brightness controls, list active audio outputs and verify a chosen default output device.

04

Connected editor actions

Inspect VS Code context, open a known file, insert text into a verified selection and run supported commands or known tasks.

05

Calculations, units & text cleanup

Use deterministic arithmetic, percentages, bill splitting and supported unit conversions. Sort lines, remove duplicates or transform supplied text without asking a model to guess the calculation.

02 / PUT IT INTO YOUR DAY

Ordinary requests.
Useful little transformations.

Follow the thought from the first sentence to the result. Make the names, files, and timing your own.

THE EVERYDAY / WORKFLOW 01

Move the sound to the right device

You plugged in a device but Windows is still sending sound to the wrong output.

An illustrated example of move the sound to the right device
AN ILLUSTRATED WORKFLOW
START WITH THIS
Show my available audio outputs and switch the default to my headphones.
  1. 01

    Start with the context

    Jarvis lists active output devices and their actual IDs instead of guessing a device name.

  2. 02

    Let the work unfold

    It selects the identified device for the requested Windows default roles and checks the resulting setting.

  3. 03

    Check the result

    If an already-open application still plays elsewhere, restart its playback stream or change that application's own output setting.

THE RESULT TO LOOK FOR

A verified Windows default output change where supported. Existing playback streams may keep their previous output.

THE EVERYDAY / WORKFLOW 02

Read an error that will not copy

A dialog shows useful text, but you cannot select it normally.

An illustrated example of read an error that will not copy
AN ILLUSTRATED WORKFLOW
START WITH THIS
Read the visible error text in this window.
  1. 01

    Start with the context

    Jarvis identifies the foreground window and checks that the requested target is still the active one.

  2. 02

    Let the work unfold

    The desktop tool captures that window and runs local text recognition with the available language support.

  3. 03

    Check the result

    Review exact error codes against the screen before using them in a search or code change.

THE RESULT TO LOOK FOR

Recognized visible text with the limits of OCR. It does not reveal hidden content or guarantee every character is correct.

THE EVERYDAY / WORKFLOW 03

Move selected text into the right editor

You are collecting useful excerpts without switching back and forth to copy and paste.

An illustrated example of move selected text into the right editor
AN ILLUSTRATED WORKFLOW
START WITH THIS
Append this selected browser text to my connected editor file.
  1. 01

    Start with the context

    The connected source returns the current selection and its identity.

  2. 02

    Let the work unfold

    The destination editor connection and selection are checked so text is not inserted into a stale or different target.

  3. 03

    Check the result

    Append preserves existing text; replacement must be explicit. Inspect the editor result after insertion.

THE RESULT TO LOOK FOR

Text inserted into the verified supported destination. A disconnected editor or changed selection produces an actionable failure.

03 / MAKE THE CONNECTIONS

A little preparation.
A lot of possibility.

An illustrated setup sheet: download, configure, say helloOpen the installation guide
01

Inspect installed capabilities

The desktop status command reports what this machine and its integrations support.

uv run jarvis desktop status
02

Connect supported applications

Browser and editor adapters add structured selection and command support. Arbitrary application internals are not available just because their windows are visible.

03

Choose the right vision path

Local OCR needs the Windows recognition language; interpreting a screenshot with the task model requires image support from that provider.

04 / A CLEAR PICTURE

Good to know
before you begin.

Device support varies

Brightness, audio controls and window operations depend on the hardware, Windows environment and installed dependencies. Check status rather than assuming universal support.

Computer input is a separate tool

The high-level computer tools can click, type and press keys where available. Those actions still need the correct target and configured permissions; they do not provide deep integration with every app.

05 / A LITTLE MORE CONTEXT

The natural next questions.

Workflow images are generated illustrations, not screenshots of a connected assistant. Availability depends on your configured tools and providers.

FOLLOW YOUR CURIOSITY

A few more possibilities.

Back to all features