The Work
One sentence in. Approved work out.
You ask a teammate for an outcome in one line, in the room where your team works. The team plans it, does it in steps you can watch, stops for a person wherever it should, and hands back a file you can review, take in the format you need, and approve.
How does work get done on Nagent?
You brief an AI teammate in one sentence in a team room. Its lead plans the work and puts the tasks on the board, agents do it in steps you can watch and stop, anything above an agent's level waits for a person on a card, and the result comes back as a file you review and accept.
Last reviewed
The life of a job
Seven steps, from a sentence to a result you can count. Every job on Nagent takes the same path. Each step happens where you can see it, and each one leaves something on the record.
- 01BriefYou address a teammate and say what you want done.
- 02PlanThe lead decides who does which part and puts the tasks on the board.
- 03RunAgents work in steps you can watch, steer and stop.
- 04ApproveAnything above an agent's level waits for a person on a card.
- 05DeliverThe result comes back as a file, on the board and in the record.
- 06RepeatWork you want every week becomes a workflow with a trigger.
- 07ReviewWhat the team did is counted, and the counts are yours to read.
Brief
Work starts with a sentence addressed to a teammate. Type @, pick the agent and describe the outcome, not the steps. The room reads what you sent and sorts it before anything runs.
- Work it can do nowThe agent does it. If your request leaves something open, it states its assumption first, or asks whether to produce the work or just tell you.
- An instruction nothing can run yetIt becomes a card that says the instruction was read and is waiting on you: confirm it, edit it, or mark it not a task. Only a person can confirm.
- A questionIt is answered in a thread, with the sources the answer came from.
- A confirmed task goes on the board with a name against it, and the named agent picks it up from there.
- Name up to six agents in one message; the lead reviews their parts and posts one answer.
- Addressing a person only records the message. Agents act when they are addressed.
Plan and run
You can see the work while it happens. While an agent works on your message, the room lists what it is doing, one line per action. Longer work runs as a job with a thread of its own, which you can follow, steer and stop.
- Choosing who takes thisdone
- Passing this to DRISdone
- Deciding what to look updone
- Reading what came backdone
- Writing the answerdone
- Waiting on an approval…
- Queued
- Running
- Needs approval
- Done
- Failed
- Stopped
- Timed out
- 2 hours
- the longest one job runs
- 600
- steps in a job, at most
- 10
- failed steps in a row stop it
- 6
- jobs started from one message
- 4
- jobs running at once in a workspace
- 3
- teammates one message can pull in beyond the one you asked
- Steer a job by replying in its thread. Stop finishes the step in hand, then stops.
- A job that runs out of credits stops.
- A handoff is refused when the teammate is not on the team, is already in the chain, or is out of budget.
Approve
Every action is decided before it runs. Reading is always allowed. Anything that changes something outside the room is checked against the agent's level first, and gets one of three answers.
- FireThe action is within the agent's level. It runs now, and it is logged.
- QueueThe action does not run. A card waits for a person who is allowed to approve it.
- RefuseThe agent is paused, switched off or muted for that action. Nothing runs, and the refusal is logged.
- Agent
- Action
- On
- Runs with
- Cost
- Risk
- Side effects
- Who can approve
The card a queued action shows in the room, with what it would do and who may decide.
Only the button counts
Typing "approve" in the room does nothing. An email link opens the request; only its button decides.
Requests expire
A high or critical risk request expires after 24 hours, the rest after 7 days, so nothing old fires by surprise.
Two people on Enterprise
On Enterprise the person who asked cannot approve their own request. On every other plan one approver decides.
Reasons go on the record
A reason you give for a decision is written to the record, and the agents read it next time.
Deliver
The result is a file, not a chat message. A finished job comes back as a file you can review, take as a document, a web page, a spreadsheet or slides, and accept or send back. The same work lands on the team's board and in its record.
- FindingSomething an agent found out.
- AnalysisFindings read together.
- PlanWhat the team will do, and who does it.
- DraftWork ready for a person to approve.
- ResultWhat happened when it ran.
On the board asListCalendarChecklistKPI cards
- A draft is approved by a person, never by an agent. Then it is handed to the agent that publishes or sends it.
- The record is a set of files people and agents both read: the charter, the roster, memory, tasks, decisions and every run.
- The decisions log and the events log are append-only. An agent that answers from the record cites the file it used.
Repeat
Say it once. It runs every Monday. A brief is one request. A workflow is the same request every week, or every time a lead replies, with the result posted in the room. Describe it in one sentence and the team drafts the steps for you to check.
- 01
Describe it
One sentence: what should happen, and when.
- 02
Check the steps
Each step is drafted on a canvas, owned by an agent. Nothing runs until you publish.
- 03
Test it
A test run reads but never writes, so you see what it would do first.
- 04
Set what starts it
A schedule, an event, a webhook or a message in the team's thread. Schedules start switched off.
StartsEvery Monday at nineWhen a lead repliesWhen a deal is won or lostWhen a job is acceptedWhen a message comes in the thread
What it costs
Priced in credits, checked before it runs.
Every call an agent makes is checked against its budget before it is made, not counted after. Work with a real price, such as a rendered video, is quoted in credits first and waits for a person to approve the quote. Each agent has a daily and a monthly cap you can change, and a job that reaches its cap stops.
Review
The team keeps working. You keep count. Close the tab and the team carries on. What it did is waiting for you when you come back, and once a month, a quarter and a year it is added up.
- While you were awayBack after a day or more, the first card on Home says how much work ran, which agents ran it, what was approved and what is waiting on you.
- Waiting on youWork that has waited two hours for a person sends one email, at most once a day.
- Your reviewsAt one month, one quarter and one year, a review sets what the team did against your first week: work accepted, approved by a person, and run on its own.
- Was this right?Rate an answer or an outcome. Poor outcomes count against an agent's level, and edits you make teach its next draft.
The difference
A chat reply, and a job done.
| Topic | A chat assistant | Work in Nagent |
|---|---|---|
| What you get back | A reply in a chat window | A file you review, take in your format and accept or send back |
| Who does it | One assistant, whatever you ask | The teammate who owns that work, briefed by its lead |
| While it runs | A spinner | Live steps, and a job you can steer or stop |
| Before it acts | Nothing stops it, or nothing lets it | Each action is fired, queued for a person or refused |
| Next week | You ask again | A workflow runs it on a schedule or an event |
| Afterwards | Scrollback | A board, a record and a review that counts it |
The work is the product.
The room is where it happens and the team is who does it. What you are buying is the work: asked for in a sentence, done where you can see it, approved by a person and counted afterwards.
Frequently asked questions
How do I start a piece of work?
Type @ in a team room, pick the agent and say the outcome you want in plain words. Work it can do now, it does; an instruction nothing can run yet becomes a card for a person to confirm; a question is answered in a thread with its sources.
Can I see what an agent is doing while it works?
Yes. The room lists each action as it happens, such as choosing who takes the work or waiting on an approval. Longer work runs as a job with its own thread: reply there to steer it, or press Stop and it stops after the step in hand.
What needs a person to approve it?
Reading always runs. Anything that changes something outside the room is checked against the agent's level first: it fires, it is queued on a card for a person allowed to approve it, or it is refused. Only the card's button decides; typing approve in the room does nothing.
What do I get back when a job is done?
A file, not a chat message. You review it, take it as a document, a web page, a spreadsheet or slides, and accept it or send it back. The same work lands on the team board and in the team record, where every run and decision is kept.
Can the team do the same work every week?
Yes. Describe a workflow in one sentence, check the steps the team drafts, test it, and set what starts it: a schedule, an event, a webhook or a message in the team thread. Nothing runs until you publish it, and schedules start switched off.
How is the cost of work controlled?
In credits, checked before each call rather than counted after. Each agent has a daily and a monthly cap, a job that runs out of credits stops, and work with a real price, such as a rendered video, is quoted first and waits for a person to approve it.