Scenario Reve Image
Overview
Reve, Reve AI's image family on Scenario, splits into two members that share a brand and little else: v2.1 is a reasoning-driven generator and instruction editor (a top-2 text-to-image arena entry at authoring time), Remix a fast, cheap compositor that blends several images into one. Discover them with
and treat
as the contract: they disagree on field names, prompt caps, and ratio lists.
Connection and the core loop: see the
skill in this repo; model-agnostic image work: the
skill. If a sibling skill named here is missing from your available skills, ask the user to install it (
npx skills add scenario-labs/skills --skill <name>
); unattended, proceed from tool schemas and flag the gap.
Quick reference
At authoring time (the live schema wins):
| Member | Capabilities | References | Prompt cap | Aspect ratios |
|---|
| Reve v2.1 | txt2img, img2img | , optional | 4000 | 18 values, 4:1 through 1:4, default auto |
| Reve Remix | img2img | , required, 1 to 6 | 2560 | 7 values, 16:9 through 9:16, default 3:2 |
Three parameters each: the prompt, the reference array,
. Neither member has a mask, seed, width and height, negative prompt, or batch-count field, so an edit is scoped by wording and size comes only as a ratio.
(v2.1 only) picks a fitting shape; pass an explicit ratio when the deliverable demands one.
Pick by job. v2.1 covers generation from a prompt alone and precise edits: swap the text on a poster, recolor a product, change a material, relight or restyle, merge references while every subject stays consistent. Remix blends photos, illustrations, or design assets into one cohesive composite. Where either would do,
both: at authoring time a v2.1 run cost several times a Remix run and took over a minute at p50 against Remix's twenty-odd seconds.
Frame tags wire v2.1 references
In a v2.1 prompt, a reference is addressed with a
tag, numbered from 0 in the order the assets appear in
: the first is
, the second
. Use the tags whenever more than one reference is in play; without them the model guesses which image you mean. Remix documents no tag syntax: name subjects in plain words ("the bottle from the first image, the lighting from the second").
Edits are instructions, not masks
Neither member takes a mask, so the prompt carries the whole edit: state what changes and what must stay untouched. v2.1's reasoning rewards specific plain-language instructions over keyword lists, and its 4000-character budget leaves room for constraints. For masked inpainting on an exact region, use a model that exposes a
field (see
).
Worked example: swapping the text on a poster
- with , , . At authoring time the hits were (generation and instruction edits) and (multi-image blends); re-discover each session.
- on the pick: field names, caps, and the ratio list before anything else.
- the poster (see the skill) to get an asset id.
- with that , , and
parameters={"prompt": "Replace the headline on the poster in <frame>0</frame> with 'SUMMER SALE', matching the original font, perspective, and lighting. Change nothing else.", "references": ["asset_x"], "aspectRatio": "auto"}
for the cost estimate.
- Repeat with , then with the returned job id, re-called with on timeout, never a second .
- to check the swap, then to save.
Common mistakes
- Counting frames from 1: is the second reference; the first is .
- Carrying a field name across members: v2.1 takes , Remix takes ; each schema lists only its own.
- Running Remix without references: is required (1 to 6 at authoring time); prompt-only generation belongs to v2.1.
- Reusing a v2.1 prompt on Remix without checking length: 4000 characters overflow its 2560 cap.
- Sending width, height, a mask, or a seed: none exists on either member; is the only size control.
- Treating a v2.1 timeout as an error: p50 latency topped a minute at authoring time; re-call with .