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 to Sapiom	A forked Git repository cloned to your machine, plus local sapiom.json provenance.
Bundled starter	Sapiom sign-in; no Sapiom capability request	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 attempts dependency installation. The fallback versions let project creation finish when npm lookup is unavailable; they do not make dependency preparation 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 your selected coding agent in the destination and asks it to create the project. If you are signed out, it opens Sapiom sign-in before retrying the live-gallery action.

   Coding agent

   First connect Sapiom MCP to Claude Code or Codex. Start the coding agent in an empty destination and ask:

   Sign me in to Sapiom if needed, then create a project here from the live Hello Agent template. Read its AGENTS.md and README.md before making any changes.

   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. Prepare and verify locally

   Ask your coding agent:

   Read this project’s package-manager metadata, get its dependencies ready, check the full agent project, then run it locally with name set to world.

   The coding agent handles setup and typechecking as part of reaching that outcome. You do not need to run package-manager or validation commands yourself.

   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 the coding agent to create the project, install dependencies, and read AGENTS.md.

Coding agent

Start Claude Code or Codex in an empty destination and ask:

Create the bundled default Sapiom starter in this directory, install its dependencies, and read AGENTS.md before changing it.

Substitute coding-pause for the dispatch-and-resume starter. The starter source is local, but using Sapiom MCP to scaffold it still requires Sapiom authentication.

The scaffold writes the project, an empty .sapiom-dev/stubs.json, a valid unlinked sapiom.json, the local authoring skill, and a best-effort initial Git commit. It also attempts dependency installation and reports dependenciesInstalled. If that field is false, let the coding agent repair setup before the full check; do not recreate an otherwise valid scaffold.

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.