Parameters

Every design Prompt2CAD produces ships with a set of parameters — adjustable knobs the agent declares as it writes the geometry. They show up in the bottom-right panel of the viewport and let you re-shape the model without spending credits.

Three kinds of parameter

Type	Looks like	Example
Number	Slider with min / max / step	width: 0.8 → 2.2 m, step 0.05
Enum	Button group	finish: matte-white / black-brown / white-oak
Boolean	Switch	back_panel: on / off

Numbers can carry a unit. The most common is length (meters internally, displayed in your unit system). Others are angle (radians under the hood, displayed in degrees), count (integers like shelf count or drawer count), and none (unitless ratios).

Why parameters matter

Parameters are free in two senses:

• No credits — dragging a slider re-executes the geometry code in your browser; no API call.
• No latency — the model re-renders on the next frame.

That makes parameters the cheapest iteration loop in the app. The pattern most users settle into:

1. Get a roughly-right model from the first, token-metered generation.
2. Sweep the sliders to fine-tune dimensions and try variants.
3. Only use chat follow-ups for changes a slider cannot express.

Practical examples

Dimensions

width, height, depth, length, diameter. Drag to fit a real-world spot — an alcove, a corner, the gap between two walls.

Counts

shelf_count, drawer_count, door_count, rows, cols. Step is usually 1. Adding a shelf does not require chat — the slider re-divides the carcass.

Angles

door_angle, lid_angle, recline_angle. Useful for visualising the model in its "open" state for a renderer or a client preview.

Enums

finish, style, sink_style, hardware. Listed as a button row. Picking a different finish swaps the material palette and re-textures the whole piece.

Booleans

with_plinth, with_back_panel, glass_doors. A switch in the panel. Toggling rebuilds the relevant section.

What if the parameter I need doesn't exist?

Ask. The agent can add a parameter at any point — "add a slider for the toe-kick height" — and it will show up in the panel within one token-metered iteration.

If a parameter exists but its range is too narrow ("the width only goes to 1.4 m, I need 1.8"), you can tell the agent to widen the range. That is also an iteration.

The agent declares ranges deliberately

Parameter ranges (min, max, step) are picked to keep the geometry sensible. A bookshelf width slider that allows 0.05 m would let you collapse the carcass into a flat plane. Override them carefully — sometimes "too narrow" really is "the agent thinks anything outside that range looks bad."

Edge cases

• Slider value out of range — values are clamped. A bug in the geometry code that wrote width = 999 would still render at width.max.
• A slider drag breaks the model — rare, but possible if the geometry code makes an assumption that fails at the extreme. The red error banner at the top of the viewport shows what went wrong; drag back, or ask the agent for a fix.
• A parameter you don't see anywhere — the agent declared it but no primitive uses it. Harmless, but you can ask for a clean-up.

Persistence

Parameter values are persisted with the project. Closing the tab and re-opening the project restores every slider to where you left it. Exports use the current parameter values — so if you have a width slider at 1.6 m, your STEP file will be 1.6 m wide.

In the experimental server-side preview, chat/status updates preserve your current slider pose instead of resetting it to the Agent's defaults. Compatible values also survive geometry refinements and are clamped if a range narrows. An explicit Agent change to the same parameter, or removing/replacing its knob, takes precedence. Slider changes remain free local editor operations and do not create a new version by themselves. They do not submit a chat instruction or change the Agent's server-side design defaults; request a specific pose in chat when you want the Agent to inspect it.

Next: Sections — the one piece of model vocabulary worth knowing.