Agents
Edit root agents
Agents are defined at three levels. A project can use the union of your root agents, its organization's agents and its own. Every agent except the assistant works inside one organization.
assistantroot●workingWorks acrossOne shared memory. Talks with you and hands each organization's work to its chief; it does not direct agents, create tasks or launch sessions.
rootYour root configuration. Only you change it. Each organization runs its own copy, with memory, files and credentials kept in that organization.
Distinctly Digital–idlereviewer copy–idleresearcher copy
Forge▲errorreviewer copy–idleresearcher copy
Home–idleresearcher copyreviewer turned off for Home
orgDefined in the organization file. The chief hires and fires here; you can override any setting.
Distinctly Digital–idlechief●workingcopywriter◐waitingeditor●workingmontage-producer
Forge–idlechief●workingcoder
Home–idlechief–idleplanner
projectDefined in one project and available only there. The chief hires and fires here too.
Distinctly Digital–idlesocial-scheduler Spring launch–idlecontinuity-checker The Lantern Coast
Forge–idleload-tester API gateway
Homenone
Available in a project
Spring launch| Agent | Level | Status |
|---|---|---|
| assistant | root | ●working |
| reviewer | root | –idle |
| researcher | root | –idle |
| chief | org | –idle |
| copywriter | org | ●working |
| editor | org | ◐waiting |
| montage-producer | org | ●working |
| social-scheduler | project | –idle |
Not available here: continuity-checker (The Lantern Coast only) and every Forge or Home agent.
Who changes what
root You add, change and remove root agents. The chief cannot.
org project The chief hires and fires to meet your needs, within the role rules. Each hire lands in the trail.
override You can change any agent's settings at any level, at any time. An override shows where it was set.
Changing an agent's model is a trailed human action, applied to its running session on reload.