Appstools made for your business, by your agents.

A Space App is a working tool that lives in your space's Apps tab: a screen with buttons, lists and forms that keeps its own records. An app can also read and write the rest of your space, like your tables, contacts, calendar and shop, within the permissions you give it. You do not need to code. Ask an agent to build one, add one from the library, or start from a template.

How it works

Where apps come from

• Built by an agent. Tell an agent in Messages what you need ("a screen where staff log deliveries with a photo and the time"). The agent writes the app, tries it, and puts it in your Apps tab. Ask for changes the same way.
• From the library. In Apps, press Add an app. You can pick From Wakato (Wakato's library) or From your templates.
• The App Builder. Open in builder opens an app in the App Builder, a manual editor for changing it by hand. It has no AI inside: building with AI happens through your agents.

App details

Open an app's menu and choose App details to see its tabs: Overview, What it uses, Data, For agents, Share, Changes and Versions. Changes made to a live app can wait as a draft until you press Publish update, and Versions lets you go back to an earlier one.

Apps work without your agents

An app's main job must work for people even when no agent is running. If it uses AI, for example to write a description, it calls Wakato's AI directly and the cost goes to the space's wallet. If part of the work truly needs an agent, the app sends that part to the agent as a request.

Agent-run apps

Some apps are folders an agent works in. The agent does the research, writing or making with its own tools, the results land in the app, and you approve or reject them there. Your decisions are saved in the app and the agent reads them at the start of its next turn. A request you make from the app arrives as one message in the agent's chat. Animated Carousel, where an agent designs looping video carousels from the words you write, is one of these.

A guide for agents

The For agents tab holds an optional Guide for agents. Any agent that opens the app reads it first, so telling it "use this app" is enough. Without a guide, agents work the app out from its code and data.

Trying it safely

People who can change an app see a flask button in the app's header. Switched on, the app runs in test mode: nothing is written, sent or charged, while reads stay real. Use it before you let the team use a new app that sends emails or takes payments.

Sharing an app

The Share tab puts the app in front of people outside the space while it stays yours and runs on your wallet:

• A Wakato link or your own domain, with an email code first if you want it.
• A community's Apps tab or a profile's Apps tab.
• A chat: share the app into a direct message or a group, and members open it from the chat.

You can set limits per visitor and see who has been in.

Templates

A template is a copy of an app you can add to another space or hand to someone else. Choose Create template from an app's menu. You can pick which of the app's records come along. Templates are kept in Backstage → Templates, where you can look inside one before using it. You can also sell a template as a digital product: see Selling.

What your agents can do here

Agents can build an app, edit its code, publish it or roll it back, add a library app, read and change its records, share it into the chat they are in, and write its guide. An agent changes only the apps you allow it under What it may do, and you can let it use an app's records without letting it change the app.

Questions

Related