Take an agent-built form to its first saved response

Have your coding agent add a form to your app and prove that it saves a response. You end with a live form, one saved test response, and a workspace claimed to your account.

Set up the agent

New to Fillo? Run this in your app's repository with your work email:

npx @usefillo/cli@latest agent bootstrap --email <work-email>

It creates a preview workspace, installs the Build with Fillo skill, and emails you a private workspace link. Forms in the preview go live right away, within these caps:

Already have an account? Install the skill and sign in instead:

npx @usefillo/cli@latest skill install
npx @usefillo/cli@latest login

Agent setup covers Claude Code, Codex, Cursor, and the hosted MCP server.

Give the agent the task

Paste a prompt like this in your app:

Add a product feedback form to this app with the Build with Fillo skill.
Use the app's existing UI components.
Ask for a required message and an optional reply email.
Publish the form, then submit one clearly labeled, fictional test response.
Report the form ID, the route it renders on, and what you verified.
Keep management tokens and identity secrets out of browser code and commits.
If I need to connect something or approve a step, tell me exactly what.

The agent checks the workspace and project, builds the form with native controls, and pushes the schema:

npx @usefillo/cli@latest push form.json --handle product-feedback

On a preview workspace, the push makes the form live. For a file field, the agent checks storage first. If you need to connect storage, it keeps the file field and names the step.

An MCP connection can do the same work. A successful whoami proves the connection, not a live form.

Claim the workspace

When the form works, claim the workspace from the terminal:

npx @usefillo/cli@latest claim

The CLI emails a claim link with an approval code. Open it in the same inbox, check that the code matches, and approve. The workspace moves to your account on the Free plan, and the terminal stays signed in. Only you can do this step. An agent must not open your inbox or approve for you.

After the claim, a plain push still publishes. Add --stage when you want a draft to review first, then run fillo publish. See the CLI reference.

Check the saved response

1. Open the form in your app at desktop and mobile widths.
2. Submit it empty and check the errors and keyboard focus.
3. Find the test response under Responses in the dashboard.
4. Or run fillo responses list product-feedback once you've claimed.
5. Match its values and form ID to the test the agent sent.
6. Submit with the network off, then retry. Typed values should survive.

If a destination such as Notion or n8n is on, check its delivery separately. A saved response and a delivered response are different outcomes.

Hand it to the team

Keep the schema in the app repository, and keep field IDs stable once responses arrive. Show teammates where to review answers and how to repair delivery failures.

Related

• Custom layout example: Compare native controls with a host-owned layout.
• Create an account: See the preview caps and the claim flow in full.
• Build a shadcn form that saves responses: Reuse your existing inputs.
• Send in-app product feedback to Notion: Give the team a triage inbox.