Set up Omnigent with Localtonet on Windows

Install Omnigent on Windows, verify its local web UI, then expose it through a Localtonet HTTP tunnel.

Prerequisites

A current supported uv installation.
Permission to install user-level tools and network access to retrieve packages.
The Localtonet client installed on the same Windows device for remote access.

Windows limitation: Omnigent runs natively on Windows in degraded mode. The server, web UI, and documented SDK-based harnesses are supported, but some POSIX-dependent workflows require Linux, macOS, or WSL. Do not run the POSIX install_oss.sh bootstrap in native PowerShell.

Install and verify Omnigent

Open PowerShell and verify uv:
```
uv --version
```
Install Omnigent with Python 3.12:
```
uv tool install --python 3.12 omnigent
```
If Windows cannot find omnigent after installation, close the terminal and open a new one.
Start Omnigent and keep the terminal open:
```
omnigent
```
On the same Windows device, open:
```
http://localhost:6767
```
Confirm that the Omnigent interface loads and still works after a refresh. You can also test the endpoint with:
```
Invoke-WebRequest http://localhost:6767
```

Create the Localtonet tunnel

Run and authenticate the Localtonet client on the Windows device hosting Omnigent, then select that connected device in the dashboard.
Select an available relay server or region.
Create an HTTP tunnel targeting IP address 127.0.0.1 and port 6767. See the Localtonet HTTP tunnel documentation for current dashboard details.
Use the Start button and wait until the tunnel is running.
Open the assigned public HTTPS URL from another network or device and confirm that the Omnigent interface loads.

Security: Verify Omnigent authentication, authorization, session sharing, agent policies, credentials, and tool permissions before sharing the public URL. Stop the tunnel when remote access is not needed.

Troubleshooting

uv or omnigent is not recognized: Open a fresh terminal and retry. Confirm you are using the Windows account under which the tool was installed.
The local page does not load: Confirm omnigent is still running and test the exact address http://localhost:6767. Resolve local startup errors before checking the tunnel.
The local UI works but the public URL does not: Confirm the Localtonet device is connected, the HTTP tunnel targets 127.0.0.1:6767, and the tunnel was started.
Remote access stopped: Omnigent, the Localtonet client, and the tunnel must all remain running.
Port 6767 is occupied: Stop duplicate Omnigent instances and determine whether another application is using the port. Do not guess an undocumented port override.