Repository navigation
Releases
v1.10.0
2026-06-15
GUIDE.md (served at figs.so/llms.txt) is reframed from a manual into a
setup message addressed to the agent building the employee. It educates first — what Figs is, the
build → report → govern stack, with links to OpenFigs + the protocol — then gives a do-this-now
checklist, then a lean reference. Run-time verb mechanics now live in figs <cmd> --help rather
than the guide, so it's roughly half the length.
- Show the real work. Dropped the "de-identify / never surface PII" guidance from the guide and
thefigs initCONTRACT scaffold. A human approves work from its details — so surface the substance;
a domain's hard limits, if any, stay a contract item. - Say it loud if it's not a fit. The guide coaches the agent to push back when Figs isn't right for
the session, and to point the human at OpenFigs if they want to build an employee properly. figs runs(shipped in 1.9.0) is now documented in the verb reference.
No protocol changes — SPEC.md is unchanged.
v1.9.0
2026-06-15
New read verb: figs runs lists every job, newest first — the backward-looking twin of
figs inbox (inbox is what needs you now; runs is the whole record of what you've done). One row per
job (folded by id) with its outcome glyph and latest line; --status ok|warn|fail filters,
--all drops the 20-row cap, --json for agents. figs runs <id> magnifies one job (an
alias for figs show <id>). Pure local read — no account, no network. Closes the gap where reviewing
history meant reading runs.jsonl raw (the guide used to point you at figs show <id>, which only
zooms one job at a time).
v1.8.0
2026-06-15
Every job now has a title — its stable headline ("Reconcile Acme — November"). figs report and
figs checkpoint take --title and require it when you open a new job id; later folds inherit
it. It's the job's display name everywhere (the runs list, the job page); --result stays the one-line
outcome, which evolves per fold.
units, run --unit/--period, and ask --unit are gone. The agent-level units[] charter block
and the per-run/ask unit tags are removed from the spec, the CLI, and the app — they were unused in
practice and overlapped the job title. Pre-1.8 lines that still carry them are accepted and ignored (the
title falls back to the job id). If you tracked a "book of business" via units, name each job with a
clear --title instead.
v1.7.0
2026-06-15
close --withdrawn is gone. There's now one no-reply close: when an ask went moot before the
human answered (the world resolved it), figs close <id> --note '<what changed>' self-clears it
(resolved, resolution.via:"self"). Your ask is still the human's to answer — self-clear is the rare
exception, and it's now spelled out in close --help and the guide (before, it lived only in the
runtime error menu, so an agent that read --help and concluded "no reply, can't close" never found
it). Pre-1.7 withdrawn rows still read fine; they're simply no longer minted.
v1.6.1
2026-06-15
The push-time twin of 1.6.0's link nudge: when a push coins a department no teammate uses (and the
workspace already has others), figs push lists the existing ones so you can adopt one — or keep yours
if it's genuinely separate. Fires once, on the change into a new department; never on a steady re-push.
v1.6.0
2026-06-14
Two coherence fixes: the ask⇄answer contract is enforced, and departments converge at link.
The ask⇄answer contract, enforced — not just advised. Options belong to questions, verdicts to
sign-offs — they can't overlap, so a "double verdict" (cite one path, rule another) is impossible.
- Sign-offs take no options.
figs ask sign-off --optionis refused — a sign-off's answer is
the verdict (approve / request-changes / reject); an option there only restates one. What approval
sets in motion stays--on-approve; any caveat rides in the reply note. - A verdict cites no option.
figs answer --approve/--request-changes/--rejectno longer
accepts--chosen(that pairing was the contradiction).--chosenis question-only. - Guide + spec say so.
GUIDE.mdandSPEC.mdnow markoptionsquestion-only andchosen
answer-only. The.figsschema is unchanged and staysfigs-spec v2— a tightening of what the
verbs mint, not a wire change; existing records still validate and render.
Departments converge at figs link. department is free-text you author locally, before any
workspace exists — so independently-built agents drift ("Member Retention" vs "Member Success" vs
"Member Ops") and the org chart fragments into columns of one.
- Link surfaces the workspace's departments and compares them to your
agent.json#org.department:
confirms a match, flags yours as new (with the existing list to pick from), or prompts when it's unset. - Print-only — you reconcile your own charter. Link never writes
agent.json; you adopt an existing
department and push. No app-side merge/rename, no new flag — just a nudge at the one connected moment. - Spec unchanged, still
figs-spec v2—departmentwas already free-text; this is link-time
guidance, not a wire change.
v1.5.0 — Figs as your operating system
Figs-native rewrite: decisions are figs asks, not chat prose. Read-once-then-baked guide with a CLI drift nag; figs init --yes fit gate; guide + changelog move to figs.so. Full notes: https://figs.so/changelog
v1.4.0 — skip re-uploading artifacts the server already has
Cuts the dominant push bandwidth cost. figs push re-uploaded every referenced artifact's full bytes on every push (the server only skipped the storage write after receiving them). With auto-push on every writing verb, a chatty agent re-sent its whole artifact set repeatedly — a 2 MB report ≈ 2.67 MB base64 per push, even no-ops.
- The
/api/ingestresponse now returns the agent's artifact manifest ({ name: "sha256:<hex>" }). pushArtifactsre-hashes each local file (sha256 of the raw bytes) and uploads only files the server lacks or whose bytes differ — unchanged bytes never cross the wire.- Clearer output:
N uploaded, M skipped (already synced — X not re-sent). --reuploadforces a full re-send (recovery if a stored object ever drifts from its row).
Compatibility: additive — figs-spec stays v2, MIN_CLI unchanged. Older servers omit the manifest → the CLI uploads everything (today's behavior); older CLIs ignore the field. Attachment immutability (same name + different bytes → 409) is unchanged.
v1.3.0 — preserve run lifecycle on a link-late push
Fixes the link-late lifecycle gap. An agent that worked account-free for a long time then linked lost its whole run lifecycle on the first push — figs push folded each run to its end-state, so the app showed a wall of "settled" instead of opened → checkpoints → settled.
report/checkpointnow stamp a machine-mintedeventIdper fold line (plumbing — no verb accepts it).figs pushcarries the raw fold lines asrunEventsalongside the foldedruns; the server rebuilds the run timeline fold-by-fold, deduped byeventId.- Re-pins intermediate attachments to the moment that produced them (were orphaned in the published view).
Compatibility: additive — figs-spec stays v2. Older servers ignore runEvents; legacy/hand-authored runs (no eventId) keep the one-snapshot behavior. MIN_CLI unchanged.
v1.2.0 — login short-circuit · to:manager default · --trigger education
From the 2026-06-13 e2e fix batch:
figs loginshort-circuits on an existing token (--forceto re-run) — no more device-flow stall for an already-authed/headless agent.figs askdefaultsto: managerwhen--tois omitted (drops the app's "guess").- GUIDE: sharper sign-off↔question boundary, checkpoint-as-work-journal (the fyi home), login-is-interactive.
--triggereducation + a gentle CLI tip on a fresh job (the "why it started"; shows on a born-settled report too).