Overview
The CLI is the most direct interface to the pipeline. Every operation available through the IDE and web interface has a CLI equivalent, making it suitable for automation, CI/CD pipelines, and scripted workflows. The CLI is installed alongside the SDK and authenticates through the same credentials.
Core Commands
ludopoly generate
Creates a new package from a natural language description or specification file. The command accepts inline descriptions, file-based specifications, or a combination of both.
Flags:
--chain <chain>— Target blockchain (default: ethereum)--platforms <list>— SDK output platforms, comma-separated (default: typescript)--security <level>— Audit depth: basic, standard, comprehensive (default: standard)--output <dir>— Output directory (default: ./ludopoly-output)
ludopoly translate
Converts an existing contract to one or more target languages. Accepts a source file or a deployed contract address.
ludopoly compose
Combines multiple packages into a unified application, resolving dependencies and interface conflicts.
ludopoly deploy
Deploys a generated package to the specified chain and network.
The --dry-run flag simulates deployment without broadcasting a transaction, reporting estimated gas costs and potential issues.
ludopoly audit
Retrieves the audit trail for a pipeline run. Each run is identified by a unique run ID displayed at the end of execution.
Configuration
The CLI reads project configuration from ludopoly.config.yaml in the current directory. Global defaults can be set through ludopoly config set:
All CLI commands support a --verbose flag that streams the agent swarm's decision log to the terminal in real time. This is particularly useful for debugging unexpected outputs or understanding why the security agent vetoed a particular approach.
CI/CD Integration
The CLI is designed for non-interactive environments. Authentication in CI pipelines uses a service token set through the LUDOPOLY_TOKEN environment variable. Combined with the --non-interactive flag, the CLI runs without prompts — failing fast on any issue that would normally require user confirmation.