Your first task,
today
Nothing to configure: the swarm is created for you, the models are already wired up, and a task is just a sentence. The five steps below are exactly what happens after the install.
Sign in with an email
On the first run the app asks for an email and a password — that is your account. Every account gets its own database: chats, bots, files and memory never mix with anyone else’s. The same account opens the browser version and the phone one: the swarm is the same everywhere.
- The password is asked once — the app remembers the session
- What else the account does
The swarm is already there
Right after the first sign-in the list on the left holds ready-made bots: an assistant, a doer, a planner and others — 29 roles in the catalog. If the one you need is missing, ask in plain words and it appears, with its own character and its own limits.
- Create an Accountant bot”
- Hide the ones you don’t need, pin the ones you do
- The role catalog
The first task, in plain words
Write what you would write to a colleague. The assistant works out who to call in and where to start: the plan shows up in the feed, with the owner of every step next to it. Start with something small so you can watch the whole path at once.
- Build a one-page site about my coffee shop and show me a preview”
- Read this contract and list the risks”
- Find five suppliers and put them in a table”
The permission card
Before anything big — publishing, sending, paying, deleting — the bot stops and asks. The card says exactly what it is about to do: allow once, allow always, or refuse. Nothing irreversible happens without your yes.
- Rules can be set up front: what is fine unasked, and what never is
- How the result gets checked
The result lands in the chat
Finished work comes back into the conversation: files, a preview link, a screenshot, a table. When a bot says “done”, that is checked against the log of what it actually did — and if the promise is missing, the reviewer sends the work back before you even look at it.
- Version history: any step can be rolled back
- The whole path of one task
Three common questions
Mac refuses to open it
The build is not signed by Apple yet: allow it once in the security settings and it never asks again.
No server of your own
None needed: free models or your own key will do. A server matters when the data must not leave the building.
The bot is slow
Big tasks run in steps, and every step is visible in the feed. Long work can be cancelled with a button.