Database

Most apps need somewhere to store data — todos, habits, orders, whatever your app is about. Bool sets up a database for you automatically as part of building your app; you don’t provision or configure anything.

Browsing your data

Open the Dashboard tab and go to Data. Every table the agent has created for your app shows up in the sidebar as soon as it exists.

Click a table to see its rows in a spreadsheet-like view, where you can:

• Search and filter rows
• Add a new row using a generated form (one field per column)
• Edit a row’s values inline
• Delete a row, with a confirmation step

The view stays live — if the agent changes data (or another collaborator edits a row) while you’re looking, it updates without a refresh.

Your app updates live for everyone

Data in your app is live. When someone adds, edits, or deletes something, everyone else looking at that screen sees it within a moment — no refresh, no “reload to see changes” button, and nothing you have to ask for. Your own changes appear instantly, before the save has even finished; if a save fails, the change undoes itself and you’re told why.

That makes shared apps work the way people expect:

• A team todo list where everyone sees items appear as they’re added
• A party game lobby where players watch each other take seats
• A scoreboard, order queue, or booking sheet several people are watching at once
• Your own app open in two tabs, or on your laptop and your phone

You don’t need to ask for any of this, and you don’t need accounts for it to work — an app anyone can open with a link updates live for everyone who has it.

Not yet: continuously moving things. Data changes are live, but signals that change many times a second — other people’s mouse cursors, a drawing stroke while it’s still being drawn, characters moving in a fast-paced game — aren’t smooth yet. If you ask for one of those, the agent will build the closest honest version and tell you what it can’t do, rather than shipping something that looks broken. This is on our list.

Ask the agent instead

For anything more involved than editing a row by hand — adding a column, changing a relationship, seeding data, running a one-off migration — it’s usually faster to just ask in chat than to do it manually. For example: “add an archived boolean to the habits table” works the same way as any other build request.