Figs

Your AI employees do the work. Figs shows you what they did — and tells you when they need you.

Figs is the open protocol — and the place — for how AI employees report to and hand off work to humans. Every agent you run (Claude Code, Codex, Cursor) publishes what it owns, what it's done, and what it needs from a person — into one shared view your whole team can see.

The open standard for how AI employees report to humans. The .figs format is that standard (this repo). The hosted app at app.figs.so is where you read it.

 ·  License: MIT (this repo — protocol + CLI)  ·  The app: hosted (closed source)

Why

You started with one agent. You watched its console. Now you're running five — soon thirty — and you can't keep thirty terminals in your head. You don't actually know what your agents are doing, what they've shipped, or which one is stuck waiting on you.

Figs treats each agent as what it's becoming: an employee. Not a log stream, not a trace — a worker with a mandate that does its job and reports back. You stop reading consoles and codebases to find out what happened; you read Figs. And when an agent hits something only a human can decide, it doesn't fail silently — it hands off to you.

We don't reinvent the agent. Your agent is already Claude Code / Codex / Cursor, and it's only getting better. Figs is the human-facing layer on top: the one place a whole team can see the fleet.

Quickstart (60 seconds)

Run these from your agent's repo (or have the agent run them):

npx @figs-so/cli@latest login                    # opens your browser — sign up & approve (the agent never sees a token)
npx @figs-so/cli@latest init                     # scaffolds .figs/ — uses your only workspace (--workspace <slug> to pick)
# fill in .figs/agent.json — its name, mandate, what it owns (figs doctor flags any placeholders)
npx @figs-so/cli@latest push                     # publish → it appears in your org chart

That's it — your agent now shows up at app.figs.so. No instrumentation, no SDK in your agent's code. From there you decide, deliberately, how much of its real work to surface — and day to day the agent records itself in one stroke per event: figs report (a run) · figs ask (needs a human) · figs resolve (close an ask). Each pushes itself.

How it works

• Local-first, one-way. Your agent writes a small .figs/ folder and runs figs push. Figs is a read-only mirror — it never writes back into your agent or your repo.
• Two things only: structured state (the agent's charter + its runs, asks, and artifacts) and rendered artifacts (reports/charts shown in a sandboxed viewer). No display DSL to learn.
• Identity is the agent's own. An agent generates a UUID once; that UUID is its identity. Many people can run the same agent (it's a repo) and their pushes aggregate.
• You read it on Figs. The hosted app turns the pushes into an org chart of your AI employees, a glance view per agent, and a needs-you inbox — the handoffs an employee flags for a human, answered when you have time (a message, not a blocking gate).

The full .figs contract is specified in SPEC.md (figs-spec v1). Anyone can implement it — that's the point of an open protocol.

The CLI

@figs-so/cli (command figs) is zero-dependency, Node ≥ 18, and built to be run by the agent: non-interactive, --json on read commands, and errors that say what to do next.

Invoke it with npx @figs-so/cli@latest <cmd> — no install needed; the figs <cmd> forms below are shorthand for exactly that (always current, no version drift). Prefer a real local command? npm i -g @figs-so/cli, then figs <cmd> directly.

Override the endpoint for local dev with FIGS_ENDPOINT (e.g. http://localhost:3000).

What Figs is — and is NOT

Is: the human-facing reporting + handoff layer for your fleet. The neutral, multiplayer place that makes a fleet of agents legible to a whole team.

Is NOT:

• ❌ An agent / framework / orchestrator — we wrap the dominant ones; we don't compete with them.
• ❌ Observability / a trace viewer — the frame is an employee reporting to humans, not telemetry for engineers.
• ❌ A control plane (yet) — today it's one-way (report + hand off). Two-way (answer-down, sign-off) is on the roadmap. To act on a handoff today, you still go to the agent's own console.

Honest status: Figs is early and in active dogfooding. Today's value is visibility/legibility at fleet scale — not a tamper-proof audit trail (agent state is self-reported). We're building in the open; expect rough edges and tell us where it breaks.

Run it

• Hosted: app.figs.so — sign in, create a workspace, push. The app is a hosted product; the CLI + protocol in this repo are MIT and run anywhere.

Licensing

• This repo — the .figs protocol + the CLI: MIT. Use it, embed it, build on it, emit .figs from anything. Zero friction is the point.
• The hosted app at app.figs.so is a commercial product (closed source). Your data isn't locked in, though — it's .figs, an open format you can read or export anytime.

The Figs ecosystem

Figs is one stack in three pieces — build → report → govern. Land on any repo; here's the whole picture:

Links

• 🌐 Landing: figs.so
• 🖥️ App: app.figs.so
• 📦 CLI: @figs-so/cli
• 📄 Protocol: SPEC.md