Walk through one Wren build from first prompt to merged branch, with screenshots from a real session covering plan review, edits, and approvals.
These are the steps you’ll repeat for most build work. The screenshots are from a real session, so what you see here is what you’ll see in Studio.The example below adds a knowledge base topic, but the shape is the same whether you’re writing a flow, wiring an integration, or changing how the agent speaks: describe it, answer any questions, approve the plan, review what changed, then merge when you’re happy.
1
Start from the home screen
The chat panel opens with a prompt input. Choose See prompt suggestions for starters grouped by intent: Build, Test, Ask, and Analyze. Pick a suggestion, fill in the blank where there is one, or ignore them and type your own request.
Home screen with Build, Test, Ask, and Analyze suggestions
The more grounded your request, the fewer questions come back. “Add a topic for our office opening hours” works, but “Add a topic for our office opening hours: 9am to 6pm Monday to Friday, closed weekends and UK public holidays” gets you there in one turn. See the prompting guide for more.
2
Answer any clarifying questions
Rather than guess at business rules it can’t infer, Wren asks. Questions come in a set you step through: pick an option, choose Something else to type your own answer, or Skip to let Wren decide.
Step through the questions, or skip to let Wren choose
This is the step that stops Wren inventing your policies. If it doesn’t know your refund window or your opening hours, it asks rather than picking something plausible.
3
Approve or revise the plan
Once it has enough context, Wren presents a plan card summarizing what it intends to change, with Approve and Revise buttons. Nothing is written until you approve. Expand the card to read the full breakdown.
The plan, with Approve and Revise
Revise opens a feedback box. Say what should be different and Send to re-plan, or leave it blank to reject outright.
Revise sends feedback and re-plans
For small, unambiguous changes Wren may skip the plan and just do the work. The bigger or more structural the request, the more likely you’ll see a plan first. You can always force one by asking: “Plan this before making any changes.”
4
Watch it work on a branch
The first time Wren makes a change it creates a branch automatically, named after the request and prefixed wren/. Main stays untouched, and the branch chip replaces Main in the top-left for the rest of the session. Each step it takes is listed as it goes, with a running count of changes made.
A branch is created automatically, and every step is listed as it runs
Expand the summary to see each step, and open any changed resource to check it by hand. Everything Wren wrote is an ordinary edit on your branch, so you can adjust or undo it exactly as you would your own work.
5
Merge to main
Merging is yours to do. Wren never does it for you. The Merge button in the top-right opens a dialog where you can add an optional message, then ship the branch back to Main. From there, your changes flow through the normal Sandbox → Live pipeline.
Merge the branch back to Main when you're ready
Not ready to merge? Leave the branch where it is. You can come back to the same chat later, keep iterating, and merge when it’s right.
