For high-volume creators tired of waiting on browser tabs:

Prep your video assets 3x faster without the manual copy-paste grind.

Queue all your prompts in single window. Let the app bulk-render your images and videos in the background while you focus on the final edit.

See it in action →

✓ Flow & Grok, one place✓ No scripts, no config✓ Your own account, always

PrompCut — Auto Flow

📝

Batch Prompt Input

2 PROMPTS

One prompt per line — each line = one generation job

1
2
A futuristic cityscape at sunset...
A cyberpunk street with neon signs...
2 prompts

⚙

Execution Parameters

MODEL

🍌 Nano Banana Pro

ASPECT RATIO

1:1

16:9

9:16

IMAGE COUNT

OUTPUT DESTINATION

📁 .../Legion/Downloads

Execution Terminal

IDLE

[12:39:28]System initialized. Awaiting prompt batch...
[12:39:28]Loaded model 🍌 Nano Banana Pro

You're not slow. Your workflow is.

AI batch video production works on paper. In practice it's a loop of switching tabs, copy-pasting prompts, waiting, downloading, and figuring out which prompt made which image — repeated 40 times before you've touched a single edit.

📋

One prompt at a time, by hand

Paste, generate, wait 20 seconds, download, rename. Twenty images means twenty rounds of this before you can open CapCut.

🔀

A different tool for every engine

Flow automator. Separate Grok tool. Two subscriptions, two setups, two things to break. You spend more time managing tools than using them.

🔍

"Which prompt made that shot?"

Regenerating one image means scrolling back through the entire chat thread trying to match a file name to the prompt that created it.

⏱

Real editing work sits waiting

Voiceover. Assembly. Timing. The parts that need a human brain — stuck behind a queue of clicking and waiting that a computer could handle.

Paste. Start. Come back to a full folder.

Drop your prompts into the queue

Paste everything into PrompCut and pick your engine — Flow for images, Grok for video. You can mix both in one run. Setup takes under two minutes.

No formatting required

PrompCut opens Chrome and takes over

A persistent browser session runs in the background using your own login. It submits each prompt, waits for generation, and moves to the next one. No babysitting. No re-login every time.

Your account, your generations, your usage limits

Every output stays traceable

Results stay tied to the prompt and engine that created them, so you can find the exact source text when a shot needs one more pass.

Prompt-to-output history

Need to redo one? Pull it from the Library

Every run is saved with its prompts. Click the image you want to fix, see exactly what generated it, and regenerate — without touching a single chat thread.

Library — coming in the next update

One app. Both engines. No juggling.

🪟

Both platforms live in your browser

Instead of buying a Google Flow automator and a separate Grok tool, PrompCut brings a shared queue to the tabs where the work already happens.

📚

Library keeps your prompts and outputs linked

Every image is stored with the exact prompt that created it. When you need to tweak a shot, you click it — not scroll through 200 lines of chat history.

🔐

Runs inside your own browser session

PrompCut uses your logged-in Chrome profile. No API keys, no tokens, no third-party credentials stored anywhere. You're generating as yourself — the same as clicking manually.

⚡

Add it like any browser extension

Install the extension, open Flow or Grok, and start a queue from the page. No Python environment, no command line, no YAML config.

🔧

We patch it when platforms change their UI

Flow and Grok update their interfaces. When that breaks automation, we push a fix — usually within 24–48 hours. Auto-updates mean you never reinstall to stay current.

🎬

Built from inside the workflow

This exists because a video editor got fed up spending the first hour of every batch session on copy-paste work. Every feature is shaped by that problem.

	PrompCut	Separate tools	Doing it by hand
Flow batch automation	✓	✓	✗
Grok video automation	✓	Separate app	✗
Single unified interface	✓	✗	✗
Prompt + output library	✓	✗	✗
Your own account / no API keys	✓	Varies	✓
Hours saved per 50-image batch	~2 hours back	Partial	All wasted

The questions worth asking — answered.

Ranked from the most common concern to the least. If something's holding you back, it's probably here.

Most common

Will this get my Flow or Grok account flagged or banned?+

PrompCut uses a persistent Chrome session — the same browser you already log into. It doesn't use headless bots, it doesn't scrape, and it doesn't generate at inhuman speed. From the platform's perspective, it looks like you're clicking through your browser — because you are. The difference is that PrompCut is doing the clicking for you, at a pacing that's indistinguishable from manual use.

What happens when Flow or Grok updates their UI and breaks things?+

This is a real concern, and the honest answer is: it will happen. When it does, we monitor it and push a patch — usually within 24–48 hours of the change breaking automation. PrompCut auto-updates itself, so you get the fix without reinstalling anything. We treat UI compatibility as an ongoing maintenance commitment, not a launch-and-forget feature.

Do I need to know anything technical to install and use this?+

Nothing technical. Add the extension, open the supported AI tool, and start a queue. No Python, no Node, no terminal window, no configuration files. If you have installed a browser extension before, you already know the setup path.

I already have a tool for Flow and one for Grok. Why switch?+

Two tools means two maintenance windows, two things to break, two subscriptions, and two separate windows to manage mid-session. PrompCut isn't just combining them — it's the only app that lets you route a batch through multiple engines from a single queue, and the only one that ties your output files directly to the prompts that created them. When you need to pull one image and regenerate it, you do it from one interface with one click.

What if it crashes or stops halfway through a 50-prompt batch?+

Every step is logged in real time in the terminal panel. If something stops, you'll see exactly which prompt it stopped on and why. The outputs you already generated are already saved to your local folder — you don't lose completed work. You can pick up from where it left off without rerunning the whole batch.

Right now I just need Flow — do I have to pay for Grok support I won't use?+

No. The Lite plan is free and includes both engines. You use what you need and ignore the rest. The sidebar just sits there until you want it. You'll probably want Grok eventually when you move from images into video — but there's no pressure to use features before you're ready for them.

Are more platforms coming? What if I use something else?+

Flow and Grok are live now. More platforms are on the roadmap — the app is built so adding a new engine shows up as a new tab in the sidebar without changing anything else. If there's a specific platform you need, email phanphuc1100@gmail.com. Active requests shape what gets built next.

Ready to stop
running the queue yourself?

Join the extension beta waitlist. We will email you when the next group opens.

After you join

We log your email in the PrompCut waitlist table.

You get first access when the Chrome extension beta is ready for another cohort.

We ask which engines and workflows matter most before expanding support.

You help verify the extension workflow before the public launch.

Questions? phanphuc1100@gmail.com