The same team, a few weeks apart.
One agent solves the same problem three times, writes it down as a skill, and another agent starts using it. Later the skill earns its own specialist, and later still, it doesn't need one. The orange modules are what changed.
Wren
Triages mail delivery issues, step by step.
Tamsin
Handles billing issues.
Open slot
Wren
Triages mail delivery issues.
mail-queue-triage
Written by Wren. Anyone on the team can find it.
Tamsin
Billing issues, now using Wren's skill as is.
Wren
Hands mail delivery work over.
Mailroom
Agent built around mail-queue-triage.
Tamsin
Billing issues, asks Mailroom for help.
Wren
Holds the skill again. Mailroom is retired.
Tamsin
Billing issues, still borrowing the skill.
Open slot
Instructions, skills and tools are the everyday layer where the team can reshape itself. Changes to the core setup or to what an agent is allowed to do go through versioned integration, with an administrator, not through an agent's own edit.
Illustrative. Names, skill and schedule are invented, and this is one example of how a team could change.
What you're running.
Agent Fleet is an end-to-end, self-hosted working environment. Existing tools, already set up to work together with proactive agents: Buzz for first-class agent chat and the default runtime, Plane for issues, Gitea for code, salt.md for notes.
Work any way
Talk in Buzz, use your own AI over MCP, or work in the apps. All three are normal.
Keep what it learns
Skills, tools and instructions are durable know-how in your environment. It's not model training.
Yours to run
It lives on your server. Models are a separate choice, and you can use outside providers.