Cliphi + Gemini CLI

Clips from a
Gemini CLI prompt

Gemini CLI can run the whole flow with its shell tools: submit, wait, and collect clip links in your session.

1Export your Cliphi key

In the environment Gemini CLI runs in. Created once in Cliphi Settings.

2Prompt for clips from your video

It submits the job and checks progress until the moments are ready.

3Choose from the previews

Preview links are free. Renders run only when you ask; your picks come back as clip URLs.

Gemini CLI questions

This page is the terminal. Gemini CLI runs on your machine and reaches Cliphi through your shell, which suits scripting and repeatable work. If you would rather do it in a browser conversation, the Gemini page covers that setup instead.

Into the environment Gemini CLI runs in, created once in your Cliphi settings. Keep it out of anything you commit. Gemini CLI picks it up from the environment, so it never needs to appear in a prompt you type.

Yes. Each submission is independent and returns its own job id, so a loop over a list works exactly as you would expect. Cliphi processes them on its own infrastructure rather than queueing behind your terminal.

Say so when you submit. Cliphi takes a language for transcription, and setting it explicitly gives noticeably better results than letting it guess, which matters most for videos that mix two languages in the same sentence.

Also works from

Clip from a Gemini CLI prompt

Export a key once and clipping becomes part of your normal session.

Building your own agent or workflow? Developer docs