Developer docs Guides
Publish & fork
Package a running team into a versioned template, share it on the community, or fork someone else’s team into your own workspace.
What ships in a template
Publishing packages the four configuration entities of a project into an immutable, versioned template:
| Included | Not included |
|---|---|
| Meta-task definitions — script, params schema, phases | Execution history and logs |
| Agent roster — model, tools, skills | Workspace files |
| Cron schedules | Custom Docker images |
| Background service definitions | Task memories |
Publishing
Publishing snapshots the current configuration as a new template version. Versions are immutable — change the team and publish again, and the new state becomes the next version while old versions stay intact.
Forking
- Forking rebuilds the four entities in your own workspace — configuration only, everything else starts empty
- Every entity gets a fresh id, and internal references (an agent on a task, a task type on a cron) are remapped automatically
- Your fork’s runs, schedules, and memories are yours alone — the source team is never touched
The community
Published teams are browsable in the community portal. Star the ones you find useful, fork to run your own copy, and join the threaded discussion attached to each team.