Tasks
Mini apps
Ask for a calculator, form or small tool and the assistant writes a working app — real files, a curated visual theme, and optionally its own backend with sign-in, data and storage.
When the answer is a tool rather than a document — a calculator, a quiz, a form, a small dashboard, an interactive demo — the assistant writes an app. It is real code in real files, running in a preview beside the task.
Where it runs: in a task, when mini apps are switched on for your workspace.
What the assistant can do
| It can | What that looks like |
|---|---|
| Create an app | A working first version, styled with one of the built-in themes |
| Write a file | A whole new file in the app |
| Edit a file | A targeted change to part of a file |
| Read a file | It looks at the current code before changing it |
| List files | Orients itself in an app it did not just write |
| Delete a file | Removes a file it no longer needs |
| Rename the app | Title only |
After it creates an app, the assistant looks at its own work — it renders the app, sees the screenshot, and fixes what is visibly wrong before handing it to you. That is why the first version usually arrives already corrected once.
Themes, not blank pages
Every app is styled by one of around seventeen curated themes — a coherent set of colours, fonts, and shapes, with a light and a dark palette. The assistant picks one that fits what you asked for, and you can ask for a different one at any time. The point is that a generated app should not look generated.
Apps with a backend
An app can go further than a page in a browser. Ask for sign-in, saved data, file uploads, or scheduled server work and the assistant can provision the app its own isolated backend, then use it:
| It can | What that gives the app |
|---|---|
| Set up a backend | An isolated project just for this app |
| Create a collection | A place to store records |
| Create a bucket | File and image storage |
| Configure sign-in | End-user accounts for the app’s own users, including social sign-in |
| Deploy a function | Server-side code the app can call |
| List or delete resources | Housekeeping on what it has created |
The app’s users are its own — signing in to your mini app is not signing in to Dhanu. Backend credentials stay on the server; the generated code never holds an admin key.
App backends depend on how your Dhanu is configured. If the assistant says it cannot set one up, that capability is not enabled for your deployment.
Working with it well
Describe behaviour, not implementation. “A form that collects name, phone and plan, then shows a monthly cost” is a specification. “Use React state” is not your problem.
Change one thing at a time. Apps are edited file by file; a narrow request gets a narrow, reviewable change.
Say when it needs to remember something. “Entries should still be there tomorrow” is the sentence that turns a page into an app with a backend.
After it is built
This page covers the tool — how an app gets made. Everything you can then do with one, from editing it by pointing at the preview to publishing it on your own domain, is in the Apps section.