Skip to main content
This page only matters if you’re having Claude build software for you. If you’re not, feel free to skip straight to agents on a schedule.
If Claude is writing code, your project usually lives in GitHub — think of it as Google Drive for code, with a built-in history of every change. You don’t need to master it; you just need to know the safe way to let Claude work there.

​
The one safe habit

Tell Claude to never change the “live” version directly — always make changes in a separate copy first, and let you look before it goes live. In GitHub terms that’s “work on a branch and open a pull request,” but you can just say it in plain English:
“Make this change in a separate copy and show me before anything goes live.”
This way nothing reaches your real project until you’ve okayed it. You stay the final approver.

​
Why this matters to you

It’s the difference between “Claude quietly changed my live site and I didn’t notice” and “Claude proposed a change, I looked, I approved it.” The second one is how you sleep at night.

​
How Orbit helps

A code change might take a few sessions to finish. Without shared memory, each session forgets why the earlier one made its choices. With Orbit:
  • The reasoning behind each change is saved to your Vault, so later sessions don’t undo or contradict earlier ones.
  • A decision like “we always do it this way” is followed by every session that touches the project.
So even longer build projects stay consistent instead of drifting.

Next: agents on a schedule

The fun part — Claude that works while you sleep.