Opens inside Autopilot, ready to use
No separate login and no link to remember. Pin a published Mini-app to a Space and the team finds it there.
Ask an agent for a stock dashboard, a shift planner or a quote calculator. It builds a Mini-app in your Library, you try the draft, and the published revision is the one your team opens.
Morrow planned workshop shifts in a shared sheet that broke every other week. The planner they use now does one job, sits next to the work it serves and changes when someone asks.
No separate login and no link to remember. Pin a published Mini-app to a Space and the team finds it there.
A Mini-app is a folder in the Library. Its code and its data are ordinary entries with a history.
Say who uses the tool and which decision it should help with. The agent builds from that, in the open.
Each Mini-app has its own conversation. Ask for a change there and the next draft shows up beside it.
Lena asked for a warning when stock drops under twenty. Until that draft was published, the team kept using revision 2.
One job, a few inputs, a clear result. A planner for the workshop works better than a tool for everything.
Preview the draft with real entries before anyone else sees it, and send it back with a sentence.
Publishing saves that exact version as a numbered revision and shows which files changed since the last one.
Every published revision is kept. If the new idea was worse, restore the files to before the Run that changed them and publish again.
Published does not mean connected to everything. What a tool can read or do is stated at publish time and checked again every time someone uses it.
The same planner lets Lena edit the entries she may edit and lets a Viewer only read. Drawing a button on screen never grants what the person behind it lacks.
A Mini-app can only call the tools named in its manifest. If a draft adds one, the publish dialog lists it under the changed files.
The internal tools workflow follows a requirement, a tested app and its version.
A small web app stored as a folder in your Library. It runs inside Autopilot in an isolated frame, and it reaches your workspace only through the tools listed in its manifest.
No. Every call it makes runs with the permissions of the person using it. Someone who cannot read a Space cannot read it through a Mini-app either.
No. An agent writes the code and you review the tool, not the source. The files are in the Library if someone on the team wants to read or edit them.
People and agents with the publish permission in that Space. Anyone else can request approval for the exact draft, and a person who may publish decides. More in Roles and approvals.
It is the wrong size for that. A Mini-app fits one narrow job: a planner, a dashboard, a calculator, a checklist. For a full application with its own backend, an agent works in a repository through Projects.
Describe it in a Task and review the first draft. Free during the open beta.