Ferry
dlhck.github.io- Category
- Developer Tools
- Rank
- No. 1717Tools index
Previous survey · No. 1749 ·
- Type
- TOOL
- Use case
- Deployment & Operations
- Interfaces
- CLI
- GitHub
- 11 stars
- Latest release
- v0.12.0
- Date
About
Ferry keeps your coding agent setup in sync between your laptop and remote Linux boxes. It syncs skills, instructions, subagents, commands, supported settings and MCP servers through a private git snapshot repository that each box pulls over SSH or Tailscale. Logins and keys stay on the machine that has them, so you do not rebuild your setup by hand on every box.
At a glance
Ferry copies a chosen agent setup from your Mac or Linux machine to Linux machines reached over SSH. Skills, instructions, hooks and selected settings travel through a private Git snapshot repository. Your operator machine is the source of truth; each remote machine still needs its own tool login.
Good fit
Worth considering when several remote agent machines keep drifting from the setup you actually use. A versioned snapshot gives you a specific configuration to publish again or revert to. Previewing supported files and skipped integrations before a sync makes the boundaries more understandable than copying an entire home directory.
Consider something else when
You want two-way configuration merging, automatic account migration or arbitrary remote edits preserved as the authoritative setup. Ferry resets and cleans its managed snapshot checkout to the published commit. Adopt changes you want to keep before publishing; this behaviour concerns the managed checkout, not every project directory on the remote host.
Start here
Prepare a trusted Linux test machine with SSH access and an empty private Git repository you can push to. Start with ferry init --dry-run for the intended target, then inspect ferry sync --dry-run before applying a sync. Use ferry status and ferry doctor to check tools, authentication and skipped integrations. Try a manual sync before enabling continuous watching.
Cost and requirements
The software is MIT-licensed. The operator supports macOS or Linux on arm64 or x64; remote hosts need Linux, SSH and curl or wget, with Debian/Ubuntu documented as tested. Host rental, Git storage and model accounts are separate costs. Ferry can install or update remote agent CLIs; configuration transfer alone does not authenticate them.
Limits to know
Configuration sync filters known credential files and token patterns, but copied hooks and scripts can execute and change agent behaviour. Treat the snapshot as trusted code. Project-migration commands have separate options for allowing secrets, so config-sync filtering is not a blanket credential guarantee. Uninstall is also incomplete rollback: installed tools, logins and merged settings can remain on the remote machine.
Tags
Tech Stack
Media

Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.