Show HN: ChartDB Agent – Cursor for DB schema design (app.chartdb.io)
Last year we launched ChartDB OSS (https://news.ycombinator.com/item?id=44972238) - an open-source tool that generates ER diagrams from your database (via query/sql/dbml) without needing direct DB access.
Now we’re launching the ChartDB Agent.
It helps you design databases from scratch or make schema changes with natural language.
You can:
- Generate schemas by simply describing them in plain English
- Brainstorm new tables, columns, and relationships with AI
- Iterate visually in a diagram (ERD)
- Deterministically export SQL script
Try it out here - https://chartdb.io/ai - no signup required.
Or sign up and use it on your own database
Would love to get your feedback :)
23 comments
[ 2.6 ms ] story [ 42.9 ms ] threadOnly thing I kinda dislike is the low readability of the connection because of that border around the table of the same color as the connection lines (I think things would look cleaner without it)
prompts:
https://github.com/chartdb/chartdb/blob/c3c646bf7cbb1328f4b2...
"Design a schema like Calendly" --> Did it
"OK let's scale this to 100m users" --> Tells me how it would. No schema change.
"Did you update the schema?" --> Updates the schema, tells me what it did.
We've been running into this EXACT failure mode with current models, and it's so irritating. Our agent plans migrations, so it's code-adjacent, but the output is a structured plan (basically: tasks, which are prompt + regex. What to do; where to do it.)
The agent really wants to talk to you about it. Claude wants to write code about it. None of the models want to communicate with the user primarily through tool use, even when (as I'm sure ChartDB is) HEAVILY prompted to do so.
I think there's still a lot of value there, but it's a bummer that we as users are going to have to remind all LLMs for a little bit to do keep using their tools beyond the 1st prompt.
It was easier to close the tab than fire a human, but other than that not a great experience.
Have you thought about making a tool to help preview/dry run migrations?
I feel that's something I would want a ton of confidence in if an LLM is making migration scripts.
Especially if it's doing scary stuff like breaking up a table.
A SQL MCP + mermaid is all you need.
Btw, it can also do an awesome job turning query plans into readable mermaid flow diagrams, adding details to the chart, using color to highlight bottlenecks.
I'll probably stick with Claude for now.
A killer feature would be a discussion loop that slowly refines the model in plaintext before committing to a diagram.