Use it
Hand a job to a team
The whole job goes out, the finished set comes back, and you can see who did what. The Content team is already installed.
One agent is one worker. A team is several, with a lead that splits the job and collects the pieces. You set the goal and hand it over; you do not chase each agent.
The shape
- You
- Set the goal and approve what leaves the machine
- Assistant
- The desk you talk to; it decides whether this is a one-agent job or a team job
- Company → department → team
- Where the work is organised. A department groups teams; a team is the set of agents that finish one kind of job
- Agent
- One worker with its own instructions, its own tool permissions and its own memory of what that job taught it
Every agent is visible: what it was given, what it handed over, and what it is waiting on. Anything that goes out — a post, an email, a file sent anywhere — waits for your approval.
Try it
- Open the officeThe Content team ships with the installer, ready to work.
- Say the job*"Cocoa launch: a shop post and a 15-second clip."*
- Watch the hand-offsWriter drafts, editor reviews, video renders — each row says who has it now.
- Approve what goes outThe post waits at your desk before it goes anywhere.
What it costs
Every agent runs on the model you connected, so a team spends more tokens than one agent — and the screen says which agent spent them. Start with a team on a cheap model and move the important seat to a better one.
Building your own
- An agent's instructions, skills and tools are per agent — one can be strict and one can be quick.
- Selling a team, a skill or an agent you wrote is allowed; see the licence in the app repository.