Respira turned one on 14 November. A year ago there was no plugin, no website and nobody using it. Today several things open at once, and I wanted to write down how the year went before I explain them.
Respira is the Romanian word for “breathe”. I am one person in Brașov, Romania, and everything here was built and answered by me.
How it started
It began with a task at my day job. The investor section of a Divi WordPress site had to be updated. Pages had to be created and changed, and more than 40 PDFs had to be uploaded and linked by hand. The deadline was tight, and the task allowed no mistakes. Done by hand, it would have taken days.
It did not need a clever script. It needed an AI that could work inside the site the way a careful person would: read what is already there, make each change in the page builder’s own format, and leave the live pages alone until someone had looked. So I built that. It is still a side project, and I still build it alone.
What the year held
Respira has shipped 583 releases since, counted by version in the plugin changelog, and it works with 19 page builders and platforms. Every release is on the releases page, with what changed in plain words. The respira CLI came in April. In July the WooCommerce add-on made stores agent-ready. In September came Murmur, Respira AER and Respira Exhale.
Three things I learned. Answering support myself is the best research I have, because a question that arrives twice usually means the product should have said something the first time. A live site should change only after a human says yes, so the edit lands on a copy, a snapshot is saved first and one step takes it back. And when one person carries the whole thing, small releases beat big ones. A fix is not news. I ship it and go back to the queue.
Respira Code opens today
Respira lets your AI agent edit the pages on your WordPress site. Respira Code lets it build small apps and features that run on the site itself, such as a sign-up form with its own table, a WooCommerce rule or a daily email, and do database work with snapshots and dry runs. It is an add-on on top of Respira and uses the same connection.
Every deploy is checked before it runs. A release that fails its checks is refused, a broken one takes itself back, and one command from the respira CLI returns the site to the release before. The first deploy of each app waits for your yes on one wp-admin screen, and an off switch stops everything.
Two examples run on urbankid.ro, a site I run myself. One is a widget on the wp-admin dashboard that counts which search engines and AI crawlers read the site, and which pages the AI assistants open most. The other is a page that reads the site’s Google Search Console numbers and turns them into the few changes most likely to bring clicks this week, each with a button that copies a prompt for the agent. My agent built both. Both are described, with their limits, on the Respira Code page.
The limits matter. Respira Code never edits WordPress core, other plugins’ code or the parent theme. An app’s code has the power of a plugin, which is why the checks, your approval and the off switch stand in front of it. You also need a coding agent such as Claude Code, Codex or Cursor.
A homepage with more air in it
The new homepage is shorter. You can click around a sample dashboard before you sign up, with nothing real to break. Further down, a made-up plant nursery shows the live page and the copy an AI changed, side by side. You drag a divider across, see the four changes, and approve or reject them. That is what Respira does on your site, shown instead of explained.
You will also see more of the natural world. Respira’s mark is a pinecone seen from above, and the brand grows out of pinecones and pine trees. I have a tattoo of a California pine cone, and it is what set me on this road. For a year the site was clean and corporate and left that out, so the pines are back, as photographs.
Pricing you can read
Plans are priced by site. The homepage has a slider over every site count the three plans sell, and the price per site moves as you drag it. On yearly billing it is €5.92 a month for one site and €0.99 a site at 250. The pricing page shows the same per-site number on each plan, with a comparison table under it.
The promise is in plain words. There is no charge per edit, and no plan has an edit allowance. There are no daily or weekly edit limits: the only limit is a safety cap on each connection that stops a runaway agent. And there are no AI fees. Connect the Claude, ChatGPT or Cursor plan you already pay for, or bring an API key to Respira AER.
A page that counts
The live page is the public record of what Respira is doing: a globe, a counter of lines of code updated through Respira, and a grid of activity across connected sites. It is counted from signed tool events and carries operation outcomes, never your WordPress content.
Murmur gets its own home
Murmur began inside Respira for WordPress. It now has a home of its own at murmur.link. Your client opens a link with no login, taps the spot on the page that should change and writes a note. You get the exact spot, a screenshot and the device, ready for your AI agent. It is made to work on any website. It is live on WordPress today, and every other website opens soon: the page takes your email and sends one message when it does.
Thank you
Earlier this month I also made a video and a page for everyone who builds on WordPress. It is the same bet as Respira: that WordPress is a good place for an AI agent to work, if the agent asks first.
Thank you to the people who use Respira and write back. I answer every message myself, and a reply usually arrives within a day. What you tell me decides what I fix first and what I build next.
Mihai Dragomirescu
Join the conversation
0 comments · Respira accountNo comments yet. Be the first to weigh in.