Getting Good Results

Forge works with whatever you give it, but a few habits consistently produce better results faster.

Describe the outcome, not the steps

Forge knows how to build things in Studio — that's its job. What it can't know is your business.

Less useful:  Add a node, then connect it to the database node,
              then set the output to...
Better:       When an order comes in, reserve the stock and email
              the warehouse.

If you prescribe the steps, Forge follows them even when a better route exists. Describe the destination and let it plan.

Give the business context once

A sentence of context up front beats ten corrections later:

You:   We're a tour agency. Bookings live in the "bookings" table,
       payments go through our internal API. I want an agent that
       handles booking questions.

Forge explores your application on its own, but it can't read your mind about which table is authoritative or which API is legacy.

Answer the clarifying questions

When Forge asks something before building, that's the cheapest moment to steer. A vague "do whatever's best" is fine too — Forge will pick a default and say what it assumed — but a concrete answer removes a whole class of rework.

Ask big, expect iterations

Don't shrink your request to what feels "safe" — ask for the whole feature. Just know that Forge deliberately builds it in passes: the happy path first, then error branches, then polish. After the first pass, keep going in the same conversation: "now handle the out-of-stock case", "add logging to the failure branch".

Reject with a reason

Rejecting an approval isn't a dead end — it's steering. Use Add reason and say what you want instead:

Reject: "Don't create a new table — use the existing orders table, the status field."

Forge reads the reason and adjusts its plan. This is often faster than letting a wrong change through and asking to undo it.

One task, one conversation

Start a New chat when you switch topics. A conversation about the support agent that suddenly turns to database cleanup drags old context along — separate conversations keep Forge focused, and your history readable.

Verify through the links

After changes, the Changes made summary links to everything Forge touched. Clicking through and looking at the result on the canvas takes seconds and catches misunderstandings early — Forge tests what it builds, but only you know what you actually meant.