Respira Code for WordPress
Build apps on WordPress with your agent, one restore away, on any host.
Respira for WordPress edits pages. Respira Code goes further: your agent can write a small application for your site, in PHP, SQL and scheduled jobs, and ship it without being able to take the site down or lose its data. These are called apps. This page says what the add-on is, who gets it and how to stop it.
What it adds to Respira
- An apps folder. Each app lives in
wp-content/respira-apps/<slug>/as immutable releases, with a pointer to the one that serves. - A crash guard. A release that fatals, runs out of memory or fails its checks never keeps serving. The previous release takes over.
- Guarded SQL and migrations. Every change to data has a snapshot first. Data has the rules.
- A kit with rules built in. Mail that sends once, secrets the agent cannot read, jobs that run one at a time, erasure links. The kit lists every function and Primitives explains the rules.
- The respira CLI and MCP tools.
respira app deployand the 10 Respira Code tools. See the reference. - Apps that move.
respira app pullreads an app back from one of your sites so you can deploy it to another.
wp-content/
mu-plugins/respira-code-loader.php the loader, installed by the add-on
respira-apps/
.disabled the kill switch (a file)
pen-pals/
current the release that serves
previous the last known good one
releases/1.0.0-57a4e4617547/ immutable: app.json, entry.php, migrations/, i18n/ Who gets it
Respira Code is included at no extra cost on Founder, in any billing cycle. While the 100 launch licences last, it is also included on yearly Builder plans with 10 sites or more, yearly Studio and legacy Agency. Maker and Builder 5 do not include it. Once the launch licences are taken, no other plan includes it. It is never part of a free trial.
Where it is not included, Respira Code costs €158 a year or €20 a month. Maker and Builder 5 can add it at that price, as can any other paid plan.
A launch licence belongs to the plan. It stays for as long as the plan stays on yearly billing and active. If the holder cancels, the place is not given to someone else, and a plan that is cancelled but still inside its paid period keeps Respira Code until that period ends. The number of places left is shown on the pricing page, on the Respira Code page and on your Downloads page. If a team member should use it, the owner grants that member's key explicitly.
If your licence lapses, nothing you built stops. Apps keep serving. Deploys, migrations and data changes are refused, while rollback, the kill switch, status and logs keep working. A bought add-on whose renewal is being retried keeps working for 7 days, and a site that cannot reach respira.press keeps working for 3 days after the last check that confirmed the licence.
What it needs
- A paid Respira plan. A free trial does not count.
- Respira for WordPress 9.3.10 or newer on the site.
Install
- Update Respira for WordPress to 9.3.10 or newer. Respira Code refuses to run on anything older.
- Download Respira Code from your Respira dashboard (the downloads page, or your Respira Code card on the sites page or the billing page), then upload it in wp-admin:
- In wp-admin, open Plugins, then Add New Plugin, then Upload Plugin.
- Choose the respira-code zip file you downloaded, then press Install Now.
- Press Activate Plugin. Then open Respira Code in the wp-admin menu and go through its three setup steps.
- The site owner finishes a three-screen setup in wp-admin: What it does, This host, and Rules and the off switch. On the last screen the owner chooses how long a key keeps developer access, types the site's domain and presses Switch Respira Code on. That switches Respira Code on for the site. It gives no key developer access. Until a key has it, no developer access exists.
- Connect the agent, in two blocks. First, the owner gives a key developer access. Second, the owner pastes the prompt from the screen to the agent. Both are described below.
Connect an agent
Block 1: give a key developer access. No separate key is needed. On the Respira Code screen, under Keys, the owner presses Give developer access on a key the agent already uses. If the site has no key yet, or the agent should have a new one, the owner presses Create a Respira Code key. Respira then shows a connect command once, with the key filled in, and the owner runs it in a terminal. Paste the key into that command, never into a chat.
Block 2: paste the prompt. Under Paste this to your AI agent, the screen shows a prompt with no key in it. The owner pastes it into Claude Code, Cursor or any agent that can run a terminal. The agent checks that the site is connected to the respira CLI and starts with the site brief.
Only a full access key that belongs to an administrator qualifies. Respira refuses the rest, and the Keys list says why on the key:
- A token from the Respira dashboard, including a team member's token, and a sign-in (OAuth) connection. Those are checked by respira.press and are not given access here.
- A read-only or limited key: limited to content scopes, to a tool profile other than full access, or to a list of tools.
- An expired key.
- A key whose owner is not an administrator, no longer exists, or is not on the site's Respira account or team.
An administrator can give developer access to another administrator's key. The Keys list then shows a box on that key to tick first, saying the owner means it.
Claude or ChatGPT connected through your Respira dashboard get developer access from the dashboard instead: once the setup in wp-admin is finished, the Respira Code card on your sites page switches it on for that site. Switching it on issues a new site key, shown once, and older keys for that site stop working. It lasts 24 hours at a time; the card arms it again, revokes it, or rotates the key. A team member gets it only when the owner grants it to them by name.
How long developer access lasts
The owner chooses, on the last setup screen and later on the Respira Code screen under Keys, then Change: 24 hours, 7 days, 30 days or Until I switch it off. A new setup preselects 7 days. The choice applies to keys given access from then on. Each key shows when its access ends and has a Disarm button that takes the access back at once. Shortening the window cuts the access of every key that already has it. A site set up before the choice existed stays on 24 hours until the owner changes it.
A key cannot give itself developer access, and neither can an agent's request. Only the site owner can, in wp-admin.
The respira CLI
The commands in these docs are written short, as respira site brief. If you have not installed the respira CLI, run each one as npx -y @respira/cli site brief --site my-site. After npm install -g @respira/cli the short form works as written. Always use the full package name, @respira/cli. The short name respira on npm is an alias Respira publishes that forwards to it, but agents and scripts should name the package itself.
WordPress multisite is not supported. A host that sets DISALLOW_FILE_MODS refuses uploads and deploys, and rollback still works.
The kill switch
One switch turns every key and every app off. While it is on, no app code is included, no database is touched, and the site runs as if the add-on were absent. It works even when wp-admin is down.
# an empty file, made with your host's file manager or FTP
wp-content/respira-apps/.disabled
# or this line in wp-config.php
define( 'RESPIRA_APPS_DISABLED', true ); There are three ways: the red Switch everything off button on the Respira Code screen, the file above, or the line in wp-config.php. It also engages by itself after three failed verifications in a row. Only the owner switches it back on, in wp-admin. No API key can.
Where next
Start with your first app, which goes from a site brief to a rollback. If you are handling people's data, read the safety rules before you deploy anything. To see every number, read Limits.