⌘K
DocsGuides

Repositories

Every project's source code, its history, and how work flows through it.

Managed for you

You never provision or configure a repository — every project comes with a private, managed one from the moment it's created. It holds your project's complete source code and the full history of every change ever made, by you, your teammates, and your agents. Any earlier version can be revisited or restored.

Branches mirror your environments

The repository is organized the way software teams organize theirs: everyone works on their own branch. Spaceboy's agents build on the shared sandbox branch, each teammate's sandbox and development environment gets a branch of its own, and main is the project's shared line of truth — the code production serves. Spaceboy creates and manages all of these branches for you.

How environments coordinate a team

How work reaches main

Work lands on main deliberately, through two doors. Setup checkpoints merge to main when the agent completes them — that's what you pull into your own sandbox with Sync with main. Production releases go further: they open a pull request from your branch into main, the repository's release checks run against it, and only a green merge deploys. The code serving your users is never edited directly.

Release checks

Using your own GitHub

On the Team plan and above you can connect your organization's GitHub: new projects' repositories are then created inside your GitHub organization, under your ownership and policies, while Spaceboy keeps operating them the same way. And if your code already lives in a repository somewhere, migration turns it into a Spaceboy project without touching the original.

GitHub integrationMigrate an existing repo