Synced folders
Keep a local copy of a workspace in sync, resolve conflict copies, and keep files out with ignore rules.
A synced folder is an ordinary folder on your machine that holds a workspace. You and your agent edit it with any
tool; fontego keeps it in step with the server.
Get a copy
fontego clone notes # into ./notes
fontego clone notes ~/notes # or anywhereTo bring a folder that already has files into a workspace, run fontego link notes inside it: it connects the folder
and sends its files up.
The folder gets a hidden .fontego/ with its own state: leave it alone.
Keep it in sync
fontego status # what you changed since the last sync (works offline)
fontego sync # send your changes up and bring everyone else's down
fontego watch # keep syncing: seconds after you edit, and as soon as someone else commitswatch waits while you are offline and carries on when you are back. Only one watch runs per folder.
Each sync sends whole files together with the version each one started from, so nothing is overwritten by accident. If someone changed the same file meanwhile, the server merges the text when the edits don't touch the same lines.
Conflict copies
When two edits change the same lines, the file keeps the server's version and yours is saved next to it:
plan.md
plan (conflict ana@example.org 2026-11-19 10.42.07).mdfontego conflicts lists the copies waiting. Merge each one into its file by hand (or ask your agent to), delete the
copy and sync.
Skipped files
Some files are refused by the server, and fontego sync reports them as skipped while the rest go through:
- you are a reader of the workspace;
- the file looks like a secret (
.env, private keys) or is over the size limit; - it is a protected path and you aren't an admin of the workspace;
- it is a rejected path, which nobody can write.
The file stays in your folder as it is. Files on a rejected path are never sent down to anyone either.
Ignore rules
Ignore rules keep files that belong to one machine (dependencies, caches, build output, local .env files) from going
up. They use the same syntax as .gitignore, with case ignored, in three levels:
| Where | Applies to |
|---|---|
| built in | .git, .fontego, and system and editor junk |
.fontego/ignore | this copy only; it is never synced |
.fontegoignore, at the top or in any folder | everyone: it syncs with the workspace and travels with templates. A deeper one wins |
As in Git, a rule never deletes anything: it only keeps new files from going up. A file that is already in the
workspace keeps syncing both ways even if a rule matches it; fontego status says so, with the fontego rm that
takes it out of the workspace (your copy stays).
fontego status --ignored # what the rules keep in this folder
fontego check-ignore build/a.js # which rule matches a path, if anyIgnore rules are each copy's convenience. What a workspace protects or rejects is the server's policy, and separate.