Backend tasks

The [estage-dedicated:] tag is the guaranteed way into the backend builder. But once your project has an active Dedicated Cloud, plainly-worded data requests route there too.

How to trigger it

With a cloud active, just ask:

• “create a table to save user feedback”
• “add a sign-up form that saves to the database”
• “set up user authentication”
• “a newsletter subscribe button that stores emails”

What happens

Exactly the same engine as the tag: the backend agent inspects your cloud, creates or updates tables, security rules, realtime, and functions — then the UI is built wired to them. Progress shows in chat (“Cloud: Working on your backend…” with substeps).

It also stays in scope: ask for “make the button blue and add email capture” and only the email capture goes through the backend path — the styling is handled as a normal edit.

No cloud yet?

Then plain phrasing can’t reach the backend builder — instead Genesis offers to provision a cloud when it notices your request needs one (a chip-question: “This needs a backend — want me to set one up?”). Or skip the dance entirely with the tag: [estage-dedicated: …] auto-provisions on an active subscription.

When to still use the tag

• No cloud yet — the tag handles provisioning.
• Certainty — borderline phrasing (“make a feed”) can read as a visual-only request; the tag removes the ambiguity. Rule of thumb: casual asks work plain; important features get the tag.

Full backend docs: Dedicated Cloud.