Changelog

What changed on Sailfork, newest first. Everything here is live on sailfork.com.

194 changes since October 27, 2026 RSS feed What is coming next

Day 20

Diffs that know what a file is

Images, config files, notebooks, tables and diagrams read as what they are in pull requests and the file view, and risky files are marked.

New

  • Changed images show side by side with their pixel and file sizes, with a divider to swipe across them, or the new one faded over the old. Added and deleted images show on their own, and SVG files switch between the picture and its source.
  • JSON, YAML and TOML diffs list what changed by key path, like dependencies.react: "18.3.1" → "19.0.0", ignoring key order and formatting. Lines is one click away, and a file that does not parse shows its lines with the reason.
  • Files that need a careful look carry a badge in the diff: secrets, CI workflows, container builds, code owners, migrations and infrastructure. The merge checklist lists them too; only a migration still waits for a person.
  • The file view draws CSV and TSV files as a table and Jupyter notebooks as their cells, with markdown rendered, code colored and outputs shown. Code shows the source.
  • Markdown draws mermaid diagrams and $…$ and $$…$$ math, in READMEs, comments and MDX files, which now preview like markdown.
  • Git LFS files show and download as the real file, not the pointer: images diff like any other image, and a pointer whose file was never uploaded says so.
  • A diff names what its lines cannot show: line breaks changing between LF and CRLF, a byte order mark added or removed, a missing final newline, a file becoming executable, a symlink’s target, and a submodule added, moved or removed.
  • Save an issue list as a view of your own: its filters, grouping, order and the properties rows show sit as a tab beside My issues, one can open first, and the list remembers the layout you left it in. Views follow you between browsers.
  • New issues can start from the templates a repository keeps in .sailfork/ISSUE_TEMPLATE or .github/ISSUE_TEMPLATE, and the composer lists issues that may already say the same thing as you type the title.

Improved

  • Agent rule files from Cursor (.cursorrules), Windsurf (.windsurfrules), Cline, Kiro steering, Roo Code and Copilot chat modes and agents get the same header as Claude Code and Cursor rules: what they are and when they apply.
  • Files your .gitattributes marks linguist-generated or linguist-vendored start folded, and UTF-16 and Windows-1252 text is decoded instead of shown as binary or garbled.
  • Dependency changes in package.json, Cargo.toml, pyproject.toml and requirements files are summarized like lockfiles, as are flake.lock, mix.lock and Podfile.lock.
  • Notebook diffs draw changed markdown cells as markdown, old and new with the changed words marked, and MDX components show as labeled cards with their props instead of disappearing.
  • Issues filter by status, author, due date, relations (blocked, blocking, sub-issues, a pull request, needs input) and what involves you. Click "is" on a filter to make it "is not", "or" on labels to make it "and", or type label:bug or assignee:me in the search box, which now searches comments too.
  • Group issues by priority or milestone, order them by due date or oldest first, pick what rows show (milestone, estimate, author and more), and see each group’s points. A parent’s panel shows how many of its points are done.
  • Selected issues take a milestone, estimate, due date or parent at once, and close as done or won’t do. G and Shift+G jump to the first and last issue, and ⌘Enter opens one in a new tab.
  • The issues list sets a sub-issue under its parent when both are in the same group, and names the parent when they are not. An issue’s side panel draws the line of issues above it with arrows to the previous and next sub-issue, and a parent’s panel shows a progress strip and a count of its sub-issues by status.
  • An issue reads as one centered column. J and K, or the arrows by its position in the list, step to the next and previous issue of the list you came from, and Esc returns to that list with its filters. Who opened it leads the activity, Follow sits beside the Activity heading with the people following, and a sub-issue can be added right under the description.

Fixed

  • Caisson diffs carry the same file facts as pull requests, Git LFS uploads included, and raw UTF-16 and Windows-1252 files open as text in their own charset instead of downloading.
  • Scrolling a long pull request diff stays put while more files load: the line you are reading no longer jumps, and the conversation no longer shows up in the middle of the changes.
Day 19

Comment on words, not just lines

Select any text in a pull request’s diff to comment on exactly those words.

New

  • Right-click a line or a selection in a diff for its own menu: comment on it, suggest a change, copy the line or selection, copy a link or the path, view the file at that line, or mark the file viewed. Shift+F10 opens it from a focused line number; links and text fields keep the browser’s menu.
  • Selecting code in a diff offers Comment on this; the thread is anchored to the selected characters, which stay highlighted in the diff and quoted on the thread. Learn more

Fixed

  • A file’s header, its hunk headers, the unchanged-lines rows and the history row now start at the same left edge, and the Viewed controls line up on the right.
Day 19

Review together, and in one go

A pull request shows who is on it and where, and your review comments wait as pending until you send them all at once.

New

  • Faces under a pull request’s title show who else is on it, and hovering them says what each person is reading or writing.
  • The file list and each file header show who is on that file, and a line someone is commenting on is marked in the diff with their face.
  • Integrations and agents can show up too, under their client name, through PUT /pulls/{n}/presence. Learn more
  • Start a review: comments you add are saved as pending on every device you use, seen by nobody else, and sent together with Approve, Ask for changes or Send.
  • The review API takes line comments and the head commit you reviewed in the same call, and lands them all or none. Learn more
  • Review comments can carry proof: the command behind a finding, its exit code and output. It reads Verified when Sailfork ran it in a sandbox or CI at the pull request’s head, and Claimed otherwise. Learn more
  • Apps: a reviewer, CI provider or agent platform gets its own bot account, which you install on your account or organization, on every repository or only the ones you pick. Learn more
  • An app acts through installation tokens that last an hour and reach only that installation’s repositories. Its comments, reviews and presence carry the app’s handle, and suspending or removing it ends its tokens at once. Learn more
  • An app with sandboxes permission on an organization runs its own sandboxes there, so the proof it cites from them reads Verified. Learn more
  • Apps hear about what happens in their repositories: pull requests, reviews, review comments and threads, issues, pushes, CI runs and installation changes arrive as signed webhooks, with a delivery log and redelivery. Learn more
  • Apps and other CI providers report check runs on a commit. They show beside Sailfork CI on the pull request with their summary, Re-run and action buttons, count toward its checks and required checks, and their annotations appear on the lines they point at in the diff. Learn more
  • Find apps in the directory, install one on yourself or an organization you own, on every repository or only a few, and manage what is installed from settings: change repositories, pause or remove. Learn more
  • Build an app from Settings, Your apps: set its permissions and events, copy its client secret once, rotate or delete it. Learn more
  • Ask an installed app for review on a pull request, and choose which apps’ approvals count toward a merge (none by default, as with agents). Apps carry an app chip and link to their page. Learn more
Day 19

See how an agent reached you

Work an agent did through the CLI shows a terminal icon, and work done over MCP shows the MCP logo.

New

  • The CLI and both MCP servers send X-Sailfork-Surface, and the API returns it beside the agent client.

Improved

  • Issue leases, comments, pull requests, the Agents page and review history mark each agent with a terminal icon for the CLI or the MCP logo for MCP; hover the name to see the client too.
Day 19

A terminal mark for agents

Agents show a terminal icon instead of a robot.

Improved

  • An agent that does not name its client shows a terminal icon beside its name, the same mark as an agent on a client without a logo, and the Agents links in the site, docs, help and Ready issues use it too.
Day 19

Diffs you can read by color

Added and removed lines stand out in every diff, and each changed file shows its status and size.

Improved

  • Added and removed lines in pull requests, commits, compares and caissons have stronger green and red, with the line numbers a shade deeper.
  • Each file in a pull request’s diff shows whether it was added, changed, renamed or deleted, with a bar and +/− counts for how much changed.
  • The Unified and Split switch has icons.
Day 19

One header row for code on a phone

On a phone, a file or folder opens under a single row: branch, path and one menu.

Improved

  • The path bar stays on one line on a phone and drops the repository name the top bar already shows; a long file name truncates instead of pushing the actions to a second row.
  • Code and Blame, Copy path and every file action live in the one menu at the end of that row, aligned and labelled.
  • The top bar on code pages names the organization and repository instead of repeating Code.
Day 19

States read in color

Merged, passed and waiting on you now look different at a glance, everywhere they appear.

Improved

  • Added lines are green and removed lines red, in the change bars and every +/− count.
  • Merged pull requests and caissons are green instead of blue or gray, and anything waiting on a person, from a held write to a production deploy or a pending invite, is amber.
  • Notifications show passed deploys and checks in green, and approvals waiting on you in amber, not only failures in red.

Fixed

  • A short list of changed files beside a pull request no longer scrolls away at the end of the diff.
Day 19

Phone menu, team switching and toolbars

The phone menu rises from the Menu button, every team is one tap away in it, and crowded toolbars fold into one labelled menu.

New

  • Your personal workspace and every organization sit as chips at the top of the phone menu: one tap switches.

Improved

  • Menu opens as a sheet from the bottom of the screen, where its button is, instead of from the left edge.
  • On a phone, the file and folder bars keep Code, Blame and Go to file in place and fold Edit, Copy, History, Raw, Download, Delete and New file into one menu with labels.

Fixed

  • The app no longer bounces as a whole on an iPhone when you drag the top bar or the tab bar.
  • An organization’s name no longer breaks across lines on a phone, the issues Group by options fit, the activity page scrolls with the tab bar at the bottom, and a commit’s file list no longer scrolls sideways.
Day 19

Sailfork on a phone

Search is one tap from every page, code wraps to the screen, and fields no longer zoom the page on an iPhone.

New

  • A search button in the top bar on phones and tablets opens the command menu from any page, instead of only from inside Menu.

Improved

  • Code and diffs wrap to the screen on a phone, so a review needs no sideways scrolling. Wrap lines still turns it off, and the choice is kept.
  • Issue titles show two lines on a phone instead of cutting off, and the issue views scroll sideways instead of wrapping onto a second row.

Fixed

  • Search boxes, pickers and settings fields no longer zoom the page in when tapped on an iPhone.
  • Tall dialogs scroll inside the screen, the command menu sits at the top on a phone, and the menu and side panels stay clear of the home indicator.
Day 19

Folders of any size open at once

A folder with a million files opens on its first thousand and loads the rest as you scroll.

Improved

  • A big folder shows its first 1,000 entries right away and loads the next 1,000 as you scroll, in the folder page and the file tree. The folder’s file and folder counts cover all of it.
  • Each page of a folder lists in about a quarter of a second on a million-entry folder, down from 0.6 seconds, and the page no longer waits for every page before it draws.
Day 19

File icons for every file type

Files in the code view, pull requests and go-to-file show an icon for their type, from configs and lockfiles to languages and tools.

Improved

  • File icons now cover about 1,400 extensions and 2,100 file names, like package.json, Cargo.toml, Dockerfile and README, instead of a dozen generic shapes.
Day 19

File trees work from the keyboard

The file trees in code and pull requests take arrow keys and type-ahead, and a pull request’s tree filters and marks each file’s change.

New

  • A pull request with more than 10 changed files gets a filter above its file tree.
  • Pull request and caisson trees mark each file A, M, R or D, and a closed folder shows a dot when files inside it changed.

Improved

  • Arrow keys move through a file tree, right and left open and close folders, Home and End jump to the ends, and typing a name jumps to it. Screen readers hear it as a tree.
Day 19

Large files open and download

A file over 10 MB shows its size, a preview of its start and a download of any size.

Improved

  • A file over 10 MB shows its size and, for text, its first 256 KB. Files up to 10 MB show in full. Learn more
  • Downloads stream, so a file of any size downloads from its page.
  • Diffs of large files say a large file changed instead of loading it.
Day 18

Merge queue, push rules and rulesets

The merge queue lands pull requests in batches, and branch rules now say who may push, who may merge and whether commits must be signed.

New

  • Turn on the merge queue in repository settings, and ready pull requests land in batches. A red batch is rerun once, then the pull request that broke it is reverted. Learn more
  • A stack waits in the queue as one unit and lands bottom first.
  • Check the queue with sailfork queue status, leave it with queue leave, or use the merge_queue tool from an agent. Learn more
  • A branch rule can require signed commits. Sailfork checks SSH signatures against the signing keys on the author’s account.
  • Branch rules take lists of people and teams who may push and who may merge, and you can protect tags the same way. Learn more
  • Organizations get rulesets that apply one rule to many repositories, with a dry run, a bypass list and a push audit.
  • Owners files can decide who approves a change, per branch rule. Comment and formatting changes in owned paths need lighter approval, and a repository admin can merge past approvals with a reason that is logged.

Improved

  • Checks skipped because of a path filter show as skipped and count as passed, in the web app, pr checks and the MCP tools.
  • Tokens and SSH keys show their limits in each row.
Day 18

Moves from GitHub bring more with them

A move now copies Git LFS objects, branch protection and rulesets, and the other parts of a GitHub repository that people notice are missing.

New

  • Git LFS objects come across with the repository, every version the history points at. Learn more
  • Branch protection, rulesets and the merge queue are copied once, when the copy is made, and never over a rule you already set. Learn more
  • The GitHub wiki becomes a sibling repository.
  • Collaborators and teams carry over to the copy.

Improved

  • Every label and milestone moves, not just the ones in use.
  • The compare and commit pages say when they list only the first files of a large change.
Day 17

Git LFS, forks and waits that wake on events

Sailfork serves Git LFS, forks repositories without copying them, merges for you once checks pass, and tells agents and the command line when CI changes instead of making them poll.

New

  • Git LFS works on Sailfork with the standard git-lfs client, up to 10 GiB of LFS objects per repository. Learn more
  • Fork a repository with sailfork repo fork and list its forks. A fork shares its parent’s stored data, so it is ready at once. Learn more
  • Auto-merge runs on the server. sailfork pr merge --auto returns at once, and the pull request merges when its checks pass, only if the branch is still at the head you reviewed. Learn more
  • The sign-up form asks how you heard about Sailfork. The answer is optional.
  • Create SHA-256 repositories from the new-repository page or the command line.
  • Purge a repository now from its deletion notice, in the web app or with sailfork repo purge, once you type its name.

Improved

  • Folders list 1,000 entries at a time with a cursor, in the API, the command line and the MCP tools.
  • pr checks --watch and the pull_checks tool wake on CI events instead of a timer.
  • Go-to-file ranks paths on the server, and first visits to profiles and organizations paint from the server.
Day 16

Fix conflicts without a checkout, and merge what you reviewed

A pull request that conflicts with its base can be fixed in the browser, and a merge is refused if the branch moved after you reviewed it.

New

  • Resolve a pull request’s merge conflicts in the browser. Pick a side, keep both or edit each block, and Sailfork lands one merge commit on the branch. Learn more
  • Agents and scripts list and resolve the same conflicts through the API, with no local checkout. Learn more
  • A merge is refused with a 409 when the head moved from the commit you reviewed. pr merge --match-head-commit sends the commit to the server.

Improved

  • The merge panel links to the conflict page instead of telling you to resolve files locally.
  • The merge result lists the merge commit, the method used and whether the branch was deleted.
Day 16

Drydock owner controls, agent discovery and an app that opens offline

Drydock owners can see and stop what runs on their hosts, agents can find Sailfork’s tools without a guide, and the app keeps itself on your device.

New

  • Drydock owners see background and CI sandboxes, stop them, and read why a job is waiting. Learn more
  • Owners get mail when a host of theirs goes silent or runs short of disk, and again when it recovers. Turn it off with sandbox settings set --alerts off.
  • Drydock runs gVisor on KVM on bare-metal hosts, and the web app shows each host’s platform.
  • Sailfork publishes an API catalog, an MCP server card, agent skills and an auth.md at their well-known paths, and the homepage links to them. Learn more

Improved

  • The app keeps its files on your device, and pages you opened while signed in open again without a network. Signing out clears them.
  • Pages and the API answer faster for signed-out visitors, with the session, account and organizations loaded in one request.
Day 15

Stacked pull requests

Open a pull request on top of another, review each one on its own, and merge the stack in order.

New

  • Stack pull requests with sailfork pr create --onto N, move one with pr edit --onto, and print the tree with pr stack. Learn more
  • The pull request page shows the stack it belongs to.
  • pr merge --stack merges the levels below first, and each level lands on the bottom base.
  • When the pull request below is squashed or rebased, the branches stacked on it carry over without showing its work twice.
  • Agents get stack tools over MCP. Learn more
  • Sub-issues nest as a tree, and a graph shows the work around one issue or pull request.

Improved

  • The docs have a new layout, navigation and agent setup, with guides for caissons, sandboxes and moving from GitHub. Learn more
Day 13

Releases, webhooks and outside contributions

Repositories get releases and webhooks, anyone can propose a change to a repository they cannot push to, and public repositories paint before the app loads.

New

  • Repositories have a Releases tab with downloadable assets, and sailfork release lists, views, creates, uploads and edits them. Releases from GitHub come along in moves. Learn more
  • Repository settings have a Webhooks section. Sailfork signs each delivery for pushes, pull requests and CI runs.
  • On a repository you cannot push to, choose Propose a change to open a pull request from a branch of your own.
  • Edit, create and delete files in the browser.
  • Open a pull request from the compare page.
  • A public status page shows whether the database and storage are healthy. Learn more

Improved

  • A public repository’s home paints before the app’s code arrives.
  • Lock conversations, hide comments and block people from a comment, and manage blocks in settings.
Day 10

CI and sandboxes for teams

Version 0.2.10 adds manual workflow runs, a per-run GITHUB_TOKEN, artifacts and test reports, matrix jobs, hosts that upgrade themselves, and controls for organizations.

New

  • Run a workflow by hand with inputs from the Runs page, sailfork ci run or the ci_dispatch tool.
  • Every run gets a GITHUB_TOKEN, a short-lived access token for the run, limited by the workflow’s permissions and revoked when it ends.
  • CI keeps uploaded artifacts for 30 days and shows JUnit test results on the run page.
  • Each matrix combination runs as its own job, and always() and failure() work across approval gates.
  • Drydock hosts (0.2.10) upgrade themselves when a new version ships, and two hosts can share one machine.
  • Organizations can set sandbox limits, allowed images and network, and sealed secrets, and see sandbox minutes in usage.
  • Personal repositories can run CI and caisson tests on your own Drydock host.

Improved

  • Sandboxes keep a per-repository dependency cache, so installs repeat faster.
  • Agents can test any branch with repo_test, commit and open a pull request with caisson_ship, and look around a repository before opening a caisson.
Day 10

Held writes reach people, and sandboxes have a page

Version 0.2.9 tells approvers about held writes, shows running sandboxes in the app, and smooths what small agents still tripped on.

New

  • A write held for a person shows up in the Inbox and email of the people who can approve it, and clears once it is answered.
  • Organizations have a Sandboxes page to see, extend and stop running sandboxes.
  • Anyone can read the caissons of a public repository.

Improved

  • caisson_status and caisson view list the sandboxes a caisson started, and every caisson tool takes org.
  • Sandbox commands skip pip’s root-user warning, and a broken patch names the hunk and line.

Fixed

  • A repository at its caisson limit names the caissons holding the slots.
Day 10

Caissons that small agents can drive

Version 0.2.8 fixes what small agents tripped on while driving caissons, and the caisson pages in the web app.

Improved

  • The command line and MCP tools wait out a server restart instead of failing, and auth status no longer calls a working token rejected during one.
  • caisson_test can stop a sandbox it kept, and answers name only tools the agent has.
  • A command missing from the default sandbox image comes with a hint to pick another image, and the docs list what the default image has.
  • --json FIELDS works with a space on every command, caisson grep accepts -n, caisson commit takes several -m, and grep and find exit 1 when nothing matches.

Fixed

  • MCP tools reject unknown arguments, accept owner for org, and flag a read that failed for some paths.
  • The caisson page shows every step with its line counts, folds one write into one step, and uses the organization’s rules.
  • The caissons list reaches every caisson, and organization pages link to the organization’s rules and Drydock setup.
Day 10

Run a caisson’s tests in a sandbox

Versions 0.2.6 and 0.2.7 run a command on a caisson’s code in a throwaway sandbox on your own Drydock machines, and sandboxes wait for room instead of failing.

New

  • Run a command on a caisson’s code, its branch plus uncommitted edits, in a throwaway sandbox with sailfork caisson test, or the caisson_test tool for agents. Learn more
  • Creating a sandbox waits for room when every Drydock host is full, 60 seconds by default and up to 600 with --wait, and waits for a host that is reconnecting after an update. Learn more

Improved

  • A sandbox started from a caisson syncs its files to the caisson before every command, removing deleted files and keeping build output.
  • sailfork caisson test exits with the command’s own exit code, and 124 when it times out.
  • Restoring the path of a write held for a person withdraws it, and agents are told so.

Fixed

  • A sandbox now stays alive when one process in it runs out of memory.
  • Drydock hosts (0.2.7) remove the containers of sandboxes that stopped on their own.
Day 8

Signed-out visitors can read public profiles

Anyone can read public profiles and repositories without an account, and you can move a whole GitHub account in one step.

New

  • Signed-out visitors can read public profiles and repositories.
  • Move a whole GitHub account to Sailfork from a single page. Learn more
  • Profiles show your imported GitHub contribution history by year.
  • Contributors appear as people and link to GitHub until they join Sailfork.

Improved

  • Commits now carry their author’s email address.

Fixed

  • People outside a profile or organization now see its public view.
Day 7

The Sailfork command line

The sailfork CLI is out for macOS and Linux, with caisson commands, browser sign-in and scoped tokens. Moves from GitHub now bring issues over.

New

  • Install the sailfork CLI for repositories, pull requests, issues, CI, keys, tokens, usage and raw API calls. Learn more
  • Sign in to the CLI from your browser with a device code. Learn more
  • Open, read and write caisson files from the CLI, and run caissons as an MCP server for your agent. Learn more
  • Access tokens have five scopes, and the server enforces them on every request.
  • Moves from GitHub bring issues over with their comments, labels and state. Learn more
  • Choose what happens to the GitHub repository when a move starts, including keeping it as a pull mirror. Learn more
  • Transfer a repository to an organization, or back to its admin, from its settings.
  • Organization owners can connect their own Depot account and run .github/workflows on it.
  • Add and verify organization domains with a DNS TXT record.

Fixed

  • Old links to a transferred repository now forward to its new address.
Day 6

Caissons, SSH and code search

Caissons, online worktrees for agents, are available through the API. Git works over SSH, pushes can be far larger, and you can search code across your repositories.

New

  • Caissons: online worktrees over a branch that agents read and edit through a REST API. Learn more
  • Clone, fetch and push over SSH with the keys you add in settings.
  • Search code across repositories, branches and paths at /search and from the command menu.
  • Pushes can be far larger. The current numbers are on the limits page. Learn more
  • Sign in with a passkey, and set up an authenticator app with a QR code.
  • Sign in with GitHub, link your account, and keep repositories in sync with push and pull mirrors. Learn more
  • Shallow and partial clones, and a git-remote-sailfork helper for faster full clones.
  • Mirror include and exclude patterns, a preview of a first push, and alerts when a mirror breaks.

Improved

  • Clones, fetches and pushes are faster, and large pushes stay alive while they are checked. Learn more
  • File history follows renames, and the app opens offline from your last session.
Day 5

Caissons get their own page

Caissons are now a named feature with a page that explains them, alongside a new code browser and a hub for moving repositories.

New

  • A caissons page explains online worktrees, with a replay of a session and a map of every live caisson. Learn more
  • Open a caisson for an agent from the browser and set what it may and may not change. Learn more
  • Pages for workflow runs, with a pipeline graph and a log viewer for each run.
  • A mirrors page for setting up and watching repository mirrors.
  • A hub for moving repositories from GitHub, with a status for each repository and a switch day. Learn more
  • Organization teams, and bills you can print.
  • Set repository rules in .sailfork/repo.toml, including a monorepo layout and a merge queue.
  • Upload and crop a profile picture or organization logo.

Improved

  • A code browser built around a file tree, and a pull request list that works as a queue.
  • The sidebar and command menu offer what the current page needs.
Day 2

Help center and password reset

A help center, clearer error pages and password reset.

New

  • A help center with answers about signing in, git, moving and billing. Learn more
  • Reset a forgotten password from the sign-in page.
  • Error pages for server errors, access denied and rate limits, with a short reference on unexpected errors.
Day 1

The first Sailfork site and app

The Sailfork site, sign-in, repository and organization pages, settings and a pull request page with a merge gate.

New

  • The Sailfork site with a landing page, about, benchmarks and platform pages. Learn more
  • Sign in and sign up with email, plus a contact form.
  • Profiles, organization pages and repository views inside a new app shell.
  • A pull request page with a merge gate.
  • Account settings, quiet hours, a searchable time zone picker, and plan and usage with payment methods.
  • A page for moving repositories to Sailfork, with move scripts for any git host. Learn more

Improved

  • The code page shows how a repository grows over time.

Day 1. Sailfork set out on October 27, 2026.

Loading Sailfork