Sailfork, from your terminal.
One binary for repositories, pull requests, issues, CI and agents, on macOS, Linux and Windows.
$ curl -fsSL https://sailfork.com/install | sh
$ irm https://sailfork.com/install.ps1 | iex
The first line is for macOS and Linux, the second for Windows. No sudo. Install page and script All releases API and MCP docs
-
Install
One command puts a single binary in
~/.local/binafter checking its SHA-256. -
Sign in
sailfork auth loginopens the browser; approve once and the terminal is signed in. -
Work
Clone, push, open and merge pull requests without leaving the shell.
# install $ curl -fsSL https://sailfork.com/install | sh Downloading sailfork for aarch64-apple-darwin Installed sailfork to ~/.local/bin/sailfork # sign in $ sailfork auth login Sign in to https://sailfork.com either way: in the browser that just opened, or enter the code it prints at sailfork.com/device. Logged in to https://sailfork.com as fenil # open a pull request $ sailfork repo clone fenil/ocean-landing && cd ocean-landing $ git switch -c tide-chart && git commit -qam "Draw the tide chart" $ sailfork pr create --title "Draw the tide chart" Created pull request #12: Draw the tide chart https://sailfork.com/fenil/ocean-landing/pulls/12
As fast as curl
Most of a call is the network. The CLI adds a few milliseconds on top, and starts before you notice.
| sailfork repo view, on sailfork.com | 118.6 ms |
|---|---|
| curl, the same request | 135.4 ms |
| gh repo view, on github.com | 514.7 ms |
| sailfork --version | 3.4 ms |
Mean of 50 runs with hyperfine on an Apple silicon Mac in San Francisco, November 2026. gh talks to github.com, so its time includes a different network path. The binary is 7.28 MB on macOS.
Built for scripts and agents
The same commands work by hand, in a script and in an agent loop.
- Tables and pipes
- A table in a terminal, tab-separated lines when piped.
SAILFORK_FORMATchanges the default. - JSON on every command
--jsonprints structured output, and--json=id,titlekeeps only the fields you name.--jqbuilt in- Filter the output without installing jq:
sailfork repo view acme/app --jq .defaultBranch. - Output with a schema
sailfork schema pr viewprints the JSON Schema of whatpr view --jsonprints.- Documented exit codes
sailfork help exit-codeslists what each code means and the shape of a JSON error.- No telemetry
- The CLI sends no usage data. It checks for a newer release once a day.
- A short alias
- Run
sailfork alias installto also getsf. It is opt-in.
Sign in any way
No password in the terminal, and a way to sign in on any machine.
- Browser, code or token
- Approve in the browser, enter the device code from another computer, or paste a token with
--with-token, whichever finishes first. The old token is revoked only after the new one works. - A token you can see
- Each login is an access token named after the machine, listed in Settings and revocable there. It does not expire on its own;
sailfork token create --expires 8hmakes short-lived ones. - Kept in the keychain
- The token lives in the macOS keychain or the Linux secret service, never in your shell history.
- A coding agent can start it
sailfork auth login --device --no-wait --jsonprints the address and code and returns at once, so the agent can show them to you. You approve in the browser, signing up there if you have no account, andsailfork auth login --resumefinishes. The agent never sees a password.- git uses it too
- The same login makes plain
git pushandgit pullsign in with the token. If another credential helper already answers for Sailfork, login leaves it alone and says to runsailfork auth setup-git.
What it covers
Every command prints a table in the terminal, plain lines in a pipe, and JSON with --json.
- repo
- Create, list, view, clone and delete repositories.
- pr
- Open, check out, diff, review, comment on and merge pull requests.
- issue
- Open issues, move them through stages, label and assign them.
- caisson
- Edit a repository on Sailfork with no clone, run its tests in a sandbox, then commit and open a pull request.
- sandbox
- Run code in isolated sandboxes on your organization’s own Drydock machines, and run a caisson’s tests there.
- ci
- List runs, follow logs, rerun or cancel, and manage secrets.
- key and token
- Add SSH keys, create and delete access tokens.
- auth
- Sign in, check who you are, and let git push with the same login.
- onboard
- Lists every setup step as done, todo or needs a person, with the exact next command. A coding agent can run it again at any point to set a newcomer up.
- org
- Create organizations, invite people by email or handle, list members, and accept or decline invitations.
- migrate
- Copy repositories over from GitHub on the server, check progress after closing the terminal, retry what failed.
- api
- Call any route with your token when there is no command for it yet.
Caissons from the shell
Push a folder into a worktree on Sailfork. Only files that changed are sent, so checking 200 unchanged files takes 52 ms. About caissons
$ sailfork cs open --title "Fix the tide math" --scope src/tide/ c-z4nwicj7 caisson/c-z4nwicj7 $ sailfork cs put c-z4nwicj7 src/tide 3 uploaded, 0 unchanged, 0 held, 0 failed $ sailfork cs commit c-z4nwicj7 -m "Fix the tide math" f320d40 Fix the tide math $ sailfork cs pr c-z4nwicj7 Opened pull request #102
Install options
Set these before the install command, or run them once it is installed.
- SAILFORK_VERSION=<version>
- Install a specific release instead of the latest. Every version is listed under All releases.
- SAILFORK_INSTALL_DIR=/usr/local/bin
- Install somewhere other than ~/.local/bin.
- sailfork upgrade
- Replace the binary with the latest release, checksum verified.
- sailfork completion zsh
- Print completions for bash, zsh, fish or PowerShell.