The developer console can now write the questions of a hosted form from a sentence — the same AI, the same credits, and nothing published until you have read it.
The sentence you would have typed anyway
Making a form by hand is not hard, it is tedious. You open a builder, you decide what to ask, you type it, you set what is required, you read it back to check you did not leave a required field blank. It is the kind of work that is easy to start and annoying to finish. You already know the sentences. “A sign-up form for our design partners.” “Ask a freelancer what they charge per hour.” “A short application for the beta list.” That is the whole description, and until today the developer console made you write the questions out longhand anyway. Now it does not. Press “Describe it” in a project, write the sentence, and Intake writes the questions: the labels, the types, the required flags, the choices where choices belong. You read them, change what you like, and publish.
What the model does, and what it cannot do
The model writes words. That is all it does. It cannot create a form, publish a form, move a form, or reach the database — it returns a proposal, and the server turns that proposal into a form definition, checks it against what a hosted form can actually render, and makes a draft. If your sentence needs something this kind of form cannot do — a file upload, a payment, a question that only appears for some people — Intake says so instead of quietly dropping it. That is the same rule the provider forms follow: an honest no beats a form that quietly lost half of what you asked for. And if the sentence is ambiguous in a way that would change the form, Intake asks one question rather than guessing. You answer it, and the answer goes into the same proposal.
The credits you already have
This is the same AI, the same ledger and the same twenty credits a day as everything else in Intake. There is no second wallet for developers and no new currency. A small form costs two credits, a bigger one costs a little more, and the console tells you what it charged when it is done. Nothing is charged when the model fails, and nothing is charged for the clarifying question. If your browser drops the connection and sends the same request again, the server recognises it and hands you the form it already made instead of making a second copy — one operation, one form, one charge.
Some sentences are the same sentence everybody writes. There is a row of templates above the box — waitlist, feedback, contact, sign-in, newsletter, beta application, support request, booking, RSVP, one question — and pressing one puts its sentence in the box. It is a shortcut, not a fixed form: the sentence is yours to read and change before it is sent, and the questions that come back are written for the sentence you ended up with. The sign-in template asks for an email address and a one-time code, never a password — a hosted form collects answers, it does not hold a session, and it is not the place a password should be typed.
What it will not do
- It does not publish anything. The form it writes is a draft until you publish it yourself.
- It does not choose a provider or a Google account. A hosted form lives on an Intake address, which is the point of it.
- It does not invent requirements. If it cannot responsibly guess a list of choices, it asks you for the list.
- It is not a second builder. Everything it writes can be edited by hand afterwards, and everything you can do by hand you can still do.