From answer to asset

An exploration answer is a moment in time. When an answer is worth keeping — a table that should stay fresh, a job that should re-run every week, an app your team should open on Mondays — you switch Ronja into Build mode and make it permanent.

Who can do this

Anyone who can start explorations can use Standard and Deep analysis. Build mode requires Build access, which an administrator grants per person. Without it, the Build option simply doesn’t appear — and if you ask anyway, you’ll see the message: “Build mode is disabled for your account. Contact an administrator to request access.”

What Build mode is

Ronja has three conversation modes: Standard, Deep analysis, and Build. Standard and Deep analysis answer questions; Build is where Ronja designs and creates durable resources — tables, workflows, and data apps — writing a plan first and keeping the structure consistent as it goes.

Enter Build mode

There are two ways in:

1. From the start screen. On a new, empty exploration, an owner sees a mode control with the segments Standard, Build, and Deep analysis (Build appears only if you have Build access). Pick Build before your first message — the header stamps the session BUILDER, and the mode is fixed for that conversation.
2. Mid-conversation. In a running Standard exploration, ask Ronja to build something. The agent requests Build mode itself, which arrives as an approval strip reading “Enter builder mode” — click Approve to switch. This is one-way: the session stays in Build mode from then on.

Pick the mode before the first message — Build is offered when you have Build access.

Tip

Already deep into an exploration you don’t want to disturb? Fork a tangent in Build mode from any of Ronja’s replies and build there, leaving the original thread untouched.

Watch the plan

Early in a Build session, Ronja writes an implementation plan. A Plan panel opens beside the conversation on its first write and stays live — you’ll see “updating…” while Ronja revises it. On the right, a build-status dock with Working and History tabs tracks what’s being created; when closed, a right-edge handle labeled “Build status” reopens it.

Approve what Ronja changes

Ronja never quietly changes things that matter. When it proposes a gated action, the conversation pauses and a gold approval strip appears above the composer with a plain-language summary of what’s about to happen.

1. Read the summary. Expand the strip to inspect the details — draft diffs and review cards show exactly what will change.
2. Choose one of three buttons: Approve (allow this action), Approve for session (“Approve this and don’t ask again for these tools in this session”), or Reject.
3. While the strip is up, the composer reads “Waiting for tool approval…” — the agent won’t proceed without you.

Nothing important happens without your say-so.

Caution

Destructive actions spell out their consequences in the strip. For example, clearing a table warns: “All rows and data in this table will be permanently deleted. … This can’t be undone.” Read these before approving.

Where your assets live

Everything Ronja builds lands in a feature — the container that keeps a table, its workflows, and the app that uses them together. New builds start private to you; sharing them with a workspace or the whole organization goes through its own review lane, covered in Scopes and sharing and Versions, drafts, and approvals.

Next step

Ready to go deeper? Try Create tables with Ronja or Build a data app, or read more on the three modes in Standard, Deep analysis, and Build. If you’re the one setting Ronja up for others, continue to Set up your team.