Skip to Content
FontegoDocs

How it works

Instances, workspaces, roles, synced copies, history, conflicts and the rules for paths.

Instances

An instance is one Fontego: one server, run by one organization, with its own accounts, settings, mail and visible name. A person can have accounts on several instances, even with a different email on each; their CLI keeps a session on each one.

Registration is closed: a server admin invites people, and each sets their own password from a one-time link.

Workspaces and roles

A workspace is a folder of files with its own members. Each member has one role in it:

RoleCan
readerread files and history, search, keep a synced copy
editoreverything a reader can, and change files
admineverything an editor can, and manage members, the workspace's details and its protected paths

Someone who isn't a member gets "not found", the same answer as for a workspace that doesn't exist. Server admins run the instance (people, settings, mail, logs) and act as admins in every workspace.

Synced copies

fontego clone makes a synced copy: an ordinary folder with a hidden .fontego/ that holds its own state. You edit files with anything. fontego sync sends your changes and brings everyone else's; fontego watch does it continuously, seconds after you edit and as soon as someone else commits, and waits while you are offline.

Agents and scripts that don't need a copy can read and write single files through the CLI or the API (Working without a copy).

History and conflicts

The server keeps each workspace as a Git repository, and every change is a commit that records who made it and, if an agent made it, which agent. People never need Git.

Every change says which version it started from. If someone else changed the same file meanwhile, the server merges the text when the edits don't touch the same lines. When they do, your version is kept next to the file as a conflict copy, name (conflict <who> <date>).ext, and the file keeps the server's version: nothing is lost, and fontego conflicts lists what is waiting to be merged by hand.

What the server refuses

Every write goes through the same checks, whoever sends it:

  • Roles: readers can't write.
  • Secrets and size: files that look like secrets (.env, private keys) and files over the size limit are refused.
  • Protected paths: only a workspace's admins can change them. By default they cover agent instructions, skills and rules (AGENTS.md, CLAUDE.md, .claude/, .agents/...).
  • Rejected paths: nobody can write them, because they would run code on the machines of everyone who syncs: hook settings, MCP server lists, editor plugins.
  • Archived workspaces take no writes until they are brought back.

A refused file is set aside and the rest of the change goes through; fontego sync reports it as skipped. See Protected and rejected paths.

Ignore rules

Each synced copy can keep files out of sync with .fontegoignore files, in the same syntax as .gitignore. As in Git, a rule only keeps new files from going up: it never deletes anything. See Synced folders.

One API

The web app, the CLI and any script use the same HTTP API, under /v1. Each route declares the command that uses it, and the server publishes its commands, so the CLI learns the commands of each instance it signs in to and can do anything the web app can. The only exception is proving who you are (a password, an invitation, authorizing a new machine), which always happens in the browser, so an agent never handles a password.

On this page