Ask for it.
Watch it appear.
Clay is a project tracker where the UI isn't fixed. Describe the dashboard you need, and a coding agent builds it — live, against your real data.
One request in, one working view out.
These aren't screenshots of a designer's mockup — they're what a session in Clay actually produces.
01 — ASK
Type a sentence, get a dashboard.
The card on the right is a view the agent generated from the single request at its top. It wrote the chart, queried the Website Relaunch project's 38 real tasks, and rendered the result — no chart picker, no field mapping, no configuration screen.
The live view badge means exactly that: when a task changes status, the bars change with it.
“Show tasks by status as a bar chart.”
One sentence in chat. The agent wrote this view and wired it to the Website Relaunch project.
02 — REFINE
Keep talking until it's right.
This card is that same view's history. Each follow-up request — a bigger chart, colors by status — became a new numbered version instead of an overwrite, so you can step back to any point or branch off in a new direction.
The unchecked line isn't a task — it's simply the next request that hasn't been asked yet.
Refined in conversation.
Every request becomes a new version. Nothing is overwritten.
- “Make the chart bigger” — v2
- “Color the bars by status” — v3
- “Add a done-this-week tile”
Not a form builder.
Not another dashboard.
Just a small tracker for projects and tasks — with an agent that writes whatever interface you ask it for.
01
Ask. Watch. Ship.
No drag-and-drop builder, no widget library, no settings maze. Type a sentence and the view exists.
02
Real data.
Every generated view queries the same live database that holds your actual projects and tasks.
03
Yours to rewind.
Each refinement is a new version. Step back through every iteration a view has ever had.
Small on purpose. Live by default.
Clay keeps the core loop simple: track your work, ask for the view you need, and keep every version on your side of the line.
Try It YourselfYour Data, One Database
Projects and tasks live in Postgres you control. Generated views read from it directly.
Ask, Don't Configure
Describe a dashboard in plain language and a coding agent writes and renders it in seconds.
Refine in Conversation
“Make it bigger.” “Group by assignee.” Keep pushing a view forward with follow-ups.
Versioned by Default
Every change is a new version, never an overwrite. Roll back to any point in a view's history.
Guardrailed Agent
The agent runs read-only queries through vetted tools, with rate limits on every loop.
Audited End to End
Every agent action lands in an audit log you can read, so nothing happens off the record.
Run it, then ask.
A Docker Postgres and one dev command get a private Clay workspace running on your machine in minutes.
View the RepositoryThree commands to start your Clay server
docker compose up -d
npm install
npm run dev
Where Clay fits.
Use it wherever the view you need keeps changing faster than anyone wants to configure it.
Choose your next step.
Create a workspace, read the code, or run Clay locally and see how the agent is built.
Ask for your first view
Create an account, add a project, and describe the dashboard you want.
SourceRead the codeThe full app — agent loop, tools, and UI — is on GitHub.DeployRun it locallyPostgres via Docker, then one command for the dev server.TrustSee the guardrailsRead-only agent tools, rate limits, and a full audit trail.Common questions.
What Clay is, what the agent can touch, and what happens to your views over time.
What does the agent actually build?
Real interfaces — charts, tables, boards, and tiles — generated as code and rendered inside Clay against your live project data, not static mockups.
Can the agent change or delete my data?
No. It works through a small set of vetted, read-only tools: it can describe your schema, run queries, and propose views. Writing data isn't one of its abilities, and every action it takes is recorded in the audit log.
What happens when I ask for a change?
Each request produces a new version of the view instead of overwriting the last one. You can step back through the full history at any time and continue from any point.
Is the data in generated views real?
Yes. Views query the same Postgres database that holds your projects and tasks, so the moment your data changes, the views reflect it.
What is Clay built with?
Next.js and React on the front, tRPC and Drizzle over Postgres on the back, Clerk for auth, and the Claude API driving the agent loop. The source is on GitHub.