Skip to content

Hands-free fleet orchestration

Computer use and voice

Speak a goal and hand it to an agent on your own machine: that is the design. The design keeps the agent's actions visible, and approval from your phone is planned. OmniConflux 0.3.0 for Omarchy, macOS on Apple silicon and Windows is released in closed beta. Voice and computer use are planned, and detailed controls will be documented at launch.

Join the waitlist

How the workflow operates

  1. Stage 01

    Speak the goal

    Local transcription, one command

    You say what you want, such as "Run the staging checks on the checkout flow." The voice tool is designed to transcribe your speech locally with whisper.cpp and send the text as a command to one of your harnesses.

  2. Stage 02

    The agent does the work

    Your harness, your tools

    The harness is designed to hand the command to an agent on your own machine, with the tools and access you chose for it. How computer-use agents read and act on the screen will be documented at launch.

  3. Stage 03

    Show the actions

    Visible steps, not hidden work

    The design goal is simple: the actions an agent takes are shown to you as they happen. The exact interface will be documented at launch.

  4. Stage 04

    Independent verification

    A different vendor reviews the work

    In the design, when the task finishes, a verifier from a different vendor reviews the result. A second perspective can catch what the first agent missed. It is a check on the finished task, not a guarantee that every task is right.

Safety Model

Human oversight by design

Autonomous work needs clear boundaries. These are the design goals for computer use and voice. Detailed controls will be documented at launch.

  • Actions shown

    The goal: no agent works out of sight. Each action is meant to be shown to you as it happens. How that looks will be documented at launch.

  • Approve from your phone

    Planned: approve once, for this session, or always, from your phone. Which actions ask for approval will be documented at launch.

  • Independent review

    Every agent task gets a verifier from a different vendor. It is a second check on the finished task, not a guarantee.

  • Documented at launch

    Controls for pausing or stopping an agent, and how its work is kept apart from yours, will be documented at launch. We will not present a control as available before it ships.

Honest Engineering Boundaries

Capabilities and real technical limits

Computer use and voice are designed for structured work, and they have real limits. Here they are, plainly.

  • CLI and APIs first

    Command-line tools and direct APIs are usually faster and more predictable than screen-based automation. When a job can be done through a CLI or an API, that is usually the better route.

  • Latency and visual reasoning

    Vision models take seconds to read each screen. Computer use suits background procedures and end-to-end checks, not real-time control.

  • OS permission requirements

    Screen capture and input control need operating system permissions that you grant. There is no zero-config way around the operating system security model.

  • Credentials and enterprise tokens

    Planned managed fleets will run only on your own API keys or enterprise tokens. We never run agents on customers' personal subscription seats from a hosted backend.

Frequently asked questions

How will phone approval work?

Phone approval is planned, not shipped. The design: when an agent reaches an action that needs your say, you approve once, for this session, or always. Which actions ask, and how your phone is linked, will be documented at launch.

Does my voice audio leave my local machine?

The voice tool is designed to transcribe speech locally with whisper.cpp, so the audio stays on your machine. Only the text command goes to your harness. What happens next depends on the agent and model you chose for that harness.

Can an agent take over my computer while I am working?

Computer use is planned. How agents share a machine with you, and how to keep their work apart from yours, will be documented at launch.