the problem
ai workflows are compute-heavy, but editing directly on a remote box is fragile. you either:- burn local resources running agents and builds on your laptop, or
- move your workflow to a remote machine and lose the simplicity of local files.
the solution
sincronizado gives you a local-files-first workflow:- local files: you keep ownership of your project directory.
- instant sync: mutagen keeps the vps copy in sync.
- persistent remote shell: a
tmuxsession on the vps keeps your agent and commands running even if you disconnect.
how it works
when you runsinc inside a project folder:
- it creates/ensures a mutagen sync session for that folder.
- it sshs to the vps.
- it attaches you to a persistent
tmuxsession for that project.
get started
is this for me?
| you will love sincronizado if… | you might not need it if… |
|---|---|
| you run agents/builds that strain your local machine. | everything you run locally is lightweight. |
| you want local-file ownership with remote compute. | you prefer a fully remote dev environment. |
| you want sessions that survive disconnects (tmux). | you don’t need long-running remote processes. |