Feature guide · trusted LAN
Another computer, same compatibility tool surface.
Use the Cheap Version for ordinary local calls. Host the retired HTTP compatibility API only when an existing client explicitly requires a remote connection.
Behavior
Run uv run lowlevel-computer-use-mcp --http --legacy-http --host 0.0.0.0 --port 8765 only for an explicit compatibility session. GET /health reports readiness, POST /api/execute dispatches a registered tool, and the MCP endpoint remains at /mcp.
Configuration
The GUI installer never starts this transport or installs it at logon. The Electron Workspaces tab can start and stop it deliberately for a saved trusted-LAN connection; local Tool runner calls use the Cheap Version.
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.
install-startuprefuses unless--legacy-httpis explicitly supplied.
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 compatibility route. A second-computer test must verify firewall scope and a complete connect/save/run cycle.
Suggested articles
Headless desktops · Electron manual client · Cheap Version · Quiet processes