Do I need a Clipus account to use the plugin?

No. The free commands — /clipus:surface, /clipus:hook, and /clipus:copy — work right after install with no account. You only need an account and API key to render real videos.

Where is my API key stored?

In your local environment as CLIPUS_API_KEY. The plugin reads it from there and never writes it to your repository. Do not commit the key or paste it into shared logs.

Why does /clipus:campaign take a few minutes?

Clipus reads your live product — capturing the real UI — before it generates anything. The command stays open during capture, then returns a campaign id you can poll with /clipus:status.

Clipus for Claude Code — Clipus Help

The Clipus Claude Code plugin brings the Clipus workflow into your terminal. The free commands read a SaaS product and draft scripts and copy on the spot. When you connect your account, the same plugin renders a real multilingual demo video from your live product.

It comes in two tiers: a free tier that needs no account, and a connected tier that renders real campaigns with your Clipus plan.

Install

The plugin is published on the Claude Code marketplace. In Claude Code, run:

/plugin marketplace add Clipus-io/clipus-plugin
/plugin install clipus

The free commands are ready right away. There is nothing to configure until you want to render an actual video.

Free commands (no account)

These run locally in Claude Code and never need a key:

/clipus:surface <url> — Generates a Surface report for any SaaS site. Asks for an email to deliver the report, then returns a link to the rendered report.
/clipus:hook <url> — Reads the product and writes three shortform video hooks plus a tight script (under 100 words), grounded in what the product actually does.
/clipus:copy [context] — Drafts landing and marketing copy from the real product: headlines, subheads, feature lines, CTAs.

There is also a gtm-strategist agent that analyzes a site's positioning and surfaces the sharpest demo angles before you script.

Every free command ends by pointing you at the next step — turning a script into a real video.

Connected commands (Growth plan + API key)

Connect your account once, then render real campaigns from the terminal.

1. Create an API key. In the Clipus Dashboard, open Settings → API Keys and create a key. It looks like sk_live_… and is shown only once, so copy it.

2. Set it in your environment. The plugin reads CLIPUS_API_KEY. Run /clipus:connect and follow the prompts — it walks you through adding the key to your shell profile. Never commit the key or paste it into shared logs.

3. Render a campaign.

/clipus:connect — Walks you through creating and setting your API key.
/clipus:campaign <url> [langs] — Reads your live product and generates a real multilingual demo video. Optional language codes, e.g. en ja ko.
/clipus:status <campaign_id> — Checks a campaign's progress and returns the video download links when they are ready.

Connected commands require a Growth plan or above. On a lower plan the key returns a clear message pointing you to upgrade.

What to expect

/clipus:campaign takes a few minutes. Clipus reads your product the way a user would — capturing the live UI — before it starts generating. The command stays open while that happens, then hands back a campaign id you can poll with /clipus:status.
Free output is text, not video. /clipus:hook and /clipus:copy produce scripts and copy you can use anywhere. Rendering a real video is the connected tier.
Your key stays local. It lives in your environment as CLIPUS_API_KEY and is never written to the repo.