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
Options
| Flag | Default | Description |
|---|---|---|
--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
| Path | Purpose |
|---|---|
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.json | Agent command, artifacts dir, and pass threshold. Written only if the file does not already exist. |
pome.config.json agent command:
Typical setup flow
Examples
Related commands
| Command | Purpose |
|---|---|
pome login | Sign 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 install | Install /pome-setup and /pome-test agent skills. |
pome login options
| Flag | Default | Description |
|---|---|---|
--api-url <url> | https://api.pome.sh | Control-plane base URL. |
--dashboard-url <url> | https://app.pome.sh | App URL for Clerk sign-in. |
--key-name <name> | pome login | Label for the API key minted by this login. |
pome register agent options
| Flag | Default | Description |
|---|---|---|
--api-url <url> | https://api.pome.sh | Control-plane URL. |
--force | off | Overwrite an existing agentId in pome.config.json. |