Live branches and rebasely mount
Edit one branch together with other people and with agents. Every save reaches everyone in a fraction of a second, Rebasely commits checkpoints as you go, and git keeps working the whole time.
Live branches
A live branch is an ordinary branch that several people and agents edit at once. People edit through rebasely mount, which syncs a real directory you open in any editor, and agents through the API or the MCP tools. The unit is a saved range of lines, not keystrokes.
Turning live on
A writer turns live on from the repository's Live page, with rebasely mount <org>/<repo> <branch> --create, or through the API (POST /api/v1/repos/<org>/<repo>/live with {"ref": "<branch>"}). Turning it off writes a final checkpoint and disconnects everyone.
The default branch can be live only after an owner allows it in the repository's settings, under Live and sandboxes. Branches protected with required checks cannot be live.
Checkpoints are real commits
Rebasely commits the live state of the branch as a checkpoint after 10 seconds without edits, after 200 edits, and at least every 2 minutes while edits keep coming. A checkpoint is a normal commit on the branch, authored by whoever made most of its edits, with the others as co-authors. Clones and fetches see checkpoints only, so they always get a consistent tree.
Pushes made by checkpoints do not start workflows unless a workflow asks for them with on: push: {checkpoints: true}, and then at most once every 5 minutes.
Pushing to a live branch
You can still push with git. Rebasely first writes a checkpoint of any pending edits, then accepts your push if it builds on that checkpoint, and sends your changes to everyone connected. If live edits landed after your last fetch, git says fetch first (or live branch moved: fetch first): pull, then push again. Force-pushing or deleting a live branch is refused until live is turned off.
When two edits meet
Each edit names the version of the file it was made against. An edit made against an older version is moved past the newer changes when they touch other lines. When two edits touch the same line, the later one is refused with the current lines, and the sender reads again and retries. rebasely mount does this for you: it merges cleanly when it can, and otherwise keeps your version next to the file as a conflict copy.
Changes to other kinds of files (images, archives) are last writer wins. Paths under .git, .gitmodules, .gitattributes, symlinks and paths matching the repository's ignored patterns are never edited live.
Watching
Members of the organization see each live branch on the repository's Live page: who is connected, which files are changing, the recent changes and the latest checkpoint. On a public repository, anyone signed in can watch, read-only. People who are not signed in see checkpoints through git and the code page, but not live edits.
rebasely mount
Mount a live branch to edit it in any editor. The sync daemon watches the directory, sends each save as a change and writes other people's changes into your files.
Install the CLI and sign in
See Getting started.
rebasely auth loginasks forlive:readandlive:writeby default.Mount the branch
From any directory, name the repository and the branch. Mount an existing live branch, or create one from the default branch and turn live on:
Shellrebasely mount team/app feature/login ~/code/app-feature-login rebasely mount team/app my-idea --createWithout a path the mount is linked at
./<repo>-<branch>, here./app-my-idea. Inside a clone of the repository you can leave outteam/app;--repo team/appworks too. The Live page of each branch shows its command, ready to copy.Edit and save
Open the folder in your editor. Every save is sent; other people's saves appear in your files.
git diff origin/<branch>shows what is not in a checkpoint yet.Stop
Ctrl-Cstops a foreground mount and keeps it;rebasely unmount <branch>stops syncing and removes it.
rebasely mount team/app feature/login ~/code/app # sync in the foreground; Ctrl-C stops it, the mount stays
rebasely mount team/app feature/login --daemon # run the daemon in the background
rebasely mount team/app my-idea --create # create the branch from the default branch and turn live on
rebasely mount team/app feature/login --no-link # keep the mount in ~/.rebasely only, with no link
rebasely mounts # every mount and its state
rebasely unmount feature/login # stop syncing and remove the mount
rebasely mount gc # remove stale mounts that have nothing unsent- Every mount lives under
~/.rebasely(or$REBASELY_HOME; an existing~/.duragitkeeps being used): one shared object store per repository and one git worktree per branch, so a second branch of the same repository mounts without a fresh clone. The path you give (or./<repo>-<branch>, next to the clone when you run it inside one) is a symlink to the mount. - Run outside a clone without a repository,
rebasely mountprints the command to run instead, with the repository filled in when the path or the directory names one it can find. --adopttakes an existing clone at that path: its uncommitted changes are sent as edits, and the clone is moved aside, never deleted.- Offline, saves wait in a queue and are sent when the connection comes back. When your change and someone else's touch the same lines, the file gets their version and yours is kept as
<file>.duragit-conflict-<date-time>, with a notice in the terminal. A local edit is never dropped silently. - More than 200 files changed within 2 seconds (a checkout, a formatter) pause sending and ask first;
--burst sendor--burst holdanswers in advance. - Ignored:
.git, whatever.gitignoreexcludes, the repository's ignored patterns and editor temporary files. - The daemon keeps
origin/<branch>at the latest checkpoint. It never moves your local branch or the index. rebasely unmountkeeps a mount with unsent edits until they are delivered;--discarddrops them.
The credential is REBASELY_TOKEN, or the token rebasely auth login stored for git.
Limits
Live branches, sandboxes and agents are free within these limits during the beta. An edit past a limit is refused with a reason and, where waiting helps, a time to retry.
| Limit | Value |
|---|---|
| Edits per connection | 20 a second, bursts of up to 100 |
| Edits per branch | 50 a second from everyone together |
| Connections per branch | 100, of which 20 may write |
| Open live sessions | 10 per person or agent |
| One edit | at most 1,000 lines; text files up to 1 MiB, other files up to 10 MiB |
| Live branches | 20 per repository, 100 per organization (20 until an owner is verified); live ends after 7 days without edits |
| Edits waiting for a checkpoint | 50,000; edits pause until the next checkpoint lands |
| Checkpoints | at most one per 10 seconds per branch, 360 an hour and 4,000 a day per repository |
| Sandboxes | 20 per person or agent per repository, 200 per repository, 1,000 per organization (200 until an owner is verified) |
| Agents | 20 active per organization (5 until an owner is verified, 100 on Team); a person creates at most 10 a day |
| Live edits a month | 10,000,000 per organization (2,000,000 until an owner is verified, 20,000,000 on Pro); a checkpoint counts as 40 |
Organizations without a verified owner or a paid plan also share a monthly amount of live edits, and a number of live edits a second, with each other. When the month's amount is used up, their live edits are refused until the month ends; at the rate, for a few seconds. Reading, git and checkpoints keep working. Your organization's numbers for this month are on its Trust and limits page. All of Rebasely's limits are on one page.
Sandboxes
A sandbox is a hidden branch for one task, refs/sandbox/<owner>/<name>, created in milliseconds and merged back with one command. A sandbox can be live too. Sandboxes has the whole flow.
Agents
An agent is an automated tool with its own identity, dga_ tokens and limits in an organization, and it can ask an owner to approve what only an owner may do. See Agents and approvals.
Approvals are on that page too.
MCP
Agents edit live branches with the live.* tools: run rebasely mcp, or point an MCP client at https://rebasely.com/mcp with Authorization: Bearer dga_.... The MCP server lists every tool.