Semantic search and AI · AutessaDB
DB Copilot
The DB Copilot is an AI assistant for your database on the AutessaDB Tables page. Describe the data you need and it designs tables, proposes schema changes as reviewable cards you apply or reject, and answers questions about the data you already have.
-- the problem
Good schemas take experience
Choosing types, required flags, what should be searchable by meaning and how tables link is where data projects go wrong early. The DB Copilot turns "track support tickets with a status, priority and a link to the customer" into a concrete proposal you can inspect column by column.
What you get
- Reads run straight away: listing tables, fetching schemas, select options and querying data, shown as expandable tool-call cards.
- Changes need approval: an amber "table change(s) proposed" card, with Apply Changes and Reject Changes.
- A Create card shows every column (name, type, required, vectorized, foreign key), tags and select options.
- An Update card shows exactly which columns are added or removed and any new select options.
- For bigger asks it can present a design overview of several related tables first.
- The chat input locks until you decide, so nothing changes behind your back.
-- how it works
How does db copilot work in AutessaDB?
Open it
On the Tables page, click Autobot. The copilot opens as a resizable side panel.
Describe the data
What a record is, the fields, what should be searchable, and existing tables to link to.
Review the card
Check types, required flags, vectorized columns and foreign keys.
Apply
Click Apply Changes and the table appears, ready for rows, triggers and agents.
-- every option
What it can do
| option | what it does |
|---|---|
| Design | Propose new tables, alone or as a related set. |
| Evolve | Add or remove columns, add select options. |
| Ask | Answer questions like "how many open tickets are assigned to nobody?". |
| Approval | Every schema change is a card you apply or reject. |
| Usage | Draws on your company's AI usage allowance, like the other copilots. |
-- permissions
Who can do what?
| access | can |
|---|---|
| Anyone on the Tables page | Ask; changes apply with the person's own table access. |
◆ AI assist
Where AI helps
This is the AI feature: it designs, explains and queries, and it never applies a schema change without your click.
AI in AutessaDB works inside the same access rules as the person using it, and schema changes always wait for a person to apply them.
-- faq
Questions about db copilot
Can the DB Copilot change my tables without asking?
No. Reads run directly, but every schema change appears as a card that you apply or reject, and the chat waits for your decision.
Can it query my data?
Yes. Ask a question in plain language and it queries the table and answers.
When should I use the table editor instead?
For a single precise change you already know, or for triggers and computed columns, which have their own editors.
100% customizable, code and all
Make AutessaDB fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours