Create from a template

Choose a template source based on what you need:

Source	Requirements	What it creates
Live gallery	Sapiom sign-in and network access	A forked Git repository cloned to your machine, plus local sapiom.json provenance.
Bundled starter	No Sapiom account	A new project copied from the default or coding-pause starter shipped with Agent Core.

The live gallery is not a fixed-size catalog. Agent Studio reads the current catalog from Sapiom. If that request is unavailable, Studio labels the degraded state and still offers the two bundled starters.

Setup can use the network

“Bundled” describes where the starter source comes from. Scaffolding can check npm for current package versions, and npm install downloads dependencies. The fallback versions let scaffolding finish when npm lookup is unavailable; they do not make dependency installation network-free.

Start from the live gallery

The following path uses Hello Agent, the smallest current gallery template. It has one terminal step, no Sapiom capability calls, and accepts an optional name.

1. Choose and materialize the template

   Agent Studio

   Open Add Workspace → Start from a template. Choose Hello Agent, select an empty destination, and choose Use template, then Start session.

   Studio starts Claude Code in the destination and asks it to call the local authoring MCP. If no Sapiom credential is available, Claude asks you to complete sapiom_authenticate before retrying the clone.

   Claude Code with MCP

   Connect the authoring MCP if needed:

   claude mcp add sapiom -- npx -y @sapiom/mcp

   Ask Claude to call sapiom_authenticate, then call sapiom_dev_agents_clone with:

   {
     "dir": "/absolute/path/to/hello-agent",
     "templateId": "hello-agent"
   }

   A templateId clone creates a per-fork repository you own and checks it out with a short-lived, repository-scoped read credential. The credential is used for Git clone and discarded; it is not written to sapiom.json.

2. Read the project before changing it

   Open AGENTS.md and README.md. The checked-out source is the template’s real Git repository. The clone tool then writes sapiom.json locally with fork and template provenance so Studio can discover the folder as an agent project.

   A clone is source, not a deployed agent

   Forking and cloning do not create an engine definition and do not add a runnable agent to the dashboard. The project crosses that boundary later, when you link and deploy it.

   Because sapiom.json is written after the repository checkout, it can appear as untracked in a fresh clone. Keep it: it is the project’s team-shared identity and contains no clone credential.

3. Install and verify locally

   From the cloned folder, run:

   npm install
   npm run typecheck

   Then ask Claude to call:

   { "dir": "/absolute/path/to/hello-agent" }

   with sapiom_dev_agents_check, followed by the same arguments with sapiom_dev_agents_run_local.

   The verified zero-input result reaches greet with { "name": "world" } and completes with:

   { "greeting": "Hello, world!" }

Start from a bundled starter

The bundled choices are deliberately small:

Starter	Graph	Use it for
default	start → finish	A minimal typed agent with an entry default and terminal result.
coding-pause	prepare → kickoff ⇢ finalize	Repository handles, non-blocking models.coding.launch, pause, resume, and sandbox reattachment.

Agent Studio

Open Add Workspace → Start from a template. Under Bundled starters, choose a starter, choose an empty destination, and start the session. Wait for Claude to finish sapiom_dev_agents_scaffold, npm install, and its read of AGENTS.md.

Claude Code with MCP

Ask Claude to call sapiom_dev_agents_scaffold:

{
  "dir": "/absolute/path/to/my-agent",
  "template": "default"
}

Change template to coding-pause for the dispatch-and-resume starter. No Sapiom account is required for this tool.

The scaffold writes an npm-install-ready project; it does not install packages. It also writes an empty .sapiom-dev/stubs.json, a valid unlinked sapiom.json, the local authoring skill, and a best-effort initial Git commit. Run npm install before the full check.

Destination rules

Use a new or empty destination. Agent Studio may already have created its real, private .sapiom/ directory; scaffold and clone preserve exactly that reserved directory. Any other existing entry is rejected, and a cloned repository that owns .sapiom/ is rejected rather than merged with Studio state.

Build Turn the template into your own typed step graph and run the full check.

Test locally Execute real step code against built-in or project stubs and read the trace.