Direct Cyberbara control from your terminal

Use cyberbara-cli

If you want image, video, audio, and music generation from the shell, scripts, cron jobs, or CI, the CLI is the shortest path. It gives you a clean execution surface for both humans and automation.

Copy these three lines to validate the CLI fast

Built for scripts, shells, and batch work

npm install -g cyberbara-cli
cyberbara auth configure --api-key "<your_api_key>"
cyberbara image generate "A cinematic product shot" --model nano-banana-2 --yes

Install first, configure the API key once, then run generation commands. After that you can extend into uploads, quotes, waits, and raw endpoint calls.

Open CLI repo Get free API key

Fits the terminal and agent workflows you already use

The structure mirrors /skill, but the execution surface is the terminal. The CLI works for humans directly and also for agents that can call shell commands.

Claude Code

Codex

Claude

GPT / OpenAI

Cursor

LobeHub

OpenClaw

Where the CLI fits best

When you do not want to hand-assemble HTTP requests but also do not want to hand everything to an agent, the CLI is the most stable middle layer.

Generate directly from the shell

Start image, video, audio, and music tasks from the command line without hand-writing HTTP requests.

Fits scripts and batch jobs

Use it inside cron jobs, CI, bulk-generation scripts, and internal automation tasks.

Also works as an agent execution layer

If your agent already knows how to run shell commands, the CLI becomes a stable action surface.

Keeps the API escape hatch open

When you need lower-level control, you can still drop to the public API instead of being boxed into a black-box abstraction.

The fastest way to start

Install the package, configure the API key, and run commands. Then expand into batch workflows, automation, and scripts.

1. Install the CLI

Get a consistent command surface into your environment once, then reuse it across jobs.

2. Configure the API key

Set it once, then reuse the same auth path across image, video, audio, and music commands.

3. Generate and wait for results

Start with one minimal command, then expand into uploads, waits, and output saving.

How teams usually use the CLI

Think of it as a daily engineering tool, not just a landing-page button. It fits generation, waiting, saving outputs, and script reuse.

API Docs

Image

Generate ecommerce visuals directly in the terminal

Video

Submit video jobs in batches and wait for completion

Automation

Drop commands into CI or internal scripts

Agent + CLI

Let an agent use shell commands to run the whole workflow

CLI setup path

The sequence is simple: install the CLI, configure the API key, run the first command, then extend as needed.

Install the CLI

A global install gives you one consistent command surface for Cyberbara media tasks.

npm install -g cyberbara-cli

Open CLI repo

Configure the API key

Start with a free API key, then let the CLI save it once.

cyberbara auth configure --api-key "<your_api_key>"

Get free API key

Run the first command

Validate the path with one minimal image command, then expand into video, audio, music, upload, and task-wait flows.

Smallest validation command

cyberbara image generate "A cinematic product shot" --model nano-banana-2 --yes

If you need deeper control, use the CLI and API docs side by side: the CLI for execution ergonomics, the API docs for capability boundaries.

View API docs

FAQ

The practical CLI questions usually come up first.

Install the CLI first, then wire Cyberbara into your terminal workflow

If your work already happens in the shell, this page is the shortest starting point.

Open CLI repo View API Docs