Getting started

1. Your account

Sign in with Google. A new account accepts the terms first. Then add a passkey on your account page: Rebasely asks for it before sensitive actions such as creating an access token, adding an SSH key or making a repository public. The first passkey can be added within 10 minutes of signing in.

2. An organization and a repository

Every repository belongs to an organization, which can be just you. Create an organization, then a repository, from your home page. New repositories are private; an owner can make one public in its settings.

3. Sign git in

The Rebasely CLI is one file and needs Node.js 22.18 or later. It asks you to approve an access token in your browser and hands it to git's credential helper, so git push just works:

curl -fsSL https://rebasely.com/install | sh
rebasely auth login

The installer puts the CLI in ~/.rebasely (or the ~/.duragit an earlier install made) and the rebasely command on your PATH, with duragit as an alias; it is short, so read it first if you like. Run it again to update. On Windows, use WSL. rebasely auth status shows what is signed in; rebasely help lists every command.

Prefer not to install anything? Create an access token with the repo:write scope and paste it when git asks for a password. For SSH, add your public key in your SSH key settings, or let the CLI make and register one:

rebasely ssh setup

4. Push

From a repository you already have:

git remote add origin https://rebasely.com/<org>/<repo>.git
git push -u origin HEAD

Or start a new one:

mkdir app && cd app
git init -b main
echo "# app" > README.md
git add README.md && git commit -m "First commit"
git remote add origin https://rebasely.com/<org>/app.git
git push -u origin main

Over SSH the remote is git@ssh.rebasely.com:<org>/<repo>.git. Your repository's page shows these commands with its own name filled in, and the files, commits and branches once you have pushed. If a push is refused, Push errors says why.

5. What next

Actions

Add a workflow under .rebasely/workflows/ and push: jobs run on Cloudflare Sandboxes. The repository's Actions tab has a starter workflow to copy.

Live branches

Turn live on for a branch from the repository's Live tab, or create and mount one from your terminal, inside a clone of the repository. Every save syncs to everyone editing the branch, and Rebasely commits checkpoints as you go.

rebasely mount my-idea --create

Agents and MCP

An owner creates an agent under the organization's Agents settings and gives it its own token. Agents edit live branches and work in sandboxes through MCP: run rebasely mcp as a local MCP server, or point an MCP client at https://rebasely.com/mcp. rebasely agent init adds the Rebasely agent skill to a repository.

Live branches, sandboxes and agents covers all of this in detail, with the limits that apply during the beta.

Context for people and agents

Optionally, keep a knowledge base in .rebasely/kb/ and a map of the system in .rebasely/architecture/system.yaml. They show up as the repository's Knowledge and Architecture tabs, and agents read them over MCP before they change anything. The .rebasely folder explains the layout.