An order desk for the morning check
What the agent checked and what waits for a person, on one screen. The operations page shows the routine behind it.
Open betaFree while the beta runs
A tool for the job.Built when you ask.
Describe the job in a sentence. An agent builds a Mini-app, you try the draft on the real task, and the version you publish is the one the team opens.
From a need to a version.Four steps you can see.
Lena plans the workshop week at Morrow on paper. This is how the paper became a shift planner.
- Define
Say who uses it, and for what
Who opens the tool and what do they need to see or decide? One sentence in a Task is the brief.
- Build
The agent makes a first version
It creates the Mini-app in the Library. It stays a draft until someone publishes it.
- Test
Try the job the tool is for
Open the draft and plan a real week in it. Ask for changes in the same thread until it holds up.
- Publish
Make the version explicit
Publishing takes a snapshot with a number. The team opens that revision, and each publish is a line in the app's conversation.
Across teams
The same four steps.A different tool each time.
A good fit is small and has one job: a planner, a calculator, a board for one process.
A launch plan by product
Every product in the collection with its copy, photos and page status, filtered to what is still open.
The tool is a folder you can read
A Mini-app lives in the Library next to the Knowledge it uses.
Improved by asking
The next change is a message in the app's own conversation.
Built by an agent with one job
The builder works under its own Role, like any colleague.
A small tool with clear edges.
You can read what a Mini-app is allowed to touch and which version people are using.
What it may touch
The app lists the tools it calls
A Mini-app reaches Autopilot only through the tools named in its manifest. Every call runs with the permissions of the person using the app.
# shift-planner: declared tools
autopilot.library.pull read the shifts
autopilot.library.push save the shifts
# anything else is out of reach
Where the data lives
Ordinary files in the Library
The planner reads and writes entries in the Library, with the same access rules as any other file. An agent or an Automation can refresh them from an outside source.
# Library: Studio / shift-planner
app/ Published rev. 3
shifts.json edited by Lena, 14:20
> history kept for both
Before you ask for a tool.
What kind of tool is a good fit?
A bounded one: a planner, a calculator, a dashboard, a board for one process. A full application with its own backend is a different job, and QUESTPIE Works builds those.
Who can change or publish a Mini-app?
Editing follows access to its folder in the Library. Publishing is a separate permission, so an agent that may build can still need a person to publish.
Can a Mini-app do things its user is not allowed to do?
No. The app has no permissions of its own. Each call runs as the person who is using it, limited to the tools the app declares.
Does it run outside Autopilot?
No. A Mini-app runs inside Autopilot, for signed-in members who can read it in the Library.
Is there a fee per builder or per app?
No. Plans are per company with unlimited people and agents. It is free during the open beta. See pricing.
Start with one missing tool.
A clear user, a clear job and a version the team can inspect.