Skip to main content
You don’t have to start from scratch. Tell the Agent “Build me a dashboard for XX”, and it initializes the package, writes the page and backend, publishes and opens the app, and checks the result with screenshots. You review the result and ask for changes.

Start with one sentence

You can skip the command. Plain requests such as “build me a Pomodoro timer” or “turn my Jira issues into a list I can create, edit, and delete” go through the same flow. Only a request like “make a Notion board”, which could mean Notion’s own board view, makes the Agent ask which one you want.

What the Agent does

1

Understand the request

It reviews your existing connections and tools, proposes two or three concrete directions, and asks only questions that significantly change the product. Reversible details such as the name, icon, and layout use defaults.
2

Prove the data path

It runs one read-only query against each data source to confirm authorization, fields, and real responses. If that fails, it stops and explains why instead of filling an empty shell with sample data.
3

Initialize the package

It calls init on the miniapp tool to scaffold miniapps/<pluginId>/ in your workspace. That is the only package it edits.
4

Write the page and backend

The page goes in miniapp/client/ and the Node entry in miniapp/node/; managed MCP, Connector, and Agent access are declared as needed.
5

Publish and open

It calls publish, inspect, and open in turn, and the page appears in the sidebar of the current conversation.
6

Check with screenshots

It inspects page structure, text, and interactions in the built-in browser and reports what passed and what could not be verified.

The miniapp tool

The Agent manages a Mini App’s lifecycle through the host’s miniapp tool. You rarely call it yourself, but knowing its actions helps you follow what the Agent is doing.

Keep iterating

Tell the Agent what to change. It edits the same package and publishes again. Changes stay inside the directory returned by init; it doesn’t read other drafts, installed plugins, or host source code.
Official Mini Apps installed from the marketplace can’t be edited or republished locally. To customize one, ask the Agent to build a copy under a new pluginId.

Already have a package

Got a finished Mini App directory or ZIP from someone? Hand it to the Agent: “Install this Mini App”. The Agent inspects the package first, without running its instructions, installing dependencies, or building, then publishes it with sourcePath. A ZIP is extracted to a new directory first.
The path is used for this publish only; later updates and restarts never read it again.