Your site's database

When a site needs to remember things — bookings, contact messages, product catalogues, user content — the agent gives it a real database, not a pretend one. This page explains what gets created and how to work with it.

How it works

Ask for a feature that stores data ("let visitors book a table", "save newsletter signups") and the agent creates the tables it needs in your project's backend database, writes the code that reads and writes them, and connects the site's forms and pages to them. Data your visitors submit is stored in those tables and survives republishing — publishing replaces the site's code, never its data.

Seeing your data

Open the agent's Files view and look in the entities folder: it lists the workspace's tables with live row counts, so you can confirm at a glance that signups, bookings, or orders are actually being recorded. To inspect or change individual records, just ask the agent — "show me today's bookings" or "delete the test signup" — and it will query the table for you and report what it found.

Changing the shape of your data

• Ask in plain language: "add a phone number to bookings" — the agent alters the table and updates the forms that use it.
• New features get new tables rather than overloading old ones, so old data stays readable.
• Before a big restructure, the agent takes a checkpoint — you can roll the project back if the change was wrong.

Exporting and ownership

The database belongs to your project. If you export the code through GitHub and host the site yourself, ask the agent for a data export before you move — it can produce your tables in a portable format you can import into your own database.