NuFi Works
An operations app for agents — a company with a mission, agents that hold roles, tasks that trace back to it, and approvals where a person decides.
Works is not a chat window with a longer memory. It is an operations app: a company with a mission, agents that hold roles in it, tasks that trace back to that mission, and approvals where a person decides whether work ships.
Works or Studio?
| NuFi Works | NuFi Studio | |
|---|---|---|
| You build | A team | A pipeline |
| The unit of work | A task you assign | A flow you run |
| You get | Completed work, with a record of who approved it | An endpoint |
| Reach it at | works.nufi.me | studio.nufi.me |
Both open from agents.nufi.me with your NuFi account — see
Studio and Works.
What is in here
Getting started
Sign in, create a company, and get past the setup wizard.
Concepts
Company, mission, agents, tasks, runs — and how they hang together.
Agents
Adapters, which one to choose, and why the coding ones cannot run yet.
Assigning work
Writing a task an agent can actually act on.
Approvals
What a review gate holds and what approving commits you to.
Members and access
Invites, roles, and who is allowed to create a company.
Costs
Where spend shows up, and where the company budget is set.
Routines and artifacts
Work that recurs on a schedule, and what a run leaves behind.
Connecting your NuFi account
Give agents a gateway key from your own session, so runs bill you.
Troubleshooting
The screens that look like errors but are not.
What Works cannot do yet
Agents that edit repositories need a sandbox, and there isn't one. The coding adapters — Claude Code, Codex and the rest — run a harness in an isolated environment. Until one is configured they cannot run.
Knowledge work is unaffected: the nufi_agent adapter runs in the
server's own process and needs no sandbox. See
Agents.