Publishing & forking
Templates aren’t just something you install — they’re something you create and share. This page covers the three author-side actions: capturing a template, publishing it to the marketplace, and forking an existing one.
Capturing a template from an agent
Section titled “Capturing a template from an agent”Once you’ve shaped an agent you like, you can turn it into a template. Capturing takes a snapshot of the agent — its persona files, its set of integrations, and its workspace files — and saves it as a new template you own.
Capture copies the important parts of the agent’s setup, but never your private credentials. The template records which integrations the agent uses, so anyone who installs it will be prompted to connect their own accounts. Your secrets stay yours.
Captured templates are private to your organization by default. Nothing is shared until you decide to publish.
Versioning
Section titled “Versioning”Templates are versioned. Every time you capture new changes, a new version is recorded, and older versions remain available. Agents that installed an earlier version keep running as they were — updating a template doesn’t reach back and change agents that were already created from it.
Publishing to the marketplace
Section titled “Publishing to the marketplace”Publishing makes a template public so others can find and install it from the marketplace. Published templates appear in browse and search alongside the built-in team templates, and they accumulate signals like install counts and likes so useful templates rise to the top.
A few things to know about publishing:
- A public name is unique. Each public template has its own key, and a key can only be claimed publicly by one author. If a name is already taken, pick another.
- You can unpublish. Making a template public isn’t permanent — you can pull it back to private.
- Visibility is yours to control. Templates can be private (just your organization), public (in the marketplace), or unlisted.
Forking a template
Section titled “Forking a template”Forking makes your own editable copy of an existing template. Where installing creates a running agent, forking creates a template you own — so you can change the persona, swap integrations, and build on someone else’s work instead of starting over.
A fork is a true copy: the files come with it, so your fork keeps working even if the original changes or is removed.
Attribution
Section titled “Attribution”Every fork remembers where it came from. A forked template shows a “Based on [original] by [author]” credit, so the original author is always acknowledged — this stays with the fork regardless of what you do with it.
Republishing a fork
Section titled “Republishing a fork”Whether you can publish your fork back to the marketplace depends on the original author’s license setting:
- By default, a published template does not allow forks to be republished. You can still fork it for your own private use — you just can’t put your fork back into the marketplace.
- If the author opted in to allowing fork republishing, you can publish your fork (with the attribution credit intact).
This lets authors share their work publicly while keeping control over whether derivatives get republished. When you publish your own template, you choose which setting applies to it.
Choosing between install and fork
Section titled “Choosing between install and fork”| You want to… | Use |
|---|---|
| Get a working agent right now | Install |
| Customize a template and keep it as a template | Fork |
| Share your own agent’s setup with others | Capture, then publish |
Next steps
Section titled “Next steps”- Templates overview — how snapshots, versioning, and the marketplace fit together.
- Persona files — what you’re editing when you refine a forked or captured template.