Build on Swarmfile
Keep the Git you already use and point LFS at us, git clone a project, mount it as a real filesystem path, or give every coding agent its own mounted workspace. Every command below is the shipped one.
Four ways in
Keep GitHub, move the big files
Point lfs.url at Swarmfile and your existing host keeps the code, commits, and pull requests. Objects of any size go here, chunked and resumable, andgit lfs pull still works for every teammate.
Clone it with git
For a project with git view on, git clone swarmfile://<org>/<project> works through the remote helper the desktop installers ship. Clone and fetch (including --depth shallow clones); no push yet.
Mount the repo
A project becomes a local path. Files are opened at native speed, every change is versioned, and there is no clone to wait on. The CLI drives it headlessly with a project API key.
One workspace per coding agent
Run N agents against one project with a mount each, a shared dependency cache per machine, and branch isolation. No worktree per task, no dependency reinstall per checkout.
Git-LFS quickstart
Mint a project-scoped key in the dashboard’s git-LFS tab, commit this to your repo, and store the key once per clone. Your git remote never changes.
# .lfsconfig, committed to the repo root
[lfs]
url = https://hub.swarmfile.com/orgs/<org>/lfs/<project>
# Once per clone
git lfs install
git credential approve <<EOF
protocol=https
host=hub.swarmfile.com
username=swarmfile
password=sf_key_…
EOFWorks with stock git-lfs: no fork, no plugin, and the pointers in your history keep working. Full guide, including CI.
Coding agents
The engine runs headless with one API key, and each mount is a normal filesystem path an agent can read and write:
swarmfile mounts list
swarmfile mounts open Y: --label agent-2 --branch feature-x
swarmfile mounts open Z: --label agent-3 --project proj_other
swarmfile mounts scratch-dir default # shared dependency cacheEvery save is versioned and lockable, and a burst of file creations is made safe by the durable create queue. Coding-agents guide, with measured behavior.
Automation and CI
- Runner as CI triggers on commits and tags, checks out without FUSE, and streams only the files the job touches.
- CLI reference for every command, including exit codes for scripts.
- Project API keys for headless engines (render nodes, CI), with an allowance per plan, so a farm isn’t billed as seats; personal access tokens and signed webhooks for everything else.
Format and portability
History is checkable without trusting us: commits are hash-chained, the hub publishes Ed25519-signed checkpoints, and the standalone swarmfile-verify-history binary recomputes every hash and checks the signatures against keys you pin, with no engine or mount.
The storage format is documented, the filesystem behavior is pinned by a conformance suite, and the migrate CLI imports from local, NAS, file-list, and S3 sources with verification and resume. Nothing about your data requires our software to read.
Start with the free tier.
Public projects are free and need no card. Private projects start on Starter at $5 a seat a month, and both paid plans start with a 7-day trial.