Jobs

A job is a piece of work too big for one conversation. It has your brief, a plan, a team of agents, phases that run in order, and a record of everything that happened.

You never ask for a job as such. You ask for the work: "research what our four competitors charge, work out where we sit, and write me a report for the board." One agent, the coordinator, takes the brief, splits it into tasks, picks the right specialist for each and keeps the plan up to date. The coordinator plans and checks; the specialists do. You get your conversation back straight away and the job carries on without you.

Give it work shows where a job sits among the smaller shapes, and Create your first job walks one through.

What a job page shows

Open a job and it has six tabs.

• Team lists the coordinator and every specialist on the job. Open one to read that agent's own conversation.
• Tasks is the board: Pending, In Progress and Finished, grouped by phase, with every finished task carrying its outcome (Done, Failed, Dropped or Cancelled). Open a task for its detail, or retry one that failed.
• Plan is the coordinator's living plan, rewritten as the job goes, with a count of phases planned, pending, active, done and failed.
• Files is the job's own workspace.
• Messages is the team's own traffic, including anything addressed to you.
• Activity is the audit trail: every change, in order, with a timestamp.

The page updates live, so you can leave it open and watch. A seventh tab, Projects, moves the job to another project.

What state it is in

A badge says what the job is doing, and the list groups jobs by the same thing.

State	What it means for you
Working now	The team is on it. Nothing for you to do.
Needs input	It has asked you a question and stopped until you answer.
Needs attention	It could not sort itself out and wants a decision from you.
Recovering	It noticed something had stalled and is restarting that piece itself.
Paused	Open, but nothing running this moment.
Completed	Finished. "Completed with failures" means finished, but some tasks did not.
Cancelled	You stopped it. The work is kept, not destroyed.
Archived	Tucked out of the way.

How it asks you

When a job hits a decision only you can make, it parks itself rather than guessing. An amber card appears in your chat with a short summary, the numbered questions and a link straight to the job. Answer in that chat in your own words and the coordinator picks up where it left off. The same question sits in a banner on the job page until you deal with it.

The card lands in the conversation the job is talking to: the chat you started it from, until you answer or restart it somewhere else, and that chat becomes where it reports back. Where else the platform reaches you is yours to set on Admin > Alerts (/admin/alerts).

If you want the plan agreed before anything happens, say so when you brief the work. Held phases wait on the Tasks board with a Review Plan button: Approve lets it run, Reject asks you for a reason, and that reason goes back to the coordinator so the next version is better.

Stop, Resume and Close job are on the job page; Stop asks you to confirm. Stopping is a pause rather than a delete: resuming brings back the phases, the tasks, the team and the workspace as they were, and takes about half a minute to get moving. It also returns before the team has downed tools, so trust the board over the confirmation. A job that looks frozen is sometimes waiting for capacity from your AI provider, and will pick itself up.

Its own workspace

Every job gets a shared folder its team works in, and that is where drafts, research and finished files land. Browse it on the Files tab. It stays after the job ends, so a report from three months ago is still where the team left it. See Workspaces and files.

Where it lives

Automations > Jobs (/jobs) lists your jobs, with tabs for All, Active, Needs input, Paused, Completed, Failed, Cancelled and Archived. The search box in the top bar filters whichever tab you are on.

Automations > Active (/automations) is the wider feed: jobs, flows and scheduled tasks together, newest first. It answers "what is my installation doing on its own right now" in one screen. It is a view, not a control panel, so acting on a card takes you to the thing behind it.

Creating a job needs a project chosen, and a job belongs to one project at a time.