MINI APPS

Ask for a tool and have it by the afternoon

Describe the internal tool in a conversation. An agent builds it using any data in the workspace and publishes it privately. There is no code repository, no deployment and no ticket to raise.

Daya
Agents Chats Emails Calendars Recordings Integrate
WORKSPACE
Base apps6
Mini apps5
Drive21
Analytics23
ATTENTION
To-dos inbox15
@ / Unread11
Flagged2
Drafts3
STREAMS
payments-revamp
launch-prep
announcements
watercooler
platform
DIRECT MESSAGES
System agent
Maya
Ravi
Support agent
Research agent
Build with an agentv3
Build a tool for finance to approve old-gateway refunds before they are released.
Here is a first version. It reads Refund tracker and asks finance to approve each release.
Reads Refund trackerread only · route is Gateway
Writes Statusonly after someone approves
Posts to # payments-revampone message per approval
Flag anything that was disputed before.
Done. Disputed refunds now show a red note.
Describe a change…
PreviewDataPermissionsVersionsPublishing needs Mia’s approvalRequest publish
Old-gateway refunds
Approve each release before Ledger routing goes live
3 waiting$3,620.55
REFUNDCUSTOMERAMOUNTDECISION
R-1043Orbit$1,240.00Approved
R-1047Selin Kaya$980.55ApproveHold
R-1048Nadia Oseidisputed once before$1,400.00ApproveHold
Note for finance (optional)
System agent· #ops stream
We need a board for supplier claims. Status, amount, who owns it, and flag anything older than 14 days.
BUILT FROM SUPPLIER CLAIMS · 3 VIEWS
Supplier claimsboard · aged flag at 14 days · 2 editors
OpenPublish to workspace
Add a column for the contract reference.

Describe it in a sentence

Write one sentence in a stream saying what is needed. The agent finds the data anywhere in the workspace, builds the screens and shows the result. Reply with changes and it updates the app.

Uses live data from across the workspace, so the app is always current
Reply to change it: the next message updates the app
Published privately to the workspace in one click
Anyone can build one, not only people who can code

Small tools, organised like documents

Mini apps are organised in folders, each with an owner, a last-modified date and a history. They follow the same permissions as everything else, so an app can never show someone more than they are already allowed to see.

Folders, owners, rename, move and a bin
Limited to what its user and its agent are allowed to do
Install from the skill market if someone has already built it
Mini appsMy mini apps · 9
Supplier claims
built by an agent · used daily
Visit planner
built by Owen · used weekly
Burn tracker
built by Kate · used monthly
+ Describe a new one
Skill market · 40+ installable skills and apps

How mini apps work

Built by conversation

No code repository, no build step and no waiting in someone else's queue.

Live on workspace data

The app reads and updates the same data people work in.

Folders and ownership

Organised like files, with a history and an owner.

Skill market

Install an app that already exists instead of describing it again.

Same permissions

A mini app can only see what its user and its agent are allowed to see.

Published privately

Shared inside the workspace, never on the public internet.

System agentthinking · 11sStop
Owen: add a contract reference and group by supplier
✓ Read the Supplier claims app
✓ Found contract ref on suppliers base
✓ Added the column and the grouping
◌ Rebuilding the board view
Published to the workspace once a person approves it.

Improve it after the first version

Ask for a change and the agent looks at the app, the data behind it and how people use it, then rebuilds it and shows what changed.

Change it by replying, without starting again
The agent explains what it changed and why
Earlier versions are saved and can be restored
IN THE BOX
Build by describing
Build from any data
Iterate in conversation
Folders and colours
Rename, move and delete
Owner and modified date
Publish to the workspace
Install from the skill market
Agent-built apps
Per-app permissions
Runs on live records
No deploy step

Common questions

Do I need a developer?

No. Describe what is needed in a sentence. A developer can extend the app later through the API, but building one needs no code.

Can an agent build one without a person?

Yes, if it has permission. The result is a draft that a person publishes.

What happens if the data changes?

The app follows the data. It reads the source directly, not a copy, so a new field is available immediately and a removed one is flagged.

WORKS WITH

Describe the tool your team has been asking for

Write one sentence in a stream and an agent has it ready that afternoon.