The usual sequence
1
create_template
Create a draft from a title.
2
update_template
Write the copy and set the pricing.
3
plan_template_capture
Dry run the capture and read what it would ship.
4
capture_template_agents
Archive the coworkers into the template.
5
add_template_image
Add the cover.
6
get_template
Read
submitChecklist and fix what is missing.7
submit_template
Hand it to the Rerun team.
list_templates
Lists the templates this account authors, withtemplateId, slug, title, status, pricing, how many coworkers are captured, and why a template is no longer editable when it is.
Takes no arguments. Call it first: every other template tool takes the templateId it returns.
Statuses are draft (yours, editable), in_review (handed over, frozen), published and unlisted (live, maintained by Rerun from then on), and archived.
get_template
One template in full: the editorial document, the coworkers already captured with theirkey, and submitChecklist, the exact list submit_template enforces with met true or false per item, plus readyToSubmit and missing.
Read it before every update. update_template only touches the fields you pass, so this is how you know what is already written.
create_template
Creates an empty draft.The product name of the template, 50 characters maximum, for example
Inbound lead qualifier.submit_template hands it over and the team approves it.
update_template
Writes the editorial page of a draft. Only the fields you pass change.The audience the template is for, not the team that built it. One of
agencies, ecommerce, saas, sales, recruiting, real-estate, legal, creators, productivity, other.Replaces the whole FAQ. Each entry needs
question and answer. Four to six entries reads best, written the way someone types them into a search box.Search snippet, 120 to 155 characters. Required in that range before the template can be submitted.
Cents.
0 when free, at least 500 ($5) when paid, up to 200000 ($2,000). Any other combination is refused rather than silently stored.submit_template
Hands a draft to the Rerun team for review. It enforces the listget_template returns: a title, a tagline, a description, a meta description of 120 to 155 characters, at least one captured coworker, an install answer for every coworker, and for a paid template a Stripe account that can actually receive payouts. No image is required: the cards draw the board of the captured coworkers. It names what is missing instead of half-submitting. It also refuses on a credential found anywhere in the copy.
Once it succeeds the template is frozen: still private, no longer editable. withdraw_template is the only way back to a draft.
Payout onboarding cannot happen from here. It needs a browser: in the Rerun app, board toolbar, My templates, Payouts.
withdraw_template
Takes a template back from review into draft so it can be edited again. Only works while it isin_review. Once published, the page is maintained by Rerun and this is refused.
delete_template
Permanently deletes a draft. Refused on a template in review or already published.list_capture_sources
Lists the Boxes and coworkers that can be captured: the sandbox only, and only coworkers the engine actually knows about. Takes no arguments. The coworker ids it returns are whatplan_template_capture and capture_template_agents take.
plan_template_capture
Dry run. Inspects what capturing these coworkers would ship, without writing anything. Returns, per coworker: its skills, scheduled tasks and declared apps, the.env key names a copy will have to be given again (names only, never values), the MCP servers whose sign-in stays behind, how many memory files it holds, what the engine will redact on the way out, and excludedByDefault, the paths considered too personal to publish.
Read this before capturing. It is the security review, and the archive ends up behind a public install button.
capture_template_agents
Captures coworkers from the sandbox into the template: prompt, skills, scheduled tasks, app declarations and workspace files are archived, and the template page is rewritten from what the folder actually contains.One entry per coworker. Each entry needs
agentId and may carry exclude, keep and setup.Paths from
excludedByDefault to ship anyway. A deliberate act: these are memories and credentials.The answer to “does this coworker need to be configured after install?”, which a template cannot be submitted without.
required is mandatory. prompt is required when required is true, and is addressed to the coworker, not to the user.keep. Do not keep a memory folder without the account owner asking for it. The coworker database, data/agent.db, is not excluded by default: its tables ship with their rows, so clear the test rows first or name it in exclude.
Re-capturing a coworker already in the template updates its entry in place, and the editorial copy written about it survives. Read the warnings that come back: they name literal credentials the engine had to strip.
remove_template_agent
Removes a captured coworker from a template and deletes its archive. Apps no remaining coworker uses leave the page with it.add_template_image
Adds one image to the gallery from a URL that is already hosted somewhere public. The bytes are downloaded and re-encoded into Rerun storage, so the gallery never points at a host that can expire or swap the picture after the review. Unlikeupdate_template(gallery) this appends: the images already there are kept.
There is no upload and no image generation here. Produce or host the image elsewhere, then pass its https URL.