Docs

Sign in, create an organization and a repository, sign git in and push your first code.

Propose a branch or a sandbox, review it line by line, run checks, and merge it on the server by the base branch's rules: approvals, required checks and protection.

Edit a branch together with people and agents, give each task a hidden branch, and let tools work under their own name with rebasely mount and MCP.

A knowledge base and an architecture map next to the code, shown as the Knowledge and Architecture tabs, read by agents over MCP and kept honest by rebasely kb check and rebasely arch check.

Keys, host key fingerprints, the ssh settings Rebasely recommends and why a connection is refused.

What each refusal of a push means and what to do about it.

Why Rebasely does not store LFS objects yet, and how to push a repository that uses them.

The instructions rebasely agent init adds to a repository for coding agents: one sandbox and one worktree per task.