Docs

Settings and common questions

This page describes Fig 0.1.9.

Settings open from the gear icon in the project window (Settings). The Settings window has two tabs, Account settings and Project settings, and a list on the left of the open tab’s sections; clicking a name scrolls to it. The sections below follow the window’s own order. Every quoted sentence is the app’s own.

Make the interface larger or smaller

In the desktop app, hold Cmd on a Mac, or Ctrl on Windows and Linux, and press + or = to make the whole interface larger, − to make it smaller, or 0 to return to 100%. The number pad works too. The sizes are 100%, 125%, 150%, 175% and 200%; a larger size is skipped if its smallest window would not fit your screen.

Fig remembers the size on this computer, across projects and sign-ins. The smallest window grows with the interface; if your window is too small for the new size, Fig enlarges it. If this computer prevents saving, the size still applies for the current session; Fig shows a notice that it could not remember it.

Why did work stop?

Whatever stopped says why on screen. Find its sentence here; what to do about it is beside it.

The fleet shows “paused” and nothing is moving.
A core’s fleet — its agents — always comes up paused: after being switched on, restarted, updated or restored. Press the ▶ button (“Resume work”) next to the pause and stop buttons. While the project is stopped or paused, its items read “This project is paused”.
“Token budget reached. You may change it in your settings.” or “$ budget reached. You may change it in your settings.”
The project has reached a spending cap you set, and nothing new starts under it. Raise the cap or Clear it in Project Budgets; held work starts the moment there is room.
“<provider> is having an outage.” — “Fig can’t reach <provider>.” — “No internet connection.”
The provider or the network is at fault, not you. While no account can serve, the whole window dims to say so. There is nothing to do: “Fig will resume automatically when possible.” / “Fig will pick up on its own when the connection returns.” / “Fig will pick up on its own when you’re back online.”
“No usable accounts.”
Every account that could do the work is either refused by its provider or needs you to sign in. Each account’s card says which: “Quota reached.” (Manage billing opens the provider’s billing page; Check again asks the provider now), “Refused. Check with <provider>.”, “sign-in required” (Sign in) or “requires a new key” (Replace key). Fig retries a refused account on its own; work resumes as soon as one account can serve. See Providers.
“no accounts” — “all accounts are switched off for this project” — “all accounts require authentication” — “no switched-on account serves a selected model”
The fixes, in the same order: Add account; switch an account on under Providers; press Sign in on each account’s row; tick a model under a provider that has a switched-on account in Models. The notice on the held item links to the same places: See accounts or Choose models.
“accounts held for token availability” — “accounts held for token headroom” — “all accounts held temporarily”
The accounts are waiting on a provider’s limit or on turns still in progress. Wait: the holds clear by themselves and work resumes on its own. If a ChatGPT account has a reset to spend, Use reset appears on its card and its row under Providers; pressing it refills the windows at once.
“Unpriced tokens were spent under a $ budget. Work is paused until they are priced or ignored, the $ budget is removed, or pause on spending ambiguity is switched off.”
Fig doesn’t yet know the price of some tokens that were spent, and you asked it to pause when that happens. On the card, press Attempt to price or Ignore. Or switch Pause on spending ambiguity off under Fleet behavior, or Clear the $ budget.
“One of your sources is broken.” — “No sources attached.” — “One of your sources is detached.”
In the same order: a folder is no longer where the core expects it; no source is loaded at all; or an item’s work is in a place that no longer has a source. See sources on the notice opens Sources: put the folder back, attach it again, or Detach it.
“Docker’s disk is down to <free> free; Fig needs <need> free to resume.” — “This computer’s disk is down to <free> free; Fig needs <need> free to resume.”
Fig has already emptied its own cache; free what the notice asks for, where it says. On a Mac with a local core, Open Docker Desktop is where Docker’s disk limit is raised. Held items read “Fig’s core is out of disk space.” until the hold lifts by itself.
“Anthropic’s safety switch has flagged …”
Anthropic’s safety switch answered a flagged request with a weaker model. The notice offers Attempt handoff (start the session again fresh) or Degrade to <model> (continue on a weaker model). To let Fig decide without asking you, switch on “Safety flags are auto downgraded to the next weaker model.” under Fleet behavior.

Project settings › Fig core

“Fig runs your fleet in a container. You decide where that container is launched”

How do I switch the core off or on?
Use the core switch at the top of the section. Off means the core is not running at all; on brings it back, with its work paused.
How do I connect this app to a core on another machine?
Pick Remote core, type the core address (in the form https://host:4433) and the bearer token, then press Connect. The core there may be one fig-host started, which prints both, or one that machine’s app hosts with Reachable from other machines switched on.
How do I connect to this project from another machine?

A core the desktop app created answers only on its own machine. On that machine, open Settings › Project settings › Fig core and switch on Reachable from other machines. If the core is running, the app asks “Core needs to restart to be reachable from other machines — restarting pauses the fleet”: restart now applies it at once; restart later leaves “(restart core to apply)” under the switch until the next start from that machine. Switching it off asks the same way.

Click a core address row to copy it — choose the one on the network your other machine shares — and copy the bearer token from its row. In the client on the other machine, press the + beside the project tabs, choose Remote core, enter both, then press Confirm. Each project is its own core with its own address and token, so two projects on one machine never share either.

Where is my core’s token?
In the bearer token row; clicking it copies the token. The ⟳ beside it makes a new one, after the warning “A new token disconnects every other desktop app connected to this core. Paired phones ride their own keys and are untouched.” — Reset token confirms.
How do I back up a project, or move it to another machine?
Back up writes the whole core to one file; a running core is switched off while the copy is made and “comes back paused”. To restore, open the Open a project dialog and tick Start from a backup file. The full steps for moving a core from one machine to another are on the fig-host page.
“connected core’s version out of sync with desktop app — updating may fix issues.”
The core is older than the app. Press Update core, then Okay to “updating the core will stop any ongoing turns”. The opposite notice, “desktop app version out of sync with core”, means the app is the older one and offers Update now for the app.
What does Disconnect do?
It disconnects only this app: “Disconnect; the core keeps running”. A disconnected core keeps running when you quit the app or sign out.

Project settings › Sources

“Mount directories and/or load repositories into your project’s core.” The section has two lists: Repos and Folders.

How do I add a folder?
Under Folders, Add folder opens a folder picker on this machine. If the core is running, the app asks “Core needs to restart to add new folders — restarting pauses the fleet”: restart now attaches the folder at once; restart later leaves its row reading “(restart core to attach)” until the next start. On a remote core the button is disabled — “Folders can only be attached from the machine this core runs on” — so use fig-host attach on that machine instead.
How do I add a repository?
Under Repos, in the GitHub block: Sign-in shows a code (“Enter this code in your browser”; clicking the code copies it). Once the block reads “Connected as <login>”, Add repo lists the repositories you gave Fig access to under “Select repositories” — tick the ones you want, then press Add. If the list is empty it says “Give Fig access to more repos”: Manage opens GitHub’s own page for that access. Make repo creates a new private repository under your account.
An agent says “Push is disabled for this project.” — or a push was refused.
The push setting is the two-way control at the bottom of the GitHub block, Allow Fig to push to Github, set to Allow or Decline. It starts out as Allow, and Decline is the only setting that refuses a push made with Fig’s GitHub access. That access reaches only the repositories this project lists as sources, so a push anywhere else is refused whichever is chosen. If you are not signed in to GitHub, agents are told “No GitHub credentials available yet. When they become available you will be notified.” — press Sign-in. If the block reads “GitHub sign-in expired.”, press Sign in.
How do I remove a source?
Press Detach on its row. The files stay where they are. A repository with commits that haven’t been pushed to GitHub asks first — “Unpushed commits: <count>” — Detach anyway or Keep.

Project settings › Providers

How do I add an account?
Press Add account, pick the provider, then choose how to sign in: Subscription (Sign in with your browser) or API key (“Paste your <provider> API key.”; Get an API key opens the provider’s keys page), then Add. The account is checked with the provider before it is added.
A row says “sign-in required” or “requires a new key”.
Sign in on that row runs the browser sign-in again; Replace key takes a new key. Both buttons are on the account’s row and on its notice.
An account reads “switched off — project specific”.
You switched that account off for this project only. Flip its switch and it goes back to work.
A card says “Quota reached.” or “Refused. Check with <provider>.”
The provider refused the account — over billing, or for a reason it doesn’t give. Sort it out with the provider (Manage billing when the card offers it), then press Check again beside it; nothing changes unless the provider now serves the account. Or leave it: Fig retries on its own when work needs the account, and Ignore on the notice hides it in the meantime. Work moves to another account if one can serve.
What is the small slider beside an account’s switch?
The account’s speed. It appears on accounts whose provider sells a faster speed: two positions on an Anthropic account (“Fast mode off”, “Fast mode on”), three on an OpenAI account (“Ultrafast mode on” as well). It starts off, and like the switch it is set for this project. Moving it asks that speed from the provider on every new and running session on the account; tokens served at a speed are priced at that speed’s rate. While it is on, a bolt on the account’s card is yellow when the latest answer came back fast, orange for ultrafast, grey otherwise; an agent running fast has the bolt beside its name (“fast mode enabled”).
A row says “Fast mode disabled” or “Ultrafast mode disabled”.
The provider, not Fig, refused the speed: it isn’t enabled for the account there, the account’s plan doesn’t sell it, the account has no usage credits, or its organization hasn’t been given fast-mode access. Work goes on at the standard speed (a refused ultrafast falls back to fast where the provider sells it) and the slider stays where you set it. The button beside the line opens the provider’s page: Go to billing when credits are the reason, Go to <provider> settings otherwise. Once the provider’s side is settled, a credits or access refusal clears by itself on the next served turn; for the first two causes, move the slider or Sign in again.
A row shows Use reset.
OpenAI has granted this ChatGPT account a reset of its usage windows. Pressing the button (“Refills windows now”) spends it: both windows empty, the week starts over from the next request, and held work on the account resumes. The button appears only while a reset can be spent. To let Fig spend one without your click, switch on Use reset automatically when limits are reached under Fleet behavior.
“<account> API key nearing its spending limit.”
The key can no longer pay for one of the selected models; work runs on the models it can still pay for. Raise limit opens the key’s page at the provider, Change models opens Models, and Ignore hides the notice until the situation changes.
How do I remove an account?
Press remove on its row, at any time. Its credentials are deleted from the machine; work in progress moves to another account; its spending stays in the records (“removed account — recorded spending preserved”).

Project settings › Models

How do I choose which models Fig uses?
There is one checkbox per model, grouped by provider; all are ticked in a new project. Unticking a model stops new work from starting on it. The last ticked box can’t be unticked: “At least one model must stay selected.”
An account reads “no model selected — unused”.
No model is ticked under that account’s provider. Tick one there and the account goes back to work.
What is the section headed by a model name, with a key and six switches?
It is a helper model that Fig consults: “Fig asks <model> the calls an agent can’t make about its own work — whether it is really done, how hard a task is. Add a <provider> API key and Fig’s features that use <model> can run.” Its switches are Review optimization, Design optimization, Smart model selection, Optimized workflow, No stupid questions and Task pre-review; each one is explained beneath its label. Without a key they stay off.

Project settings › Project Budgets

How do I cap what a project spends?
Under “Global project budget caps”, type a number into Token budget ceiling or $ budget ceiling and press Set; Clear removes it. Each row shows what has been spent so far; the dollar figure is “As-if-metered” (its hover): every token priced at the provider’s metered rate, subscription use included, so it is not your bill. Once a cap is reached, everything is held, including the turn in progress, until you raise or clear it.
What are “Default unit budgets”?
The caps that every new item (Item ceiling default) and every new agent (Agent ceiling default) starts with, in tokens and in dollars. They apply only to items and agents created from then on: “Warning: default budget changes do not impact existing budget overrides!”
A note says “some spend is unpriced”.
Fig doesn’t yet know the price of some of the tokens spent, so the dollar figures are lower than the truth by that much. Nothing is hidden: those tokens appear in your spending as unpriced. Whether unpriced spending pauses work is set by the Pause on spending ambiguity switch under Fleet behavior, which is off by default.

Project settings › Fleet behavior

Can I leave and let Fig answer the agents’ questions?
Yes: the Your inbox switch (“keep your inbox from non-ambassador agents”). When it is off, every question from an agent — including those already waiting — gets Fig’s standing answer: go ahead, guided by the project’s grounding documents and the task’s purpose. Switch it back on to take the questions yourself again.
What does the safety-flag switch do?
When it is off (“Safety flags always offer handoff option.”), each flag waits for your decision. When it is on (“Safety flags are auto downgraded to the next weaker model.”), Fig moves the session to a weaker model itself and records the step in the Timeline.
What is “Pause on spending ambiguity”?
A switch that is off by default. When it is on, unpriced spending under a $ budget pauses work until that spending is priced or ignored, so a dollar cap can never be passed without you noticing.
What is “Use reset automatically when limits are reached”?
A switch that is off by default (“Manual resets only”): a ChatGPT account’s reset is spent only by your click on Use reset under Providers. When it is on, Fig spends a reset itself when the account’s weekly window is full with no credits left, a reset is available, and work is waiting that the account would take — once per hold.

Project settings › Local Permissions

Can Fig run commands on my machine?
Yes, by default — the switch reads “Fig may execute commands on this machine”; when off it reads “Fig may not execute commands on this machine”. The setting belongs to each machine separately, and agents can’t change it. Commands run only on the most recently connected machine that allows them: connecting from another machine that allows them switches this one off, and anything Fig started here is ended.
What has Fig run here?
“See what this core has run on this machine” — show history opens the exact record. While something is running, a red running locally button appears beside the chat; hovering over it shows kill commands, and pressing it ends everything this project started here.

Project settings › MCP Connections

In the app’s words, MCP servers “give agents tools from other services, such as GitHub’s pull requests and issues.”

How do I connect an MCP server?
Paste its address into MCP server URL and press Connect MCP. Fig asks you only for what the server itself requires: a key (“This MCP requires a key” → paste it → Submit key) or a browser sign-in (“Approve in your browser”). A server that works without signing in but offers a sign-in shows “Click to authenticate MCP” with Sign in on its row.
How do I give agents GitHub’s pull requests and issues?
Add GitHub’s MCP server fills in the preset address. The app then says: “GitHub’s MCP server needs a personal access token. Choose the account and repositories agents may access, then paste it here.” and “Suggested permissions: Contents read, Pull requests write, Issues write.” Make a token opens GitHub. Note the warning: “GitHub MCP tools can change GitHub data within the token’s permissions. Fig’s push setting does not control them.” The Sources section points here too: “For agents to make PRs add the GitHub MCP.”
A server reads “Sign-in expired — Reconnect.” or “MCP disabled”.
Reconnect runs the sign-in again, asking only for what the server requires. Enable brings back a server you disabled. Remove deletes it.

Project settings › Timed reports

How do I get a regular status report?
Tick timed reports and set the slider; the readout says “every <span>” and starts at 13 minutes. Reports are off by default, and an empty Timeline reminds you: “Timed reports are off.” Reports appear in the Timeline panel as “Status report” entries, and the same control is in the Timeline’s header.

Project settings › File retention

Why did a file an agent shared disappear?
Shared files are kept in the All files agents shared shelf, up to a size limit set by the File history capacity slider here (“Capacity before unpinned files expire”): from 10MB up to 10GB, or Unlimited. Once the limit is reached, unpinned files expire oldest first; Pin file on a file keeps it.

Project settings › Phone pairing

Which phones work?
Android on a 64-bit ARM processor today: the APK is on the download page. The iPhone app is coming soon.
How do I pair my phone?
Scan the code the desktop shows with your phone’s camera. To show it, flip the switch so the row reads “Phone pairing is on”, press Pair device to this core, type a Device name and press Generate pairing code; the code appears under “Scan this code with your phone’s camera.” Scanning it opens Fig on the project. If Fig isn’t on the phone yet, the download page opens instead: install Fig, then scan the code again. Already in the app? Press + (Pair device to core), then Tap to open camera and scan it — or copy the link beside the code, paste it into the box and press Tap to pair. The phone keeps the pairing once the core has answered it. Hide pairing code puts the code away; the pairing stands.
Does my phone have to be on the same network?
No. Away from the desk, on another network, the phone reaches the same live project through Fig’s relay — no tunnel or network setup. The machine hosting the core must stay on and online; while it is off or unreachable, the project’s card on the phone reads “Out of reach”.
How do I remove a phone?
Press Remove paired device beside it in this section; that phone is cut off at once. A connected phone can also Unpair itself from its Controls tab.

Account settings › Fig account

What happens when I sign out?
“Signing out stops the cores this app hosts for its connected projects and halts their work. A core running somewhere else only disconnects and keeps working.” Sign out asks you to confirm first.
What happens when I delete my account?
“Every core you own stops and stays off. Nothing is erased, and signing in again brings your account back.” Delete account asks you to confirm first.

Account settings › Sharing

What leaves my machine?
The app privacy page says what Fig always sends and what it sends only while this section reads “Data collection is allowed”. Share turns sharing on; Stop sharing turns it off, leaving “Data collection is NOT allowed.”

Account settings › Report a bug

“What went wrong? Your words, your picture and the app’s state go to Fig’s maker; your conversations never do. No reply comes, but the fix might.”

How do I report a bug?
Write what happened in the box (“What happened, and what you expected”), add a screenshot if it helps (“Drop, paste or click to add a screenshot”), and press Send. It works whether sharing is on or off. If the report doesn’t arrive (“The report didn’t go through. Send again.”), your words and picture are kept.
“The ambassador wrote a bug report for Fig. Do you want to send it?”
The ambassador can write a report when you ask it to. Nothing is sent until you decide: the notice offers Don’t send, See report — read it and its picture first — and Send.

Account settings › Stop core and quit Fig

How do I stop everything and close Fig?
Press Quit here, then I’m sure — quit: “Quitting stops the cores this app hosts for its connected projects. A core running somewhere else only disconnects and keeps working.” Closing the window instead leaves every core running. If a core refuses to stop, the dialog offers Leave it running, quit App only.