WP Agent Bridge is a WordPress plugin that lets AI assistants such as ChatGPT, Claude, and Codex work with WordPress posts, pages, images, and settings. Requests such as “fix the table in this post” or “upload this image and set it as the featured image” reach WordPress through your own GitHub account.
A user-owned execution path with no relay server run by the project.
- No relay server: The path is “AI → your own private GitHub repository → your own WordPress.” In normal operation, your post content and operation requests are not sent to the project’s servers.
- No Bridge-imposed request limits: There is no cap on the number of operations and no per-operation charge. The limits of GitHub, your WordPress server, and the AI along the way still apply (Limits from GitHub and Other Services).
- Your own GitHub as the runtime: Operation requests and results are stored in a private repository you control. A site-specific GitHub App handles the connection and notifications.
Download and Installation
WP Agent Bridge 1.1.44
WordPress plugin ZIP
Previous stable releases
WP Agent Bridge Helper 0.3.1
Optional helper plugin for the AI side (shared by ChatGPT / Codex / Claude)
Checking release information. If the check fails, you can still download 1.1.44 above.
- Save the plugin ZIP with the button above.
- In WordPress, upload the ZIP from the Plugins screen and activate it.
- Follow the guidance in Tools → WP Agent Bridge to create a dedicated private repository in your own GitHub account.
- Use Connect GitHub to create a site-specific GitHub App, and connect it to that repository only.
- Give the AI you use read and write access to that repository (the GitHub app for ChatGPT / Codex, your own GitHub login for Claude; see the helper plugin below).
- Tell the AI the target URL and the change you want to make.
It requires WordPress 6.9 or later, PHP 7.4 or later, and OpenSSL, on a public HTTPS site that GitHub webhooks can reach. Detailed steps are in the official README (in Japanese).
AI-side helper plugin (WP Agent Bridge Helper, optional)
The Bridge works without the helper. The helper is an add-on for the AI side, and a single ZIP installs in ChatGPT desktop / Codex, Claude Code, claude.ai, and Cowork. It contains no credentials and does not grant any additional GitHub or WordPress permissions.
- Operating rules: Gives the AI the request format, how to check results, how to verify content before a change, and how to handle images.
- No premature “unavailable” verdicts: If the GitHub tools disappear partway through a conversation, the AI searches for them once instead of immediately concluding that WP Agent Bridge cannot be used.
- Transfer script (wpab.py): For AI tools that run in a terminal, such as Claude Code and Codex CLI, it sends requests and checks results with a fixed procedure. Where GitHub API writes are refused, it switches to
git pushautomatically.
ChatGPT desktop / Codex
Run codex plugin marketplace add takka-d/wp-agent-bridge --ref main, reload ChatGPT / Codex, and install WP Agent Bridge Helper from Plugins. If you are asked to connect GitHub, connect the GitHub account you use with WP Agent Bridge.
Manual install from the ZIP: Extract the helper ZIP to ~/.codex/plugins/wp-agent-bridge-helper/ (on Windows, %USERPROFILE%\.codex\plugins\wp-agent-bridge-helper\) so that plugin.json, .app.json, .codex-plugin, and skills sit directly inside that folder. Then create ~/.agents/plugins/marketplace.json (on Windows, %USERPROFILE%\.agents\plugins\marketplace.json) with the following content. If the file already exists, do not overwrite it; add the wp-agent-bridge-helper entry to its plugins array.
{
"name": "personal-plugins",
"interface": {
"displayName": "Personal Plugins"
},
"plugins": [
{
"name": "wp-agent-bridge-helper",
"source": {
"source": "local",
"path": "./.codex/plugins/wp-agent-bridge-helper"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Developer Tools"
}
]
}
Finally, fully restart the ChatGPT desktop app or Codex, then install the helper from Personal Plugins in Plugins. To update, replace the files in the same folder and restart. See also the OpenAI documentation for how this works.
Claude Code
claude plugin marketplace add takka-d/wp-agent-bridge claude plugin install wp-agent-bridge-helper@wp-agent-bridge
Inside a session, /plugin marketplace add takka-d/wp-agent-bridge and /plugin install wp-agent-bridge-helper@wp-agent-bridge do the same thing. GitHub writes use gh (GitHub CLI) signed in with your own account (gh auth login), so there is no need to put a token in a settings file. To update, run claude plugin update wp-agent-bridge-helper@wp-agent-bridge.
claude.ai / Cowork
In “Customize > Plugins > Add,” add https://github.com/takka-d/wp-agent-bridge as a marketplace, or upload the helper ZIP as is. Plugins you add are also synced to Claude Code the next time it starts. The write path to GitHub depends on where you use it.
- Cowork, or chats linked to the desktop app: Uses
ghalready signed in on the linked computer. - Claude Code on the web: Attach the private repository to the session with write access. Reads use
gh api, and writes usegit push. - claude.ai chats not linked to a computer: There is no write path, so WordPress operations cannot run there.
What Can It Do?
Edit posts and pages
Search posts, create drafts, change titles or publication status, edit part of a post, fix tables, and more. Content changes are checked against the current content before they are applied.
Manage images and media
Upload images and set featured images or site icons. The original image is sent in small chunks without modification, and WordPress checks its size and SHA-256 (a content fingerprint) before registering it.
Manage themes and site settings
Work with supported settings and menus, manage plugins and themes, and inspect or edit theme files. Confirmations and protections apply according to the type of change.
Continue editing larger files
Keep HTML, JavaScript, CSS, and similar files in a workspace, then read, search, and patch only the parts you need. Saved snapshots can be restored.
The available operations are defined by the capability list that the installed version generates. Not every WordPress plugin or custom feature can be handled the same way.
How It Works: Sending WordPress Requests Through GitHub
Writes with the GitHub app or your own GitHub login
Stores operation requests, results, and required working data
Site-specific GitHub App
Notifies WordPress of repository changes
webhook→
The AI does not rewrite the WordPress database directly. The Bridge installed in WordPress receives the request and runs the matching operation. The GitHub App provides notifications and access permissions; it is not a server that runs WordPress operations.
Example Requests
“Check the post at this URL and fix only the affected row in the pricing table. Keep it as a draft afterward.”
“Upload the attached image to the media library and set it as the featured image of the specified post.”
“Fix the description on this page. Check the part to change first, then apply it.”
A title alone can match several posts, so adding the URL makes the target easier to identify. If the URL, title, and post type contradict each other, or a title does not identify a single post, the Bridge refuses the request.
Data Handling and Change Protection
- Data path: Information needed for an operation is handled by the AI you use, GitHub, and your WordPress. Using a private repository does not make the setup fully local or independent of external services.
- Connection checks: The Bridge checks the notification signature and verifies the configured repository, GitHub App, and runtime branch.
- Checks before changes: For content patches and similar edits, the Bridge checks the planned change and the hash (a content fingerprint) of the original data, and refuses to apply the change if something else has changed in the meantime. The protection depends on the operation.
- Duplicate-execution protection: The Bridge has safeguards against running the same request twice. Even if a result is slow to arrive, do not resend the same change as a new request.
- Saved is not the same as displayed: A successful write or a matching hash does not prove that the page looks right. Check the actual page before publishing.
Operation requests and results can contain post content, and they also remain in the Git history. Treat access to the private repository as part of your site administration.
Limits from GitHub and Other Services
WP Agent Bridge has no request limits of its own, but the limits of GitHub, your WordPress server, and the AI along the way still apply. The figures come from each service’s official documentation as of November 2026 and from measurements on this site (takka-note.com).
| Item | Limit or guideline | What it means in practice |
|---|---|---|
| Round trip | Saved to GitHub → webhook → runs in WordPress → result saved to GitHub → read by the AI | On this site, the median time from creating a request to running it is about 7 seconds. Including waiting and approvals on the AI side, one operation can take tens of seconds or more. |
| API requests | 5,000 requests per hour (the base limit for both personal tokens and GitHub Apps) | Normal post editing rarely reaches it. Other tools that use the same account count toward it too. |
| Write rate | Up to 80 content-creating requests per minute and 500 per hour. GitHub recommends about 6 pushes per minute per repository | WordPress commits a result to GitHub for every operation. Sending hundreds of operations in a row can trigger temporary rejections and waits. |
| Webhooks | A delivery with no response within 10 seconds counts as failed, and GitHub does not redeliver it automatically | The Bridge picks up unprocessed requests the next time the repository is updated (up to 20 at a time). Requests older than 24 hours are not run. |
| Batch size | Up to 20 requests are processed per push, and each request can be up to 2 MiB (Bridge limits) | Split large batches. For large content changes, partial patches work better than replacing the whole post. |
| Images and files | Up to 6 MiB per file (Bridge limit). An image handed to the AI is split into 8 KiB chunks, and each chunk is sent as its own request | 1 MiB becomes about 128 requests. On this site, uploading an image of about 1.2 MB (150 chunks) took about 12 minutes. Shrinking images first, for example by converting them to WebP, is the reliable approach. |
| Repository size | Result files and processed requests are not deleted automatically. GitHub recommends no more than 3,000 entries per directory and 10 GB per repository | On this site, about two months produced about 10,700 result files and a repository of about 110 MB. Post content also remains in the history. |
| Server | The site must be public over HTTPS, with its REST API reachable by GitHub webhooks. PHP time and memory limits, WAFs (web application firewalls), and outbound connection limits still apply | Sites on a local machine or behind Basic authentication cannot receive webhooks. Large posts with many revisions can take longer to save, and plugins that transform content at display time also affect the result. |
| AI side | ChatGPT / Codex need the GitHub app. Claude needs a write path (Claude Code, gh on a linked computer, or Claude Code on the web) |
The GitHub app needs one file-creation call per request, so chunked uploads take many calls. GitHub states that its official remote MCP server does not support OAuth sign-in from Claude Desktop custom connectors. Usage limits and approval prompts on the AI side follow each service’s own terms. |
| GitHub outages | Operations cannot run while GitHub is down | The WordPress admin screens keep working as usual. |
The Bridge also limits how much a single read returns (for example, 1,000 lines or 256 KiB per content range read, 20 candidates per post search, and 50 entries per revision list). Long posts are read in several ranges.
Sources: GitHub Docs “Rate limits for the REST API,” “Handling failed webhook deliveries,” and “Repository limits”; github/github-mcp-server “Install GitHub MCP Server in Claude Applications”
FAQ
If the result file is “not generated,” did the operation fail?
A missing result alone does not mean the operation failed. If you check before WordPress has processed the request and saved the result to GitHub, the result will not be there yet.
| Observed state | Meaning and next check |
|---|---|
| Result is not available yet | The outcome is still unconfirmed. Wait a little and check the result for the same operation ID. |
| GitHub access or result retrieval returns an error | This is a permission or retrieval problem. By itself, it does not show that the WordPress operation failed. |
| The WordPress result contains an operation error | The operation failed. Check the returned reason, such as a target mismatch or a mismatch with the content before the change. |
| A batch result covers only part of the work | Do not treat the batch as complete. Keep the items that succeeded, check for execution errors, omitted results, and items not started, and continue only what is still needed. |
If the result cannot be read, treat the outcome as “unconfirmed” and check the result of the original request first. Sending the same change again as a new request can run it as a separate operation.
What if the AI says partway through that it “cannot use WP Agent Bridge”?
In ChatGPT, the GitHub tools can disappear from the AI’s view partway through a conversation even when the GitHub app is connected. This is separate from the Bridge or WordPress being disconnected, and selecting GitHub again with @GitHub or the app picker brings them back. In Claude, it depends on whether that conversation has a write path to GitHub (see “AI side” in Limits from GitHub and Other Services).
Distribution and Use
WP Agent Bridge itself is free to download, install, and use. Terms and charges for external services follow each service. The source code is public, but the license restricts redistribution. See the official license for the exact terms.
Comments