Skip to content

Quickstart

Terminal window
npm install -g spawnfile

Verify:

Terminal window
spawnfile --version
spawnfile --help
Terminal window
spawnfile init

This creates a Spawnfile manifest and starter markdown docs in the current directory. The generated docs (SOUL.md, IDENTITY.md, AGENTS.md) are tailored to the selected runtime’s personality and capabilities:

my-agent/
|-- Spawnfile
|-- IDENTITY.md
|-- SOUL.md
\-- AGENTS.md

To scaffold for a specific runtime:

Terminal window
spawnfile init --runtime tinyclaw

Open Spawnfile and set your agent’s name and runtime:

spawnfile_version: "0.1"
kind: agent
name: my-assistant
runtime:
name: openclaw
workspace:
docs:
identity: IDENTITY.md
soul: SOUL.md
system: AGENTS.md
environment:
env:
LOG_LEVEL: info
execution:
model:
primary:
provider: anthropic
name: claude-sonnet-4-5
auth:
method: claude-code
sandbox:
mode: workspace

Edit the markdown docs:

  • SOUL.md — personality, voice, tone
  • IDENTITY.md — who the agent is, self-description
  • AGENTS.md — operating instructions and conventions

These are plain markdown files. The runtime loads them into the agent’s context.

Terminal window
spawnfile validate

This checks the manifest schema, file references, and graph structure without compiling.

Terminal window
spawnfile view .

This is read-only and writes no files while showing the resolved project graph.

Terminal window
spawnfile compile

The compiler emits runtime-native config and workspace files:

.spawn/
|-- runtimes/
| \-- openclaw/
| \-- agents/
| \-- my-assistant/
| |-- openclaw.json
| \-- workspace/
| |-- IDENTITY.md
| |-- SOUL.md
| \-- AGENTS.md
\-- spawnfile-report.json

Once compiled, you can build a Docker image and run it with auth:

Terminal window
spawnfile auth sync --profile dev --env-file .env
spawnfile build --tag my-assistant
spawnfile run --tag my-assistant --auth-profile dev

See Docker Packaging for the full build and auth workflow.