Respira Code

Developer access to your WordPress site, for your AI agent.

Small apps and database work. No SSH. One command back.

100 launch licences · 46 left

Respira lets your AI agent edit the pages on your WordPress site. Respira Code lets it work on what is underneath: code, the database and how your plugins work.

  1. You ask.

    Add a sign-up form with a confirmation email.
  2. Your agent writes the code or the query.

  3. It goes live only after it passes the checks.

Undo any time.

Five flat plates stacked inside a clear enclosure, from top to bottom: a screen, a row of modules, a keyboard, a perforated plate and a base plate. Numbered 1 to 5, they match the five layers in the list: content, plugins and settings, apps, database, agent workflows.

What Respira Code adds, layer by layer.

Content

Respiraedits it

Respira CodeNothing to add

Plugins and settings

Respirainstalls and configures them

Respira Codereads their hooks and routes

Code

RespiraNothing to add

Respira Codebuilds features that run on your site

Database

RespiraNothing to add

Respira Codeguarded SQL, migrations and undo

Agent workflows

Respiraplaybooks, undo for pages

Respira Codeundo for apps and data too

Respira Code runs on top of Respira. No SSH, no app password.

All 20 capabilities
Yes In part Not reachable Respira With Respira Code

01 Content

  • Read and write pages, posts, menus, media and SEO

    Respira: Yes With Respira Code: Yes
  • Stylesheets and JSON in the active theme: CSS, SCSS, LESS, JSON

    Respira: Yes With Respira Code: Yes
  • Every write lands on a draft, one restore away

    Respira: Yes With Respira Code: Yes

02 Plugins and settings

  • Install, update, activate, settings, redirects and cache

    Respira: Yes With Respira Code: Yes
  • Call the abilities that plugins register

    Respira: Yes With Respira Code: Yes
  • Understand installed plugins: their hooks, routes and settings, read from the site itself

    Respira: Not reachable With Respira Code: Yes

03 Apps

  • Build features as apps, shipped as versioned releases

    Respira: Not reachable With Respira Code: Yes
  • REST routes, admin screens and scheduled jobs

    Respira: Not reachable With Respira Code: Yes
  • Email with a send-once ledger, and secrets the agent never sees

    Respira: Not reachable With Respira Code: Yes
  • Code checked before it runs

    Respira: Not reachable With Respira Code: Yes
  • Canary deploy, automatic fallback on a fatal, one-command rollback and an off switch

    Respira: Not reachable With Respira Code: Yes
  • App features open to any agent as WordPress Abilities

    Respira: Not reachable With Respira Code: Yes
  • Copy an app to another site

    Respira: Not reachable With Respira Code: Yes

04 Database

  • SQL reads with row and time caps, secrets redacted

    Respira: Not reachable With Respira Code: Yes
  • Guarded writes: dry run first, row snapshots

    Respira: Not reachable With Respira Code: Yes
  • Migrations and custom tables, with table snapshots

    Respira: Not reachable With Respira Code: Yes
  • Take over existing tables, with the owner’s approval

    Respira: Not reachable With Respira Code: Yes
  • Erasure and retention for personal data

    Respira: Not reachable With Respira Code: Yes

05 Agent workflows

  • Playbooks and plan mode

    Respira: Yes With Respira Code: Yes
  • One undo across a whole sessionRespira: pages only. With Respira Code: pages, rows and releases.

    Respira: In part With Respira Code: Yes

Respira alone 6 of 20 in full, 1 in part, 13 not reachable

With Respira Code 20 of 20 in full

What Respira needs. The Respira plugin, a licence, and an agent connected over MCP or the CLI.

What Respira Code adds. The add-on, on top of Respira. The site owner sets it up on three screens and switches developer access on for 24 hours. It uses the same connection. First deploys and sensitive tables need the owner’s approval. PHP runs only inside app releases: WordPress core, other plugins’ code and the parent theme are never edited.

What keeps a live site safe.

Tested before visitors see it.

Every release runs on its own first and has to pass health checks.

canary passed in 88 ms

A broken release takes itself back.

A hidden bug costs one failed request, then the previous version serves again.

1 failed request

One command undoes it.

Roll back to the release before.

711 ms to roll back

You stay in charge.

The first deploy of an app waits for your yes on that exact release. Three switches turn everything off.

a rollback does not undo database changes

What agents have built, and what to ask for.

Each card says where it ran: on a live site, on a test shop, or nowhere yet. Each one lists what it leaves on your site.

Organic growth

A page in wp-admin that reads the site’s Google Search Console numbers and turns them into the few changes most likely to bring more clicks this week.

Built on urbankid.ro, a live site run by Respira’s founder.

Prompt to start from
Add a page to wp-admin that reads my Google Search Console numbers and shows clicks, impressions, click-through rate and average position against the 28 days before. Pick the few changes most likely to bring more clicks this week, say why for each, and give each one a button that copies a prompt I can hand back to you. Make every fix on a draft and wait for my yes.

What it leaves on your site

  • A page in wp-admin with clicks from Google, impressions, click-through rate and average position, each against the 28 days before, and a chart of clicks and one of impressions per day.
  • This week’s priorities: the five changes with the most clicks to win, each with the reason, what to do and an estimate of the clicks a month in reach. The estimate points to where the most is to win and is not a promise.
  • The rules it applies, written out in plain words: a page that ranks 4 to 20 for a search, a page on page one with far fewer clicks than its position usually earns, a page that lost clicks or impressions, two pages showing for the same search, and searches that were not there before.
  • A “Copy agent prompt” button on each priority and one for all five. The prompt asks the agent to make the change on a draft through Respira and to publish only after the owner says yes.

It needs the Site Kit plugin connected to Google Search Console. It reads the data as the administrator who opens the page, and it rebuilds the report when it is older than 20 hours or when Refresh is pressed.

The Organic growth page in wp-admin on urbankid.ro. A header reads Search Console, urbankid.ro and Organic growth, above five tiles: clicks from Google, impressions, click-through rate, average position and the share of impressions on paid articles, each against the 28 days before. Below are this week's priorities, a button that copies one prompt for all five, and the first priorities, each with a Copy agent prompt button, next to two charts of clicks and impressions per day.
The page as it runs on urbankid.ro.
The top of This week's priorities: a green bar with a Copy prompt for all five button, then the first priority, an article marked Near page one, with its position for a search, what to do, and a Copy agent prompt button beside Edit, View page and Queries in Search Console.
Each priority has a button that copies a prompt for the agent.
Two line charts, Clicks per day and Impressions per day, each showing the last 28 days as a solid line against the 28 days before as a dashed line.
Clicks and impressions, against the 28 days before.

A Black Friday sale

An agent built this as one small app on a test shop: about 1,100 lines of PHP, a stylesheet, a countdown script and one database table.

Prompt to start from
Run a Black Friday sale in my shop: 10, 15 or 20 percent off by basket size, taken off in the cart by itself, and a landing page with a countdown that ends when I say.

What it leaves on your site

  • A landing page with a countdown and the products on sale, old price and new price.
  • A cart that takes the discount off by itself, with no code to type: 10, 15 or 20 percent by basket size, 5 percent more for returning customers, one category left out and one at a flat 25 percent.
  • A settings screen in wp-admin for the tiers and the dates. The sale ends at the minute the owner set.
  • An admin-only report of orders, revenue and discount given.
The sale landing page on a test shop: a dark panel with the words Black Friday and a countdown in days, hours, minutes and seconds, a box listing how the discount works, and a grid of products each with an old and a new price.
The landing page, on a test shop.

How it went

  1. Asked

    A sale with tiers by basket size and a page with a countdown, for a test shop.

  2. Approved

    The first deploy of the app waited for the owner to say yes on one wp-admin screen.

  3. Checked

    The first release was refused because the landing page lacked a tag the check looks for, so it never went live. The agent fixed it and the next release passed. In a deliberately bad copy, lint stopped an eval call, an unsanitised request value and an unprepared query before anything was written.

  4. Live

    The fixed release served the sale page and the cart discount.

  5. Rolled back

    A deliberately broken release was refused while the live page kept serving. One command from the respira CLI, respira app rollback, put the release before back in about half a second.

The wp-admin screen titled First deploys waiting for you, with the app name, its release number and a green button labelled Allow the first deploy.
The owner's yes, on one wp-admin screen.
A cart with three products, a subtotal, a line reading Black Friday discount with 15 percent on the basket plus 5 percent welcome back, and the estimated total.
The cart takes the discount off by itself.
The sale settings screen in wp-admin: a green line saying the sale is running, four counters for orders, revenue, discount given and returning buyers, then the start and end time, the tiers by cart total and the returning customer percentage.
The settings screen and the sales report.

More examples.

Three sets of tools, one connection.

  • 302core tools for the site you have
  • 104tools for your store
  • 10Respira Code tools that build the rest

Built on a year of Respira.

Respira turned one on 14 November 2026. In that year Respira shipped 583 releases, and it keeps 3,878 sites breathing.

  • 583releases
  • 3,878sites connected
  • 19page builders supported

100 launch licences for Respira Code.

Respira Code, the add-on that lets an AI agent build small apps and features on a WordPress site, is included in these yearly plans instead of costing €158 a year or €20 a month.

For Respira's first birthday.

Customers already on these plans have their place. The places left go to people who subscribe to, or upgrade to, one of them. It stays included for as long as the plan stays on yearly billing.

When all 100 are taken, Respira Code is included in no plan. It becomes a paid add-on for everyone, at €158 a year or €20 a month.

Who gets it included, and who adds it.

Included

Yearly plans: Builder with 10 sites or more, and Studio. Founder, on any billing cycle.

As an add-on

Every other plan, monthly or yearly, and every plan once the launch licences are taken. The prices are in the section above.

Not part of a free trial.

How to start.

  1. Add Respira Code and switch it on. In wp-admin open Respira Code in the menu, read its three screens and press Switch Respira Code on.

  2. Give a key developer access. Press Give developer access on a Respira key, or Create a Respira Code key. Only you can do this, in wp-admin.

  3. Install the Respira CLI on your machine, and connect your site.

    Install
    npm install -g @respira/cli
    respira sites connect https://your-site.com
    respira app init my-app
  4. Paste this into Claude Code, Codex or Cursor.

    First prompt
    Use the respira CLI on my connected site. Run respira site brief to see what this key may do, then scaffold an app with respira app init event-rsvp. Build an RSVP form with a capacity limit and one reminder email per person. Run respira app lint, deploy with respira app deploy, and tell me what the canary checked.

It needs WordPress 6.0 or newer, PHP 7.4 or newer, and Node 18 or newer on your own machine. It does not work on a multisite network yet. Start on a staging site if you have one.

Questions before you start.

What is an app here?

A small feature that runs on your WordPress site, such as a form, a report or a daily email. Your agent writes it as plain PHP files, and Respira Code deploys it as a numbered release you can roll back.

What does the site owner have to do?

Switch Respira Code on, give a key developer access, and allow the first deploy of each app on one wp-admin screen. Everything else is the agent’s work.

What can go wrong, and how is it stopped?

Every deploy is checked before it runs, and a release that fails is not served. One command rolls an app’s code back, but it does not undo changes the app made to the database. Three switches turn every app and key off: a button, a file and a line in wp-config.

What may I not build with Respira Code?

Respira Code is for things a site owner would be glad to show their visitors. It may not be used for phishing, hidden or deceptive code, unsolicited email, cloaking, collecting personal data in secret, payment forms outside the shop’s own provider, or attacking other sites. Respira can end developer access given through the Respira dashboard, then Respira Code access for the licence, and for a serious or repeated breach the licence itself, and abuse can be reported to word@respira.press. The full rule is Section 5.4 of the Terms.

What does it cost?

€20 a month or €158 a year as an add-on. It is included with Founder, and with yearly Builder (10 sites or more) and yearly Studio while the 100 launch licences last.

Is it safe on a live site?

Every release runs on its own first and has to pass health checks. A broken release takes itself back, and one command undoes any release.

What happens to my features if I stop paying?

Your features keep running. You cannot deploy changes until the add-on is paid for again; rolling back and switching an app off still work.

Do I need to be a developer?

You need a coding agent such as Claude Code, Codex or Cursor. You describe the feature; the agent writes it.

What will it not touch?

WordPress core, other plugins’ code and the parent theme. PHP runs only inside app releases.

Not a developer? Respira for WordPress edits the pages you already have, with no code.