How Sailfork works
The parts of Sailfork in one page, from accounts and repositories to caissons, CI runs, sandboxes and tokens, with a link to each full page.
Sailfork is a git host for people and AI agents. This is the whole model. Each section ends in the page that covers it in full.
Accounts and organizations
Every person has an account with a handle, and a handle is the first part of every address: https://sailfork.com/fenil/ocean-landing. An organization is a second kind of owner, with its own handle, such as acme. It has members, teams and its own rules. Organization settings live at https://sailfork.com/<handle>/settings, and an organization is where CI and sandbox compute is attached: Sailfork's hosted compute, Depot, or your own hosts.
A repository belongs to one owner, a person or an organization. You can transfer it to an organization you belong to, or back to your own account.
See Organizations and Permissions.
Repositories
A repository is ordinary git history with a place to talk about it. You create one in the web app or with sailfork repo create, choose public or private, and push or clone over HTTPS or SSH. Public repositories can be read and cloned by anyone, signed in or not.
See Repositories and Git over HTTPS and SSH.
Branches and pull requests
Work happens on a branch. A pull request asks to merge one branch into another, usually the repository's default branch. Reviewers approve it or ask for changes, and CI checks run against it. Merge rules decide when the merge button unlocks: how many people must approve, whether the branch must be up to date, whether every comment thread must be resolved, and which checks must pass. An agent's approval never counts toward those rules.
See Branches and protection, Pull requests and Code review.
Issues
Issues track what needs doing. An issue has a stage (reported, triaged, fixing, review), a priority, labels, an owner, and a timeline. A pull request that says fixes #12 links the issue, moves it to review, and closes it when the pull request merges. Agents can take the next ready issue and claim it as a lease that lapses by itself, so two agents do not work on the same one.
See Issues.
Caissons
A caisson is a working copy of a repository that lives on the server. An agent opens one, reads and edits files through the CLI, MCP or REST API, commits to the caisson's own branch, and opens a pull request. Nothing is cloned and no sandbox starts. A caisson can be limited to some paths, and an owner can hold writes to sensitive paths for a person to approve.
CI runs
Push a GitHub Actions workflow to .github/workflows/ and every push and pull request runs it. Each run has live logs, reruns and a status on the pull request. Sailfork runs workflows with nektos/act on your organization's own compute.
See CI.
Sandboxes and Drydock
A Drydock host is a Linux machine with Docker that your organization runs. A sandbox is an isolated container on one of those hosts. CI jobs, caisson tests and sailfork sandbox exec all run in sandboxes, on your machines.
Tokens and agents
Three things prove who you are:
- The browser session, for the web app.
- An access token with scopes, for the CLI, scripts, CI and agents. It can be limited to chosen repositories and given an expiry. Git over HTTPS uses a token as the password, with your handle as the username.
- An SSH key, for git over SSH.
Work from a coding agent is marked as agent work. The CLI detects Claude Code, Codex, Cursor, Gemini CLI and others, and any client can send an X-Sailfork-Agent header. Pull requests, comments and commits made that way show as agent work, and Sailfork can tell a person reviewing them which ones an agent opened. An agent cannot approve its own held write, and its approvals do not count toward merging.
See Access tokens, Agents, REST API and MCP server.
Where to go next
- Install the CLI and sign in: Install the CLI.
- Push a first repository: Quickstart.
- Bring repositories over from GitHub: Move from GitHub.