Skip to main content
pome init creates the local project layout Pome expects: scenarios/, examples/agents/, runs/, and pome.config.json. Run it once per agent project before your first pome run. Hosted runs also require pome login and pome register agent <name> to link runs to a cloud agent on the dashboard.

Usage

pome init [options]

Options

FlagDefaultDescription
--sdk <name>Scaffold for a specific agent SDK. Supported values: claude, claude-managed. Both are gated on upcoming npm publishes — the command prints a deferral message and exits without writing files.

What it creates

PathPurpose
scenarios/Your scenario markdown files (copy from the bundled library with pome scenarios <twin> --copy).
examples/agents/Example agent implementations.
runs/Default artifacts directory for pome run.
pome.config.jsonAgent command, artifacts dir, and pass threshold. Written only if the file does not already exist.
Default pome.config.json agent command:
npx tsx examples/agents/scripted-triage-agent.ts

Typical setup flow

pome init
pome login
pome register agent my-triage-bot
pome scenarios github --copy
pome run scenarios/01-bug-happy-path.md

Examples

# Basic scaffold
pome init

# Attempt Claude SDK scaffold (deferred until adapter publishes to npm)
pome init --sdk claude
CommandPurpose
pome loginSign in and store a pme_… API key (Keychain or ~/.pome/credentials.json).
pome register agent <name>Create a cloud agent; writes agentId and agentSlug to pome.config.json. Both keys are load-bearing — do not hand-edit them.
pome skills installInstall /pome-setup and /pome-test agent skills.

pome login options

FlagDefaultDescription
--api-url <url>https://api.pome.shControl-plane base URL.
--dashboard-url <url>https://app.pome.shApp URL for Clerk sign-in.
--key-name <name>pome loginLabel for the API key minted by this login.

pome register agent options

FlagDefaultDescription
--api-url <url>https://api.pome.shControl-plane URL.
--forceoffOverwrite an existing agentId in pome.config.json.