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. A task's detail says who it went to, and flags it when the job named other agents or a specialist for that kind of work was on your roster, with the reason the coordinator gave.
- 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.
Who the coordinator calls
Name the people you want and the coordinator is held to them: "have Nadia write it and Bob check the figures". Give it no names and it matches each task to an agent from the strengths on your roster, preferring a specialist to the general worker. Agents covers why those few lines matter.
It chooses only from the agents that belong to the job's project, so an agent you have not added to that project gets no tasks from it. Add one on Manage > Project > Agents (/project/agents). It also only hands work to agents that can take it: customer-facing sandboxed agents, the memory agent and the relay agent are never given a task, and your main assistant is not used as a worker. If it does assign a task to someone you did not name, the task's detail says so and why.
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. |
| Worker active | A specialist is running right now and the coordinator is waiting for its report. Same as above: nothing 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 job, Resume job and Close job are in the job's three-dot menu, each offered only when it will work: a live job can be stopped or closed, a stopped or parked one resumed, and a job waiting on your answer offers no Resume until you give it. Stop asks you to confirm, and a card reading Job cancelled appears in the chat the job reports to. 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.
Delete job, in the same menu, removes the job with its tasks, runs, messages and activity. It refuses while a run is still active, so stop the job first. The job's folder is kept if the team wrote anything in it.
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
Dashboard > Jobs (/jobs) lists your jobs, with tabs for All, Active, Needs input, Paused, Completed, Failed, Cancelled and Archived. The search box in the page's header row filters whichever tab you are on. The list follows the project chosen at the top of the sidebar, and All projects widens it to everything.
The Dashboard itself (/dashboard) is the wider view: jobs, flows, scheduled tasks and agents together, with what is running now on top and what finished in the last 24 hours below. Each row is a progress bar, and two dropdowns, Status and Kind, narrow it. It answers "what is my installation doing on its own right now" in one screen. Apart from stopping an agent's run or a job, it is a view rather than a control panel, so acting on a row takes you to the thing behind it.
While jobs are running, a briefcase with the count sits in the status corner at the top right, and on a phone it is a round button there. It opens the active jobs.
Creating a job needs a project chosen, and a job belongs to one project at a time.