wonda-cli
installsforks
How to install wonda-cli?
degausai/wonda/wonda-cli
$npx -y skills add degausai/wonda --skill wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automation
SKILL.md
| 1 | # Wonda CLI |
| 2 | |
| 3 | Wonda CLI is a content creation toolkit for terminal-based agents. Use it to generate images, videos, music, and audio; edit and compose media; publish to social platforms; and research/automate across LinkedIn, Reddit, and X/Twitter. |
| 4 | |
| 5 | ## Install |
| 6 | |
| 7 | If `wonda` is not found on PATH, install it first: |
| 8 | |
| 9 | ```bash |
| 10 | # npm |
| 11 | npm i -g @degausai/wonda |
| 12 | |
| 13 | # Homebrew |
| 14 | brew tap degausai/tap && brew install wonda |
| 15 | ``` |
| 16 | |
| 17 | ## Setup |
| 18 | |
| 19 | - **Auth**: `wonda auth login` (opens browser, recommended) or set `WONDA_API_KEY` env var |
| 20 | - **Verify**: `wonda auth check` |
| 21 | |
| 22 | ### OAuth connector auth |
| 23 | |
| 24 | Claude web and Cowork connectors use Wonda's OAuth 2.1 flow instead of a CLI |
| 25 | API key field. The connector signs in through Wonda in the browser, grants the |
| 26 | requested account access, and receives OAuth tokens bound to the Wonda API |
| 27 | resource. The server swaps those tokens to the account's internal API key only |
| 28 | inside Wonda, so agents and connector hosts never see the `sk_...` key. For the |
| 29 | CLI and local stdio MCP path, keep using `wonda auth login` or |
| 30 | `WONDA_API_KEY`. |
| 31 | |
| 32 | ### Claude Cowork local relay |
| 33 | |
| 34 | Claude Cowork (the desktop app) runs local MCP servers on the host, so it can |
| 35 | load the `.mcpb` bundle or a local stdio `wonda-mcp` config directly, WAB |
| 36 | writes included (verified 2026-07-07). Claude web cannot. The Wonda local |
| 37 | relay is the alternative path: it lets the REMOTE connector (web or Cowork) |
| 38 | run actions on the user's own Mac and residential IP without any local MCP |
| 39 | config: |
| 40 | |
| 41 | 1. Open `https://wonda.sh/download` while signed in and install the notarized |
| 42 | Mac package. |
| 43 | 2. Pair the relay with `wonda relay pair` or the first-run browser handoff. This |
| 44 | uses the existing `cli-auth` flow with a relay-scoped `wrelay_...` |
| 45 | credential stored in the macOS Keychain. Do not ask the user to paste an API |
| 46 | key or device code. |
| 47 | 3. Open `https://wonda.sh/setup`, connect LinkedIn, X, and Reddit through the |
| 48 | headful local WAB, then approve the Wonda connector once in Claude. |
| 49 | |
| 50 | The engine policy is `auto | my_machine | cloud`. `auto` uses the local relay |
| 51 | when it is online and cloud otherwise. `my_machine` must not silently fall back: |
| 52 | if the relay is offline, ask whether to switch to cloud. |
| 53 | |
| 54 | ### Organizations & spend context |
| 55 | |
| 56 | Wondercat orgs are shared wallets with their own seats and billing. |
| 57 | Members can spend from the org wallet (instead of their personal credits) |
| 58 | by switching context: |
| 59 | |
| 60 | - `wonda organizations list` (aliases: `wonda orgs list`, `wonda org list`) — see every org you belong to with your role and seat plan in each. |
| 61 | - `wonda use --org <slug>` — sticky org context for this machine. Sets |
| 62 | `X-Wonda-Org` on every request; holds, charges, and `wonda balance` |
| 63 | route through the org wallet. |
| 64 | - `wonda use --personal` — back to personal. |
| 65 | - `wonda usage` — spend-only usage summary (total + per-model + per-project |
| 66 | breakdown) for a period (`--month 2026-05`, or `--from`/`--to`; defaults |
| 67 | to the current month, UTC). `--project <name>` restricts the report to one |
| 68 | project. In org context it reports org-wide usage including a per-member |
| 69 | breakdown — admin/owner role required. Admins can also download a full |
| 70 | Excel report from the org page on the web. |
| 71 | |
| 72 | ### Projects (spend tagging) |
| 73 | |
| 74 | Projects attribute spend to a named workstream for monitoring. Agents |
| 75 | should check the active project at task start (`wonda use` prints it) and |
| 76 | set one per task when the operator monitors spend by project: |
| 77 | |
| 78 | - `wonda use --project <name>` — sticky: every subsequent charge carries |
| 79 | the project (in `wonda usage`, the API, and the org Excel report). |
| 80 | `wonda use --no-project` stops tagging; switching org/personal context |
| 81 | clears the project automatically (projects are per-scope). |
| 82 | - `--project <name>` on any command — one-off override for that invocation. |
| 83 | - `wonda project list|create|delete` — manage the registry in the active |
| 84 | scope. Org projects are created by org admins/owners only; personal |
| 85 | projects are self-service. Tagging against a name that doesn't exist |
| 86 | fails with `unknown_project` (no silent new buckets, so typos can't |
| 87 | split the monitoring data). |
| 88 | |
| 89 | `wonda topup` always tops up your **personal** wallet, regardless of |
| 90 | context. Topping up the org wallet (and configuring auto top-up) is |
| 91 | admin-only and happens on the web at `/organizations/<slug>`. If a |
| 92 | member runs out of org credits, the error tells them to ask an admin or |
| 93 | switch back to personal — they cannot top up the org wallet from CLI. |
| 94 | |
| 95 | Roles inside an org are separate from the seat plan: |
| 96 | |
| 97 | - **Owner**: the original creator. Cannot be demoted or kicked. Can transfer ownership to another member from the org page (rare). |
| 98 | - **Admin**: can invite (single or bulk via paste), kick, change roles, change seats, top up, configure auto top-up, change monthly limits. |
| 99 | - **User**: can only spend within the org wallet (subject to a per-member month |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- google-agents-cli-workflowThe CLI and skills that turn any coding assistant into an expert at creating, evaluating, and deploying AI agents on Google Cloud.SkillsJul 2026
