Docs
How Fig works
This page describes Fig 0.1.9.
The client and the core
The Fig desktop app is only a client. The work is done by a core: one container per project. It holds everything that project needs: the agents’ sessions, the project’s records, and your conversation with the ambassador, the agent you talk to. It also runs the project’s agents, which Fig calls the fleet. The app shows you a core and lets you steer it. The work itself happens in the core.
That is why closing the app does not stop the work. In the app’s own words: “Fig’s core stays running when you close the app. Work continues in the background. To stop the core do so in your settings before closing the app.”
One door
There is only one way into a core: an encrypted connection that needs the core’s address and its bearer token (a secret that proves you may connect). Everything that shows a core goes through this same door and sees the same live state, so two clients open on one project never disagree.
You can copy or reset the token under Settings › Project settings › Fig core — see Fig core.
Where a core runs
When you open a project, the app asks one question about its core — “Fig runs your fleet in a container. You decide where that container is launched” — and offers two choices:
- Local core (“This machine”): the app starts the container with Docker on the computer you are using. Docker is the only thing that computer needs. Without it the app says “Docker is not installed — Fig requires Docker”.
- Remote core (“Somewhere else”): the app connects to a core that is already running
on another machine. You type its core address (in the form
https://host:4433) and its bearer token, then press Confirm. That core may be one fig-host started or one that machine’s app hosts with Reachable from other machines switched on.
Each project is its own core, with its own address and token. A core the desktop app created answers only on its own machine until Reachable from other machines is switched on under Settings › Project settings › Fig core. A core fig-host created answers other machines from the start. Whichever program starts the core — the app or fig-host — honors the saved choice.
A core works the same wherever it runs: the same settings, controls, sources and work. The container runs in the hosting machine’s Docker. In the client, attaching folders and changing Reachable from other machines can only be done on that machine — for folders, the app says “Folders can only be attached from the machine this core runs on”. Everything else, including switching the core on and off, works from any connected client.
Your software stays yours
A project’s Sources are what the core works on: “Mount directories and/or load repositories into your project’s core.” A folder is a folder on the core’s machine; a repository is a repository you own on GitHub. Your software stays in those places, which belong to you. The core keeps its own state — sessions, records, conversation — in storage of its own, never inside your folders. Detaching a source never deletes its files.
Fig’s work goes onto branches of its own in your folders and repositories. Nothing in Fig merges automatically; a merge is always an agent’s deliberate act. Pushes to GitHub use the access you granted when you signed in to GitHub, can reach only the repositories the project lists as sources, and can be turned off in one click: Sources › Allow Fig to push to Github › Decline.
Fuel
Fig runs on your own accounts with AI model providers. Under Settings › Project settings › Providers, Add account picks a provider and then one of two ways in: Subscription, which signs in through your browser, or API key. You decide which accounts a project may use, which models its fleet may use, how fast each account runs where its provider sells a faster speed, and how much it may spend — see accounts, models and budgets. The tokens the models consume are billed to your own accounts.
A core comes up paused
Switching a core on never starts the work by itself. A core always comes up with its fleet paused, whatever it was doing when it stopped, and only you can set it going: press the ▶ button (“Resume work”). A pause you set holds until you end it; no restart undoes it. The reverse is also true: closing the app, or pressing Disconnect in Settings › Fig core, leaves the core running.