Rebasely Beta: data may be purged
View as Markdown

Rebasely docs

Rebasely is git hosting for people and agents working together. Every repository is its own Durable Object on Cloudflare, with pull requests, Actions, live branches, sandboxes and an MCP server. This guide covers all of it, from the first push to agents that ask for approval.

Install the CLI and sign git in
curl -fsSL https://rebasely.com/install | sh
rebasely auth login

Start here

From an account to your first push, and the questions people ask first.

  1. Getting startedSign up, install the Rebasely CLI, sign git in with an access token, and push your first commit to Rebasely.
  2. FAQShort answers about Rebasely: what it is, what it costs, how it differs from other git hosts, and what is still in beta.

Work with people and agents

Review, edit together, try things in a sandbox, and let tools work under their own name.

  1. Pull requestsOpen, review and merge pull requests on Rebasely from the web, the CLI, the API or an agent, with the Visual diff of the architecture, protected branches and checks.
  2. Live branches and mountEdit one branch together with people and agents: mount it as a folder with rebasely mount, and Rebasely commits checkpoints as you go.
  3. SandboxesGive each task its own hidden branch: create a sandbox from any commit, run its checks and merge it back with one command.
  4. Agents and approvalsGive each automated tool its own identity, token and limits in an organization, and let it ask an owner to approve what only an owner may do.
  5. SSH (turned off)Rebasely no longer offers git over SSH. How to clone and push over HTTPS instead, and switch an existing clone.

Understand how it fits together

What happens on a push, and the folder that describes your system.

  1. How Rebasely worksWhat happens when you push to Rebasely: the Worker, the repository's own Durable Object, and where your objects are stored.
  2. The .rebasely folderKeep a knowledge base, an architecture map, dataflows and Actions workflows in a .rebasely folder, so people and agents work from the same context as the code.

Run CI

Workflows in .rebasely/workflows, each job in its own sandbox.

  1. ActionsRun CI on every push and pull request with Rebasely Actions: workflows in .rebasely/workflows, jobs on Cloudflare Sandboxes, logs, secrets and checks.
  2. Workflow syntaxThe keys of a Rebasely Actions workflow file: triggers, jobs, steps, expressions, built-in actions and the variables a step sees.

Look something up

Commands, endpoints, tools, limits and errors.

  1. CLI referenceEvery rebasely command and flag, generated from the CLI's own help: pull requests, sandboxes, Actions runs, mounts, agents and sign-in.
  2. REST APIThe Rebasely REST API under /api/v1: authentication with access tokens, errors, and the endpoints for repositories, pull requests, sandboxes, live branches and Actions.
  3. MCP serverConnect agents to Rebasely over the Model Context Protocol, at /mcp or through rebasely mcp, and the tools they get.
  4. LimitsEvery limit Rebasely enforces in one place: repository size, pushes, pull requests, live edits, sandboxes, agents and Actions.
  5. Push errorsWhat each error from a push to Rebasely means and how to fix it, from size limits to protected branches.
  6. Git LFSRebasely does not store Git LFS objects yet. What to do with large files until it does.

Keep your account safe

Signing in, confirming it's you, and access tokens.

  1. Sign-in and passkeysHow you sign in to Rebasely with Google, why passkeys are optional, and how Rebasely asks you to confirm it's you before sensitive actions.
  2. Access tokensPersonal and agent access tokens: their scopes, expiry, tokens for all your organizations, where git and the CLI keep them, and what happens when one leaks into a push.

For tools and agents: /llms.txt lists every page, /llms-full.txt has all of them in one file, and each page is Markdown at its address plus .md. Coding agents also get the Rebasely agent skill.