Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pome.sh/llms.txt

Use this file to discover all available pages before exploring further.

The pome binary is how you run scenarios against a digital twin, inspect run traces, manage active sessions, and authenticate with the hosted control plane. Every workflow — from local OSS development to CI pipelines targeting the hosted cloud — goes through this single binary.

Installation

Install pome globally with your preferred package manager:
npm install -g pome
Verify the installation:
pome version

Global flags

These flags apply to every pome command and can be placed anywhere on the command line.
FlagDefaultDescription
--config <path>.pome.jsonOverride the config file path. The CLI normally walks up from the current directory to find .pome.json.
--output <fmt>terminalOutput format. terminal renders human-readable output; json emits machine-readable JSON.
--quiet / -qfalseSuppress all non-error output. Useful in scripts where you only care about exit codes.
--verbose / -vfalseWrite debug logs to stderr. Equivalent to setting POME_DEBUG=1.
--api-url <url>https://api.pome.shOverride the cloud API base URL. Use this for self-hosted deployments or staging environments.
--no-colorfalseDisable ANSI color output.

Commands

CommandWhat it does
pome initScaffold a new Pome project with config, harness, and example scenarios
pome loginAuthenticate with the hosted Pome control plane
pome logoutRemove stored credentials
pome runRun one or more scenarios against a twin
pome inspectPretty-print a run’s full trace
pome exportExport a run as a .tar.gz archive
pome twinBoot a standalone twin for manual testing
pome sessionsList or kill active hosted sessions
pome versionPrint the CLI version
See the command reference for full flag documentation, exit codes, and examples for every command.