CloudAxis Coding is a cloud coding agent — part of the same AI cloud computer that runs your other agents. You describe a change in plain English; it clones your GitHub repository into an isolated cloud machine, makes the edit, runs your tests, and opens a pull request with proof it works: a live preview, screenshots, and test results. You approve the merge with one reply — pinned to the exact commit you reviewed.
You never open an editor. There is no IDE to babysit and no diff to run and trust. The output is a reviewable, proven pull request delivered to your CloudAxis inbox and, if you like, to WhatsApp. Nothing merges without you. It is the operator experience — you describe and approve; the agent does the fiddly part and shows its work.
How it works
- Connect a GitHub repository and describe the change — in the app, on WhatsApp, or by mentioning @cloudaxis in a GitHub comment
- CloudAxis builds it on an isolated cloud machine, runs your tests, and captures a live preview + screenshots
- It opens a pull request with the proof attached and tells you it is ready
- You approve the merge from your phone — pinned to exactly what you reviewed
Features
Proof-of-work pull requests
Every change ships with evidence, not a promise. For a web app the agent starts your dev server, opens the page in a real browser, and attaches a live preview, multi-viewport screenshots, and test results to the PR. You review what the change looks like and that it passes — before you merge.
Approve-to-merge from your phone
Ship by replying to a message. The merge is pinned to the exact commit you reviewed and requires a typed code, so a stray reply can never merge the wrong thing. Merging is always a human decision — CloudAxis never ships code without you.
Start a change any way you like
From the Coding panel in the app, from a WhatsApp message, or by mentioning @cloudaxis in a GitHub issue or pull-request comment. You can even describe the change by voice — send a voice note and it transcribes what you said. The same engine runs no matter how the request arrives.
Isolated, single-use machines
Each session gets its own sealed cloud computer, cloned from your repo with a short-lived, repo-scoped token — about an hour, not a standing key. When the task ends the machine is stopped and reaped. The durable record is the pull request on your own GitHub.
It closes the loop
If continuous integration fails, CloudAxis can pick the session back up, read the failing checks, and push a fix — a bounded number of times, not an infinite retry. A live timeline lets you watch each step, with a read-only code and diff browser.
Hardened before beta
We ran a full security and billing audit and fixed 22 issues before opening the beta — you are billed for exactly the model that ran, failures notify you, and high-risk requests are refused at the door. Read the write-up.
What works well today
Being a public beta, here is the honest picture. The full preview-and-screenshot proof is strongest for web apps — Node front ends (Next.js, Vite, and friends) and Python web apps like Django are the sweet spot. Backend services and libraries with no dev server are proven by their test suite instead of screenshots — still real evidence, just not a picture. A handful of toolchains (Go, Rust, Ruby, PHP) are not baked into the build machine yet and are on the roadmap. Bring a web app or a JS/Python repo and it will feel like magic; bring an exotic stack and you are helping us prioritize what to add next.
Your code runs in an isolated, single-use machine with a short-lived, repo-scoped GitHub token; the machine is reaped when the task ends. Untrusted repository content and comment triggers are screened, and high-risk requests are refused. We do not use your content to train third-party foundation models. See Security and Privacy.
Who it is for
Founders and small teams who own a codebase but do not want to context-switch into it for every small change. Agencies shipping client sites. Solo builders who want to move a task forward from their phone. If you can describe the change and read a preview, you can ship it — the agent handles the editor part, and you stay the one who says “ship it.”
Read more
How it works Proof-of-work PRs Approve-to-merge vs Cursor / Copilot / Devin The audit behind the beta