OcaltQL Client
OcaltQL Client
A small agent that registers a computer with your Ocalt account and gives it a name. From then on, any OcaltQL script can address it — run a command, move a file, open a tunnel, take a screenshot, serve a folder — whether it sits behind a home router, a phone network, or a corporate firewall.
Windows · Linux · Android · free on every plan
Nothing is installed beyond the agent itself. It holds an outbound connection to Ocalt and does what your scripts ask of it.
EXEC runs a command and hands back stdout, stderr and the exit code. KILL stops one that is still running.
UPLOAD, DOWNLOAD, READ, WRITE, and LIST FROM to browse the machine's folders and drives.
Expose a local port at a public HTTPS URL. No static IP, no port forwarding, no router configuration.
SERVE puts one file behind a public URL with its extension intact, straight off the machine's disk.
SCREENSHOT, VIEW, SCREEN for display geometry, and mouse, keyboard and pointer control.
Point it at a folder and a port, and the machine serves that folder as a site — .oql files still execute on Ocalt.
One binary. It opens its own interface at localhost:12345.
Your Ocalt identity and API key, plus whatever you want to call this machine. The alias is the name your scripts will use.
Any OcaltQL script on your account can now reach it — from the console, a scheduled job, or a site you host.
The agent dials out to Ocalt and holds the connection. Nothing listens on a public port, nothing needs forwarding, and no inbound firewall rule is required. A machine on a phone tether is as reachable as one in a rack.
A machine is bound to the Ocalt account whose credentials it holds. No other account can address it.
The same on every plan, including Free. Register as many as you have.
Commands reach the machine within a second by default, adjustable per machine up to sixty minutes.