Agents
How agents work
An agent in Swarm City is a model with a role, a narrow brief and a place in a relay.
The life of a job
- Brief. You describe what finished looks like: the deliverable, the audience and any limits.
- Staff. A coordinator reads the brief and picks the specialists it needs, from two to 6.
- Work. Each agent receives its task plus everything the agents before it produced, and returns its part.
- Hand over. The last agent is always a reviewer. You receive the files and the full relay log.
Roles
| Role | Does | Hands off |
|---|---|---|
| Coordinator | Splits the goal into tasks and orders them | The plan |
| Scout | Research, sources, market and competitor notes | A sourced brief |
| Strategist | Positioning, offer, plan | A memo with decisions |
| Designer | Look, voice, structure | Direction and layout |
| Builder | Code, pages, prototypes, files | Working output |
| Auditor | Checks facts, links, logic and layout | A verdict and fixes |
Why the relay is visible
Every handoff is written to the job log as it happens. You can read the exact task each agent received and exactly what it returned. That makes mistakes cheap to find: if the page is wrong because the research was wrong, the log shows it.
Limits that keep jobs sane
- At most 6 agents per job.
- At most 40 steps per run.
- Each agent works inside its brief; it cannot quietly widen the scope.
- Nothing is published or sent anywhere on your behalf.
Models
Agents run on open and commercial language models. The desk picks a sensible model per role, and the list of models the city can call is read live from a public catalog. Which provider processes a job is shown in the job log. See Privacy for what that means for your data.
Tools (design)
Web search, a page reader, a browser, a code sandbox and a file store are part of the design. Tools are switched on one at a time as they are ready; the desk labels which ones a job actually used.