What agent orchestrators work on Windows?

Summary

• Native Windows support varies across coding-agent tools. Hermes Agent says "Native Windows is fully supported", Claude Code, Cursor's CLI and Pi ship Windows installers, and Superset lists Windows as "not yet available".
• Omnigent runs natively on Windows "in a degraded mode": the server, the web UI and the SDK harnesses (claude-sdk, cursor, codex) work, but the tmux terminal wrappers and the filesystem and network sandboxing don't.
• On Windows, Omnigent contains agents in a Windows Job Object, which limits the process tree and resources but doesn't isolate the filesystem or network. Its README points to Linux, macOS or WSL for the rest.
• On Databricks, "Omnigent is in Beta" (the open-source project lists "Status: alpha"). A Databricks Sandbox host runs the agent in the cloud, so you can drive it from a Windows browser or the desktop app.

What agent orchestrators work on Windows?

Several coding-agent orchestrators install on Windows today, but installing and having every feature are different things. Omnigent, the open-source meta-harness, runs natively on Windows in a degraded mode: its server, web UI and SDK-based harnesses work, while terminal wrappers and OS-level sandboxing need Linux, macOS or WSL. If isolation matters to you, run the agent on another host and drive it from Windows.

Which tools document Windows support?

Tool	Role	What its docs say about Windows
Omnigent	Meta-harness over many agents	Runs natively "in a degraded mode"; install with uv; the desktop app has a Windows installer
Hermes Agent	Agent that spawns subagents	"Native Windows is fully supported" through a PowerShell installer; WSL2 also works
Claude Code	Agent with subagents and parallel sessions	PowerShell, CMD and WinGet installs, WSL, and a desktop app for x64 and ARM64 Windows
Cursor CLI	Agent CLI that orchestrators drive	A PowerShell installer next to the macOS, Linux and WSL script
Pi	Minimal agent harness	A PowerShell installer
Superset	Desktop app for parallel CLI agents	Windows "not yet available"; macOS is the primary target

On native Windows, Claude Code's docs recommend Git for Windows so it can use its Bash tool; without it, Claude Code uses PowerShell as the shell tool.

What works in Omnigent on native Windows?

The README is specific. These work: omnigent server, the web UI, and SDK-based harnesses through omnigent run <agent.yaml> with the claude-sdk, cursor or codex harness. Agents run under a Windows Job Object for process-tree containment. windows_jobobject is the default sandbox type on Windows, as linux_bwrap is on Linux and darwin_seatbelt on macOS, so the same agent YAML works across platforms. These don't work on Windows:

• the native omnigent claude, omnigent codex and omnigent cursor tmux/PTY terminal wrappers, so use an SDK harness or the web UI instead;
• bwrap and seatbelt filesystem and network sandboxing, and the L7 egress proxy. The Job Object backend "contains the process tree and enforces resource limits but does not isolate the filesystem or network".

The bootstrap script is POSIX-only, so install with uv:

uv tool install --python 3.12 omnigent
# or from the repo:
uv tool install --python 3.12 git+https://github.com/omnigent-ai/omnigent.git

How do you get the missing features from a Windows machine?

Option	How it works	Trade-off
WSL	Install Omnigent inside WSL, which the README names for the wrappers and sandboxing	You work in a Linux environment on the same machine
A Linux or macOS host	Register it with omnigent host <server-url>, then pick it from the web UI or desktop app on Windows	The host has to stay online
A cloud sandbox	Run sessions in Modal, Daytona, E2B, Kubernetes, Databricks or other sandboxes, launched from the CLI or provisioned per session by the server	Needs a provider account or a server set up for managed hosts

How Databricks approaches Windows users

On Databricks, "Omnigent is in Beta". The Databricks quickstart has a Windows note: use the uv install, because the install script supports only macOS and Linux; the tmux-based terminal wrappers aren't available; and agents run without file system or network isolation. For a fuller setup, choose a Databricks Sandbox host. Databricks provisions and runs it in the cloud, it keeps running when your laptop is off, your credentials never leave Databricks, and models route through your workspace's Foundation Model APIs over Unity Gateway. You start it in the browser at <workspace-url>/omnigent by picking Sandbox in the host picker, and the desktop app, available for macOS, Windows and Linux, connects to the same workspace URL. Databricks Sandbox is in Beta and available in select AWS regions. Its network egress isn't restricted, so what you gain is a separate cloud host, not a fenced network.

FAQs

Does Omnigent sandbox agents on Windows?

Partly. A Windows Job Object contains the process tree and enforces resource limits, but it doesn't isolate the filesystem or network.

Can I run Claude Code or Cursor through Omnigent on Windows?

Yes, as SDK harnesses: omnigent run <agent.yaml> with claude-sdk or cursor. The native omnigent claude and omnigent cursor wrappers aren't available on Windows.

Is there an Omnigent desktop app for Windows?

Yes. Omnigent's desktop docs list a Windows installer (.exe) next to the macOS and Linux builds.

Does Superset run on Windows?

Not yet. Superset's README lists Windows as "not yet available" and names macOS as the primary target.