CLI reference
wt is the WonderTwin command-line. One binary, four surfaces: twin lifecycle, discovery, requests, and diagnostics.
This page is the canonical list. Per-command detail pages will land as the CLI’s surface area expands; for now the help text (wt <command> --help) is the source of truth for flags and output shapes.
Twin lifecycle
Section titled “Twin lifecycle”Start, stop, and inspect twins on a local machine or CI runner.
| Command | What it does |
|---|---|
wt up [<vendor>...] | Start configured twins. With no args, reads wondertwin.json and starts every twin declared there. With vendor names, starts only those. |
wt down [<vendor>... | --all] | Stop running twins. With vendor names, stop those; --all stops everything. |
wt status | Print what’s currently running, on which ports, and drift state for Pro twins. |
npx wondertwin init <vendor> | One-shot bootstrap — initialize a wondertwin.json with the named vendor’s defaults. |
See Your first twin for a complete declare → activate → point walkthrough.
Discovery
Section titled “Discovery”Browse the catalog, scan your project for SDKs that need twinning, and acquire access. New in v0.1.0 — see the release notes.
| Command | What it does |
|---|---|
wt catalog | Browse the full WonderTwin catalog. Search by name, filter by category or tier. |
wt catalog --mine | See what your org has — installed, entitled, and available. |
wt catalog <name> | Detail view for a specific twin — API coverage, endpoint count, SDK language, auth pattern, webhook support. |
wt scan | Detect project dependencies (parses go.mod and package.json) and match against the catalog. Shows whether a twin exists and what action is available. |
wt subscribe <twin> | Acquire access to a twin. Backend resolves the outcome based on org state and policy: already entitled, subscribed, trial started, upgrade required, or approval requested. |
Requests
Section titled “Requests”Signal demand for twins that don’t exist yet. Pro orgs get structured request tracking; community users get a GitHub-issue link.
| Command | What it does |
|---|---|
wt request <service> | Request a twin that doesn’t exist yet. Deduplicated server-side; feeds WonderTwin’s build prioritization. |
wt request --list | Check the status of requests you’ve submitted. |
Diagnostics
Section titled “Diagnostics”| Command | What it does |
|---|---|
wt --version | Print the installed CLI version. |
wt --help, wt <command> --help | Help text for the CLI or a specific subcommand. |
MCP tools
Section titled “MCP tools”Six discovery commands above are also exposed as MCP tools for agent frameworks that require structured JSON over a tool-call protocol: wt_catalog, wt_catalog_detail, wt_subscribe, wt_request, wt_request_list, wt_scan. The MCP surface mirrors the CLI surface; same behavior, different transport.
What’s next
Section titled “What’s next”- Install the CLI if you haven’t already
- Your first twin for the canonical declare → activate → point walkthrough
- v0.1.0 release notes for the Agent Twin Discovery commands