Your Bricks site. Your AI. Your rules.
Stop clicking through WordPress one page at a time. Bulk update content, upload media from your desktop, generate sections from any AI — all from your terminal or our GUI.
Bricks Builder is powerful.
Managing it at scale isn't.
Bulk updates are manual
Changing heading colors across 20 pages? Open each one. Find the element. Edit. Save. Repeat. That's an afternoon gone.
Media upload is tedious
Drag files from your desktop to WordPress media, then manually insert them into elements one by one. Every. Single. Time.
Other AI tools lock you in
Existing AI plugins force their models, their interface, their subscription. You can't bring Claude, Codex, or your own API keys.
Styles stay siloed
Want to copy a style from one page to another? Screenshot it, recreate it manually. There's no "apply this everywhere."
What if you could just talk to your website?
Your workflow, your way
Chain commands together, pipe into other tools, automate with cron. Works with any AI agent — Claude Code, Codex, or your own.
- ✓Pipe and chain commands like Unix tools
- ✓Bring any AI agent — Claude, Codex, OpenCode
- ✓Automate with cron, CI/CD, or scripts
- ✓Works alongside your existing dev tools
Everything at your fingertips
Tab directly into your site’s pages, colors, styles, and images — all inline in the prompt. No more switching tabs to copy values.
- ✓@mention pages, colors, components inline
- ✓Save and reuse prompt templates
- ✓Multi-site management — switch instantly
- ✓Multiple concurrent sessions
- ✓Visual preview before pushing changes
Build your design system
Download starter templates, create your own from existing pages, or generate new ones with AI. Style profiles keep your brand consistent.
- ✓Download, create, or AI-generate templates
- ✓Style profiles enforce brand consistency
- ✓Export and share with your team
- ✓Apply templates across multiple pages
See it in action
Pick a task. Watch the difference between CLI precision and GUI convenience.
Not another AI WordPress plugin.
See how Agent to Bricks is different.
What you can do
Things you can do on day one.
Upload images into a gallery
Point it at a folder. It uploads everything and builds the gallery section. Done.
Generate a landing page
One sentence in, full page out. Hero, features, testimonials, CTA. All using your ACSS classes.
Convert HTML to Bricks
Write HTML with your classes. The CLI turns it into Bricks elements and maps class names to IDs.
Search and replace across pages
Find every button, heading, or class usage site-wide. Change them all in one pass.
Roll back any change
Every push saves a snapshot. Something wrong? One command to undo it.
Apply a style profile
Define your brand fonts, colors, and spacing once. Every generated section follows your rules automatically.
Get started
Five steps. Under five minutes.
Install the WordPress plugin
Download from GitHub releases, upload in WP admin.
Generate an API key
Settings → Agent to Bricks → Generate API Key
Install the CLI
tar xzf agent-to-bricks_*.tar.gz && sudo mv bricks /usr/local/bin/ Connect to your site
bricks config init Verify it works
bricks site info Why I built this
I kept watching the same thing happen. A new AI tool for WordPress launches, looks good in the demo, then you see the pricing page. $29/month. $49/month. $99 for the "agency tier." On top of everything else you're already paying for.
Bricks has a clean data model and real CSS control. I wanted AI tools that matched that quality. So I built a CLI that does it for free. You bring your own AI agent, use your own API keys, run it from your own machine.
Honestly? I hope Bricks ships native AI tools that are better than this. When that happens, this project can quietly retire. Until then, it's here.
Agent to Bricks is an independent open-source project. It is not affiliated with, endorsed by, or connected to Bricks Builder.