Heliograph runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 3 Oct 2026.
Run commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled.
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
fi, serr := os.Stat(filepath.Join(dir, name))
result = subprocess.run(
env = dict(os.environ)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Heliograph
same job, measured the same wayRun commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled.
Run your coding agent's commands on machines you own: a sandboxed job slot, not an SSH login.
Run commands and manage files on your own machines. Needs a LetKite account; OAuth sign-in.
Run commands on your remote test machines over SSH without the agent ever seeing a secret.
Extract a repo's contribution gates into machine-readable contribution-gates.json.
Give your AI hands on every computer you own. One chat, all your machines — even from your phone.
Code changes and unit tests by local MLX models, behind a gate a machine can run.
Group your AI's changes into focused commit candidates; nothing lands until you approve.
Heliograph — questions
Answers built from our own checks of this server.