Inside LUVI

Inside LUVI

The canvas checks the wiring before you pay for it

A workflow graph is checked before any credit moves: an unknown port, an audio slot fed a video, an unfilled required input or a cycle is an error, and a graph with errors cannot run. That is the real difference between the canvas and generating one step at a time.

Inside LUVI

The delete we couldn't put a dialog in front of

When an assistant can delete a folder for you, a confirm dialog is no longer available as a safety net. LUVI's answer was to defer the delete by 24 hours instead — and to leave the folder's contents exactly where they were, so restoring it is an undo rather than a cleanup job.

Inside LUVI

Connecting Claude to your LUVI account: what the 35 MCP tools actually do

The LUVI connector gives Claude or ChatGPT 35 tools against your own account: it can read the model catalog, fetch a family's prompting manual, quote a price, generate, and report what the generation really cost. Here is what each group is for, and what it deliberately cannot do.

Inside LUVI

Estimate vs charge: why the number you pay only ever goes down

LUVI shows a credit estimate before every generation and charges you when the result arrives. Since September the charge follows what the job really used — capped at the estimate, never above it. What changed, what we measured, and why one model dropped from 15 credits to 7.

Inside LUVI

Why every image you upload to LUVI becomes JPEG or PNG

iPhone HEIC photos used to fail in Chrome, WebP confused half the models, and one library's browser decoder took 27 seconds on a 12-megapixel shot. So we moved the conversion to the server and made one rule: every image is stored as JPEG or PNG, colour profile and orientation intact.