Feature guide · trusted LAN

Another computer, same tool surface.

Host the API from the Electron GUI or CLI, save the connection, and let a later agent route commands to the other computer's preferred headless desktop.

Behavior

GET /health reports readiness and headless preference. POST /api/execute accepts {"tool":"...","arguments":{}} and dispatches to the same tool functions as MCP. Upload and download use bounded base64 payloads. The MCP endpoint remains at /mcp.

Configuration

Start with uv run lowlevel-computer-use-mcp --http --host 0.0.0.0 --port 8765, or use Workspaces → Host the LAN API. Connect & save in Electron; the URL is local app state.

Failure modes

• Invalid or unreachable URLs fail without changing saved connections.
• Unknown tools and malformed arguments return JSON errors.
• Oversized file payloads are rejected at the per-call limit.

Security

No API key is used because the user explicitly chose trusted LAN operation. Any client that reaches the port can execute commands and transfer files with the server user's permissions. Bind privately, restrict Windows Firewall, and never forward the port publicly.

Verification

Health, tool execution, and file-transfer smoke tests cover the local route. A second-computer test must verify firewall scope and a complete connect/save/run cycle.

Suggested articles

Headless desktops · Electron manual client · Quiet processes