Without Ondago Work paused
3 hrs
of nothing happening
You close the lid mid-task. The session waits exactly where you left it, and tomorrow starts by rebuilding the context you already had.
Session Continuity for Coding Agents
Stop babysitting
your agents.
Close your laptop without killing the work. Ondago moves your live coding session to the cloud, so your agent keeps going even when your computer is off.
Works with Claude Code, OpenCode and Codex · private secure cloud · no restart, no re-reading the problem.
One session, four steps
Your agents shouldn’t be tied to one machine
Coding-agent sessions are getting longer and more capable. But the session is still anchored to the machine where it started. Step into a meeting, close your laptop or leave your desk, and either the work stops — or you stay glued to your machine.
1
You wait at your deskTwenty minutes into the work you have somewhere to be, so you sit and watch a process that does not need you.
2
You lose the workClose the lid and the agent stops mid-task. You come back to a half-finished branch and start the context over.
3
It sits blockedThe agent hits a question after ten minutes, then idles for the next fifty because nobody was there to answer it.
And the work keeps getting longer
Agent sessions are getting longer.
Coding agents have moved past one-shot prompts. They plan, build, run the tests, read the results, fix what failed, and loop again. Each loop produces better work, and the session takes hours.
01Plan the changeThink
02Write and update codeBuild
03Run tests and inspect resultsCheck
04Fix what failedImprove
↻ Repeat until the work is ready
The solution
One session. Continuous execution.
Give your agents uninterrupted time to complete
the work you asked them to.
With Ondago Work complete
41m
of work you did not wait for
The same work continues in the cloud, reaches you once for an approval, and is finished and merged by the time you sit back down.
Keep the work moving
Meetings, commutes and closed laptops stop being reasons for stopped work.
Know when to step in
See the moment an agent needs a decision, and answer from the device already in your hand.
Move the whole session
Context, instructions, memory and the working tree travel together, not just the diff the agent produced.
How it works
Keep the session. Change the machine.
-
Step 01
Start locally
Start your coding agent on your laptop, in the tools you already use. Work on the task as you normally would.
-
Step 02
Continue in Cloud
Run
ondago liftto move your live session to Ondago Cloud. The conversation, instructions, memory, working tree and uncommitted changes move together. Close your laptop and your agent keeps going. -
Step 03
Step in from anywhere
When your agent needs a decision, answer from your phone or browser. Follow progress, approve actions and send new instructions while the session keeps running in the cloud.
-
Step 04
Continue locally
Run
ondago pullto bring the same session and its latest changes back to your laptop. Pick up where the agent is now, with the conversation and context intact.
Same session. New environment.
$ ondago lift
› capturing session state…
› context 128k · memory · 12 changed files
› continuing in Ondago Cloud · laptop can go offline
$ ondago pull
✓ session restored · 41m of work merged locally
The agent never restarts and never re-reads the problem. It resumes on the exact step it was on.
From your pocket
Command the work from anywhere.
A blocked agent becomes a notification instead of an hour of dead time. Approve, redirect or extend it in a few taps, then read the summary when it finishes.
- Live progress: files touched, tests run, the step it is on right now.
- Unblock the agent the moment it asks, instead of an hour after it asked.
- Approve sensitive actions explicitly, never by default.
- Queue the next prompt before you are back at your desk.
Security posture
Your code stays yours.
The session is sealed on your machine before it travels. What the service holds is ciphertext, which is a property of the design rather than a promise about our behaviour.
Sealed on your machine
Your session is encrypted before it leaves. We store ciphertext and hold no key that opens it, so there is no server-side search, preview or summary. Session lists decrypt in your own client.
Isolated environments
Each run gets a private environment of its own, destroyed when the session ends. It never holds the key to your account.
Scoped credentials
Provider keys are injected for one run and never persisted. Sensitive actions wait for your explicit approval instead of assuming it.
In plain English
Questions you may already have.
Do I have to move all my work to the cloud?
No. Ondago moves one running session at a time. Keep your normal local workflow and hand off only the work that needs to continue without your laptop.
Do I need to restart the task?
No — that is the point. The conversation, working tree and uncommitted changes move together, so the agent never restarts and never re-reads the problem.
What happens when the agent needs me?
You get a notification on your phone with the exact question or action awaiting approval. You answer in a few taps and the work continues immediately.
Can I bring the session back to my laptop?
Yes. Run ondago pull to bring back the full session and the latest changes, then continue in your normal local setup without losing context.
Where does the session actually run?
In a private cloud environment created for that run and destroyed when it ends. It is sealed to keys your machine holds, and it never holds the key to your account. See security posture.
Which agents does it work with?
Claude Code, Codex and OpenCode to start, with more coming as part of early access.
Is this only for technical teams?
The people running the agent are, but the outcome is not: less paid time spent waiting, more work finished, and visibility into work in progress for everyone who depends on it.