Helmsly questions
Helmsly is live today. These are the questions people ask about running it.
What is Helmsly?
A control plane for AI agent fleets, run from one console. It runs Claude, Codex, Gemini and any agent CLI side by side, on a machine you choose, and it is reachable from anywhere through the Slobal relay.
Which models and agent tools can I run in it?
- Agents
- Claude, Codex, Gemini and any agent CLI, side by side in one console
- Models
- A subscription you already hold, or other models you bring
- Keys
- BYO-LLM: you supply your own model keys
- Charged by Slobal
- Nothing per token. What the model provider charges you is between you and them
How do I install it?
On your own machine, in one command or one download. Local use needs no account and no licence.
- Windows
winget install Slobal.Helmsly, or the installer from the install page- macOS and Linux
- A disk image on macOS, an AppImage or a deb on Linux, each with its published checksum
- Then
- The hub opens at
127.0.0.1:4319on that machine. Pairing is a later step, and only if you want remote access
Every platform, the current version and its checksums are on the Install Helmsly page.
Where does my data live?
On your machine.
- Your machine
- Sessions, memory and files stay there, and Slobal does not receive the content your instance works with
- Hosting by Slobal
- Managed VPS is in the pipeline and not for sale
The short list of what Slobal holds is in the privacy policy.
Can I reach my instance when I am away from that machine?
Yes. Remote access runs through the Slobal relay to your own instance, so the same panel opens on any screen.
- Workspace address
{workspace}.on.slobal.com- Personal account
- Its own paired hub, reached the same way, at
slobal.com/helmsly - In transit
- The relay carries that traffic as a pipe, addressed to your instance. Your files are not copied to us on the way through
What do I see when my install is off?
The console, and an honest account of what it cannot reach.
- The page
- Opens either way. The relay serves it; your instance answers the data
- Four states
- Live, starting, last seen at a stated time, or not connected. A panel says which of the four it is in
- Never guessed
- A container that is waking says starting, never disconnected, and any figure not fetched this request carries the time it was true
- Controls
- Anything that would change something is disabled, with the reason written on the control rather than hidden
Can I stop an agent before it does something risky?
Yes. Nothing risky runs until you approve it.
- Approvals
- Work that needs a person waits here
- Built-in browser
- The pages an agent is working through, live. You can take over at any time
- The record
- The decision, and the record of it, sit with the rest of your instance's own data
Is anything removed before a model sees it?
Helmsly carries a data protection layer that scrubs content inside your own instance, before any model sees it. What it removes never leaves that instance: it does not travel to the model provider you have connected, and Slobal does not read it either.
Who looks after the machine Helmsly runs on?
You do. Three things are yours:
- The machine
- Yours, including its backups
- Model services
- The third-party model services you connect, and their terms
- Lawful use
- What you and your agents do with it
The terms of service set this out in full.