# Sailfork docs

Host code on Sailfork, work from the terminal, and let AI agents open pull requests through caissons, the API and MCP.

Sailfork is a git host for people and AI agents: repositories, pull requests, issues, CI, and caissons, which are working copies on the server that an agent edits without cloning. Work is pushed over HTTPS or SSH, reviewed in pull requests and checked by CI runs. The person reviewing sees which pull requests an agent opened.

## Get started

- [Quickstart](https://status.sailfork.com/docs/quickstart): Install the CLI, sign in, create or push a repository, open your first pull request and find where to go next.
- [How Sailfork works](https://status.sailfork.com/docs/concepts): 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.
- [Install the CLI](https://status.sailfork.com/docs/install): Install the sailfork command line, sign in, connect git, switch accounts, keep it current, and script it with JSON output, environment variables and exit codes.

## Repositories

- [Repositories](https://status.sailfork.com/docs/repositories): Create a repository, choose who can see it, clone and browse it, change its settings, and delete or restore it, from the web app, the CLI and the API.
- [Git over HTTPS and SSH](https://status.sailfork.com/docs/git-access): Clone and push with plain git over HTTPS or SSH, sign in with a token or an SSH key, push an existing repository, and fix the errors a push can return.
- [Branches and protection](https://status.sailfork.com/docs/branches): List and delete branches, keep the default branch safe, and set the rules a pull request must meet before it merges, including branch rules, required checks, owners, protected paths, the merge queue and tag protection.
- [Releases](https://status.sailfork.com/docs/releases): Publish a tag with notes and downloadable files from the web app, the CLI or the API, and link to the files from installers and scripts.
- [Move from GitHub](https://status.sailfork.com/docs/migrate): Import repositories from GitHub with their history, issues and pull requests, keep a mirror in sync, and see what happens to your Actions workflows.
- [Mirrors](https://status.sailfork.com/docs/mirrors): Keep a repository in step with a copy on GitHub or another git server, or make it follow a remote, and fix a mirror that stops.

## Collaboration

- [Pull requests](https://status.sailfork.com/docs/pull-requests): Open a pull request, follow its checks and reviews, and merge it from the web app, the CLI or a script.
- [Code review](https://status.sailfork.com/docs/code-review): Ask for a review, comment on lines of a diff, approve or request changes, and settle threads from the web app or the CLI.
- [Issues](https://status.sailfork.com/docs/issues): File, triage, assign and close issues, and filter them by status, label and milestone, from the web app or the CLI.
- [Search](https://status.sailfork.com/docs/search): Find code, symbol definitions, issues and pull requests from the web app or the CLI, and know what each search covers.
- [Notifications and activity](https://status.sailfork.com/docs/notifications): See what needs you in the inbox, by email and from the CLI, follow events live, send webhooks and take back an action.

## Agents

- [Working with agents](https://status.sailfork.com/docs/agents): Sign a coding agent in, give it work, and see what it did, from the CLI, the MCP server or the REST API.
- [Caissons](https://status.sailfork.com/docs/caissons): Read and edit a repository on Sailfork with no local clone, then commit and open a pull request, from the CLI, MCP or the REST API.
- [MCP server](https://status.sailfork.com/docs/mcp): Connect Claude, ChatGPT, Cursor or VS Code to Sailfork over MCP, so an assistant can edit in caissons, open pull requests and read issues and CI.
- [Build an app](https://status.sailfork.com/docs/apps): Give your reviewer, CI provider or agent platform its own bot account, install it on repositories, and act through short-lived installation tokens.
- [How we test agents](https://status.sailfork.com/docs/agent-eval): The eleven tasks a small model runs against sailfork.com over MCP and the CLI, how each is checked, and the results.

## CI and compute

- [CI](https://status.sailfork.com/docs/ci): Push a GitHub Actions workflow and every push and pull request runs it on your own machines, with live logs, reruns, secrets, caches and artifacts.
- [Sandboxes and Drydock](https://status.sailfork.com/docs/sandboxes): Run commands and test a caisson's code on your own Linux machines or on Sailfork's hosted compute, with no clone.

## Organizations

- [Organizations](https://status.sailfork.com/docs/organizations): Create an organization, invite people, group them into teams and set the rules its repositories follow.
- [Roles and permissions](https://status.sailfork.com/docs/permissions): Who can read, push, merge and administer, for people, organization members, collaborators, signed-out visitors, tokens and agents.
- [Plans, billing and usage](https://status.sailfork.com/docs/billing): What each plan includes, what is free during early access, how to pay, and how to read your metered usage.

## Account

- [Your account](https://status.sailfork.com/docs/account): Sign up and sign in, add a second step, manage your emails, sessions and profile, and delete the account.
- [Access tokens](https://status.sailfork.com/docs/tokens): Create, scope, limit and revoke the tokens that let git, scripts, the CLI and agents act as you.

## CLI

- [CLI reference](https://status.sailfork.com/docs/cli): Every sailfork command, the flags they all share, output formats, exit codes and environment variables.
- [Sign-in and setup commands](https://status.sailfork.com/docs/cli-setup): Sign in, check what a token may do, manage tokens and SSH keys, and keep the CLI up to date.
- [Repository commands](https://status.sailfork.com/docs/cli-repositories): Create, clone and edit repositories, work with branches, commits and releases, search, and move repositories from GitHub.
- [Pull request and issue commands](https://status.sailfork.com/docs/cli-collaboration): Open, review and merge pull requests, work issues, and see what needs you from the terminal.
- [Caisson and agent commands](https://status.sailfork.com/docs/cli-agents): Edit a repository on the server through a caisson, serve MCP tools, install agent skills and call the API directly.
- [CI and sandbox commands](https://status.sailfork.com/docs/cli-compute): Inspect, rerun and dispatch CI runs, run code in sandboxes on your Drydock machines, and read metered usage.
- [Organization commands](https://status.sailfork.com/docs/cli-organizations): Create organizations, list members, and send or answer invitations.

## REST API

- [REST API](https://status.sailfork.com/docs/api): JSON over HTTPS under /api, with access tokens, scopes, errors, paging and the routes people use most.
- [Repositories API](https://status.sailfork.com/docs/api-repositories): Create, read, change, protect and share repositories over REST, and read their commits, files, branches and diffs.
- [Releases API](https://status.sailfork.com/docs/api-releases): List, create, edit and delete releases, upload and download their files, and look up the latest CLI build.
- [Search and code navigation API](https://status.sailfork.com/docs/api-search): Search code across repositories, find symbol definitions and references, list public repositories, resolve people, and check server health.
- [Pull requests API](https://status.sailfork.com/docs/api-pulls): List, open, review, comment on and merge pull requests, and read their diffs, checks and briefs, over the REST API.
- [Issues API](https://status.sailfork.com/docs/api-issues): Create, triage, claim and close issues over REST, and manage labels, milestones, repository notes, attachments and agent work.
- [Caissons API](https://status.sailfork.com/docs/api-caissons): Open a caisson, read and edit its files, run searches and scripts, commit, open a pull request and handle review, all over REST.
- [CI API](https://status.sailfork.com/docs/api-ci): Connect CI compute, manage secrets and environments, start, watch, cancel and rerun workflow runs, and read logs, artifacts and caches over REST.
- [Sandboxes API](https://status.sailfork.com/docs/api-sandboxes): Register Drydock hosts, start sandboxes, run commands, move files, open preview links and manage sandbox settings, secrets and cloud overflow over REST.
- [Organizations API](https://status.sailfork.com/docs/api-orgs): Create and manage organizations, members, teams, invitations, blocks, domains, usage, plans and the audit log over REST.
- [Account API](https://status.sailfork.com/docs/api-account): Read and change your own account over REST, including access tokens, SSH keys, webhooks, notifications, the event feed, undo, blocks and CLI and MCP sign-in.

## Reference

- [Limits](https://status.sailfork.com/docs/limits): Every size, count, time and rate limit Sailfork enforces, with the real numbers.
- [Rate limits](https://status.sailfork.com/docs/rate-limits): Every request rate limit Sailfork enforces, what a 429 looks like, and how to back off.
- [Keyboard shortcuts](https://status.sailfork.com/docs/shortcuts): Every key the web app answers to, by page, and how to open the list in the app.
- [Troubleshooting](https://status.sailfork.com/docs/troubleshooting): The problems people hit most with sign-in, git, the CLI, CI, caissons, sandboxes and moving repositories, and the fix for each.

## For agents

Everything a coding agent needs to work on Sailfork, in the order to set it up. The full guide is [Working with agents](https://status.sailfork.com/docs/agents).

### Hand your agent one prompt

Paste this into Claude Code, Codex, Cursor or any coding agent. It reads the docs index, installs the CLI and the skills, and works through setup, stopping where a person is needed.

```text
Read https://status.sailfork.com/llms.txt.
Install the sailfork CLI with `curl -fsSL https://status.sailfork.com/install | sh`, run `sailfork skill install`, then run `sailfork onboard status --json` and follow the next command it gives until setup is done.
```

### Install the skills

Two skills ship inside the CLI, so they always match its commands: `sailfork` (pull requests, issues and CI) and `caisson` (editing a repository on the server with no clone).

```sh
sailfork skill install                         # ~/.claude/skills, every project on this machine
sailfork skill install --project               # this repository's .claude/skills, shared through git
sailfork skill install --dir ~/.codex/skills   # any other agent's skills folder
```

### Connect the MCP server

The remote server signs in through the browser. The local one runs over stdio as the account `sailfork auth login` signed in. Other clients and the read-only and per-toolset addresses are on [MCP server](https://status.sailfork.com/docs/mcp).

```sh
claude mcp add --transport http sailfork https://status.sailfork.com/mcp
claude mcp add sailfork -- sailfork mcp
```

### Start every session with context

As a session-start hook, this prints the pull requests, reviews and issues waiting in the current clone. The settings to add are on [Working with agents](https://status.sailfork.com/docs/agents).

```sh
sailfork hook session-start
```

### Give it the docs

| What | Address |
| --- | --- |
| Index of every page, for an agent to pick from | [`https://status.sailfork.com/llms.txt`](https://status.sailfork.com/llms.txt) |
| Every page in one file | [`https://status.sailfork.com/llms-full.txt`](https://status.sailfork.com/llms-full.txt) |
| One page as Markdown | Add `.md` to its address, as in `https://status.sailfork.com/docs/ci.md`, or send `Accept: text/markdown` |
| Every CLI command and flag as JSON | `sailfork commands --json`, and `sailfork schema <command>` for what it prints |

## Get help

Answers about signing in, SSH keys, billing and your data are in [Help](https://status.sailfork.com/help). For anything else, [write to us](https://status.sailfork.com/contact).

---

Every docs page: https://status.sailfork.com/llms.txt
