Skip to main content
Klipeo
Klipeo Docs
Vibe, the AI

Meet Vibe

Vibe is the AI editor built into Klipeo. Here's how to talk to it and what it does when you do.

Vibe is the AI that edits alongside you. You tell it what you want in plain language, and it makes the changes on your timeline. It isn't a separate tool you switch into. It's editing the same composition you are, so anything it does, you can adjust, and anything you set up, it can build on.

Opening the panel

Vibe lives in the editor header. Click the sparkles button (Klipeo agent) next to Export and the panel takes over the timeline area. A layout toggle in the Vibe header moves the panel between the bottom and the right side, whichever suits the edit you're doing.

On a phone, the editor opens straight into a full-screen Vibe screen instead of the desktop timeline, with the same transcript, composer, and media gallery.

Talking to it

Type your request in the composer and press Enter to send. Shift+Enter adds a newline. Press Escape once to arm a clear, and again to start a fresh chat.

A few things you can do while writing:

Attach files

Drop in an image, video, audio, or GIF to give Vibe something to work with.

Run a Skill

Type / to open the Skill palette and pick a saved recipe. See Skills.

Mention a clip

From the + menu, pick "Mention a clip" or "Mention audio" to point Vibe at one exact piece of the timeline.

Mention anything

Type @ to reference a track, an asset, or a marker by name instead of describing it.

Keep your asks concrete. "Trim the dead air and add TikTok-style captions" lands better than "make this good," because Vibe can map it to real operations. There's a longer guide to phrasing in Skills and cost habits in Save on AI cost.

What happens after you hit send

Vibe works in the open. You'll see it think, run its tools, and change the timeline as it goes, rather than going quiet and dropping a finished result on you.

It looks at your composition and recent history to get its bearings.
It plans which tools to run for what you asked.
It runs them one by one, and each edit lands on your timeline as it finishes.
It writes back a short summary of what it changed.

Because every change streams in as it happens, you can stop reading the summary and just watch the preview. If something looks wrong, you don't wait for the end. You fix it right there.

If Vibe needs something from you mid-turn, it asks. The question shows up in the composer as a small wizard: a text box, a single-choice list, or a multi-select, depending on what it needs. Answer it and the turn carries on.

Anything Vibe generates during a turn (images, video, audio) shows up inline as a media card in the transcript, and collects in the media gallery so you can find it again later without scrolling back.

Long jobs stop to check in

A single turn runs at most 12 rounds of tool calls. If Vibe is still working when it hits that, it stops and tells you so. Just ask it to continue and it picks up where it left off.

Chats and history

Sessions are saved on the server, so a chat survives a reload. The Vibe header has a recent-chats dropdown where you can load an old chat, rename it inline, or delete it, and a New button to start a clean one.

What it can actually do

Vibe drives the same editing operations you have by hand, grouped into areas like captions, cutting and trimming, audio cleanup, color, transitions, zooms, voiceover, and full end-to-end edits. The curated recipes for the common jobs are listed in Skills. If you can describe an edit in terms of those, Vibe can usually do it.

When something goes wrong

If a step fails, Vibe says so in the chat instead of pretending it worked. You'll see which tool had trouble and a short reason. Usually you can rephrase and try again, or do that one piece by hand and let Vibe carry on with the rest.

Where Vibe runs

By default Vibe runs on Klipeo's cloud, so there's nothing to install. You can also point it at a coding CLI on your own machine (Claude Code, Codex, Gemini CLI, or OpenCode) which is free to run and where the model selector comes in. That's all in Engines and models.

Undo covers Vibe too

Vibe's edits go on the same undo stack as yours. If you don't like what it did, Cmd/Ctrl+Z walks it back like any other change, so it's always safe to let it try something.

On this page