# Sailfork > Sailfork hosts your repositories, reviews, issues and CI, and lets your agents do real work on them from the server. Every agent change is labeled, follows your rules, and can be undone. A caisson is an agent's own branch and its unsaved edits, kept on Sailfork and edited through the API with no clone. ## Docs Each page is Markdown at its address plus `.md`, or with `Accept: text/markdown`. To set an agent up in one step, give it this: Read https://sailfork.com/llms.txt. Install the sailfork CLI with `curl -fsSL https://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. ### Get started - [Sailfork docs](https://sailfork.com/docs/index.md): Host code on Sailfork, work from the terminal, and let AI agents open pull requests through caissons, the API and MCP. - [Quickstart](https://sailfork.com/docs/quickstart.md): 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://sailfork.com/docs/concepts.md): 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://sailfork.com/docs/install.md): 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://sailfork.com/docs/repositories.md): 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://sailfork.com/docs/git-access.md): 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://sailfork.com/docs/branches.md): 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://sailfork.com/docs/releases.md): 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://sailfork.com/docs/migrate.md): 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://sailfork.com/docs/mirrors.md): 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://sailfork.com/docs/pull-requests.md): Open a pull request, follow its checks and reviews, and merge it from the web app, the CLI or a script. - [Code review](https://sailfork.com/docs/code-review.md): 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://sailfork.com/docs/issues.md): File, triage, assign and close issues, and filter them by status, label and milestone, from the web app or the CLI. - [Search](https://sailfork.com/docs/search.md): 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://sailfork.com/docs/notifications.md): 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://sailfork.com/docs/agents.md): 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://sailfork.com/docs/caissons.md): 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://sailfork.com/docs/mcp.md): 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://sailfork.com/docs/apps.md): 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://sailfork.com/docs/agent-eval.md): 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://sailfork.com/docs/ci.md): 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://sailfork.com/docs/sandboxes.md): 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://sailfork.com/docs/organizations.md): Create an organization, invite people, group them into teams and set the rules its repositories follow. - [Roles and permissions](https://sailfork.com/docs/permissions.md): Who can read, push, merge and administer, for people, organization members, collaborators, signed-out visitors, tokens and agents. - [Plans, billing and usage](https://sailfork.com/docs/billing.md): What each plan includes, what is free during early access, how to pay, and how to read your metered usage. ### Account - [Your account](https://sailfork.com/docs/account.md): Sign up and sign in, add a second step, manage your emails, sessions and profile, and delete the account. - [Access tokens](https://sailfork.com/docs/tokens.md): Create, scope, limit and revoke the tokens that let git, scripts, the CLI and agents act as you. ### CLI - [CLI reference](https://sailfork.com/docs/cli.md): Every sailfork command, the flags they all share, output formats, exit codes and environment variables. - [Sign-in and setup commands](https://sailfork.com/docs/cli-setup.md): Sign in, check what a token may do, manage tokens and SSH keys, and keep the CLI up to date. - [Repository commands](https://sailfork.com/docs/cli-repositories.md): Create, clone and edit repositories, work with branches, commits and releases, search, and move repositories from GitHub. - [Pull request and issue commands](https://sailfork.com/docs/cli-collaboration.md): Open, review and merge pull requests, work issues, and see what needs you from the terminal. - [Caisson and agent commands](https://sailfork.com/docs/cli-agents.md): 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://sailfork.com/docs/cli-compute.md): Inspect, rerun and dispatch CI runs, run code in sandboxes on your Drydock machines, and read metered usage. - [Organization commands](https://sailfork.com/docs/cli-organizations.md): Create organizations, list members, and send or answer invitations. ### REST API - [REST API](https://sailfork.com/docs/api.md): JSON over HTTPS under /api, with access tokens, scopes, errors, paging and the routes people use most. - [Repositories API](https://sailfork.com/docs/api-repositories.md): Create, read, change, protect and share repositories over REST, and read their commits, files, branches and diffs. - [Releases API](https://sailfork.com/docs/api-releases.md): List, create, edit and delete releases, upload and download their files, and look up the latest CLI build. - [Search and code navigation API](https://sailfork.com/docs/api-search.md): Search code across repositories, find symbol definitions and references, list public repositories, resolve people, and check server health. - [Pull requests API](https://sailfork.com/docs/api-pulls.md): List, open, review, comment on and merge pull requests, and read their diffs, checks and briefs, over the REST API. - [Issues API](https://sailfork.com/docs/api-issues.md): Create, triage, claim and close issues over REST, and manage labels, milestones, repository notes, attachments and agent work. - [Caissons API](https://sailfork.com/docs/api-caissons.md): 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://sailfork.com/docs/api-ci.md): 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://sailfork.com/docs/api-sandboxes.md): 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://sailfork.com/docs/api-orgs.md): Create and manage organizations, members, teams, invitations, blocks, domains, usage, plans and the audit log over REST. - [Account API](https://sailfork.com/docs/api-account.md): 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://sailfork.com/docs/limits.md): Every size, count, time and rate limit Sailfork enforces, with the real numbers. - [Rate limits](https://sailfork.com/docs/rate-limits.md): Every request rate limit Sailfork enforces, what a 429 looks like, and how to back off. - [Keyboard shortcuts](https://sailfork.com/docs/shortcuts.md): Every key the web app answers to, by page, and how to open the list in the app. - [Troubleshooting](https://sailfork.com/docs/troubleshooting.md): The problems people hit most with sign-in, git, the CLI, CI, caissons, sandboxes and moving repositories, and the fix for each. Every page in one file: https://sailfork.com/llms-full.txt ## Command line - [Install](https://sailfork.com/install): `curl -fsSL https://sailfork.com/install | sh` puts one binary in ~/.local/bin after checking its SHA-256 - [CLI guide](https://sailfork.com/cli.md): Markdown version of https://sailfork.com/cli; sign in with `sailfork auth login`, then `sailfork repo`, `pr`, `issue`, `ci`, `caisson`; run `sailfork --help` for all commands - Run a caisson's tests: `sailfork caisson test --org -- ` (MCP: `caisson_test`) runs the command on the caisson's code in a throwaway sandbox and exits with the command's own code (124 on timeout). It needs a Drydock host: an org owner runs `sailfork sandbox host add --org `, then on a Linux machine with Docker `curl -fsSL https://sailfork.com/install/drydock | sh` and `sudo drydockd install --server https://sailfork.com --token `, and `sailfork sandbox host list --org ` shows it online - Agents: run one `sailfork` command per call, with `-R owner/repo` instead of `cd` and `--jq` instead of pipes or `$(...)`, so an allowlist of `sailfork` commands is enough - Discover the CLI as data: `sailfork commands --json` lists every command with its flags (types, defaults, choices, env), examples and whether it changes anything; `sailfork schema ` prints the JSON Schema of its `--json` output, e.g. `sailfork schema pr view` - Preflight: `sailfork doctor --json` checks sign-in, token scopes and expiry, the git credential helper, server version (and the features an older server lacks) and which repository is in use; each check is ok, warn or fail with the command that fixes it, and the exit code is 1 when one fails. The MCP server offers it as the `doctor` tool - Output size: under a coding agent stdout is capped at 64 KiB (`--max-bytes N` or `SAILFORK_MAX_BYTES`, 0 lifts it); text is cut at a line with a closing note on how to get the rest, JSON is shortened so it still parses and says what it left out in `truncated`. `--summary` prints the compact form of `pr view`, `issue view`, `ci view`, `ci logs` (failed steps only) and `pr diff` (per-file stat) - [Help](https://sailfork.com/help.md): answers about signing in, SSH keys, moving to Sailfork, billing and your data, as Markdown ## Remote MCP server - [MCP endpoint](https://sailfork.com/mcp): streamable HTTP, OAuth sign-in in the browser, every tool - [Read-only endpoint](https://sailfork.com/mcp/readonly): only tools that never change data - [Toolset endpoint](https://sailfork.com/mcp/x/pulls,ci): pick toolsets (caissons, issues, pulls, ci, repos, drydock, context); add /readonly for read-only - [Protected resource metadata](https://sailfork.com/.well-known/oauth-protected-resource): RFC 9728 - [Authorization server metadata](https://sailfork.com/.well-known/oauth-authorization-server): RFC 8414, PKCE S256, client ID metadata documents and dynamic client registration - [Server card](https://sailfork.com/.well-known/mcp/server-card.json): name, version, capabilities and sign-in of the MCP server - [auth.md](https://sailfork.com/auth.md): which credential an agent uses where, and how to get it - [Connect an assistant](https://sailfork.com/settings/mcp): setup for claude.ai, Claude Code, Cursor, VS Code and ChatGPT - Local option: `sailfork mcp` runs over stdio with the CLI login (`--read-only`, `--toolsets pulls,ci`) ## WebMCP in the browser - An agent driving https://sailfork.com in a browser with WebMCP gets typed tools from `document.modelContext`, scoped to the page: repository, issue, pull request and organization pages each list their own. Tool names and inputs follow the hosted MCP (`repo_read`, `issue_get`, `pull_merge`). They run as the signed-in person; anything that changes data waits for the person to confirm in a dialog. See https://sailfork.com/docs/mcp#in-the-browser - Without WebMCP: the core flows (sign in, find a repository, read a file, issues, pull requests, inviting people) have a main landmark, headings and named controls, so the accessibility tree is enough ## API - [Full reference](https://sailfork.com/llms-full.txt): this index with the details an agent needs - REST API under https://sailfork.com/api, authenticated with `Authorization: Bearer `; client/src/contract.ts in the Sailfork repository documents every route and type - [API catalog](https://sailfork.com/.well-known/api-catalog): RFC 9727 linkset of the REST API and the MCP endpoint, with docs and status - [Agent skills](https://sailfork.com/.well-known/agent-skills/index.json): the `sailfork` and `caisson` skills, with SHA-256 digests - [Sitemap](https://sailfork.com/sitemap.xml): every site page, docs page and public repository ## Status - [Status page](https://sailfork.com/status): whether the website, API, git, MCP server and CI work right now, and 90 days of daily uptime from outside checks every 30 seconds (also at status.sailfork.com) - [status.json](https://sailfork.com/status.json): the current state as JSON; answers 503 when a part is down - [Uptime history](https://sailfork.com/api/status/history): the daily check and failure counts per part for the last 90 UTC days, as JSON - [Incidents](https://sailfork.com/api/status/incidents): outages and maintenance from the last 90 days and any still open, each with its updates, as JSON - [Status RSS feed](https://sailfork.com/status/rss.xml): one item per incident update from the last 90 days, newest first; the status page also takes email subscriptions, no account needed