SEO TITLE: WordPress Presence API: Best Proven 5 Features in 2026
META DESCRIPTION: WordPress Presence API adds AI-agent visibility, new post locks, and multisite presence tools. What changed in October 2026 and what site owners should do.
FOCUS KEYWORD: wordpress presence api

WordPress Presence API Adds AI Agent Visibility, Post Locks, and Multisite Support

The WordPress Presence API moved decisively closer to WordPress core in October 2026, with a new “What’s new” roundup published October 2 and version 0.17.0 shipping October 8. The feature plugin, sponsored by the WordPress Core team, is building system-wide presence for a future WordPress release — tracking which users are logged in, which admin screens they are on, and which posts they are editing — and this month’s updates add AI-agent visibility, a new home for post locks, multisite tools, and per-site privacy controls. If your team edits content together, or you are experimenting with AI agents that touch WordPress, the WordPress Presence API is the infrastructure that will show who — human or machine — is in the editor.

What Happened: WordPress Presence API Updates Explained

In plain English, the WordPress Presence API is WordPress’s answer to the little “who’s here” row you see in Google Docs. It tracks presence across the admin and stores it in a dedicated wp_presence table fed by the Heartbeat API, with records expiring after 150 seconds. Crucially, it writes nothing to wp_postmeta, so a busy editor no longer invalidates cached post queries on every heartbeat — a performance property that is also the reason core wants to adopt it.

Here is what the recent WordPress Presence API releases delivered, in the order it matters to site owners:

1. AI agents are now visible in the editor. AI agents edit WordPress over REST and MCP, but until now nothing put them “in the room” — the person in the editor never saw them. GitHub issue #549 (opened September 24, 2026, by Joseph Fusco) proposed that agent rows carry an “Agent” label in Who’s Online, the admin bar, and the post list. An agent is identified via the Agent Users plugin (through the wpai_agent user meta, checked with wpai_is_agent_user()), and the agent writes its own presence row with wp_set_presence(), with its own expiry capped at one hour by wp_presence_max_expires_in and removed after execution. The plugin’s own directory page confirms the result: “AI agents labelled in the admin bar, the Active Posts widget, and the Editors column, once a plugin such as Agent Users marks them.”

2. Post locks moved into the presence table. This is the WordPress Presence API’s first real consumer. Today, every post-lock refresh writes post meta, which makes every cached post query stale on sites with a persistent object cache. Moving locks into the presence table eliminates that invalidation churn — and it is the technical motivation for core adoption.

3. Multisite support. Network admins get a Who’s Online dashboard widget showing the busiest sites and who’s on each, an “Online” column in the Sites list, and an Online view, filter, and column in the Users list. All of these require the manage_network capability. The multisite work item is closed in the core-proposal milestone.

4. Per-site feature switches and privacy controls. Version 0.17.0 (shipped October 8, 2026) added a switch for each feature under Settings → Presence API, so admins can enable only the presence surfaces they want. The core-proposal readiness table lists “Privacy and site control” as closed, and presence records’ short TTL (150 seconds) means stale data does not linger.

5. New developer functions and tooling. wp_presence_exchange() and wp_presence_leave() (shipped earlier in 0.8.0) are joined by REST endpoints, WP-CLI commands, filters, and documented room conventions; a Site Health check flags when Heartbeat cannot keep presence current. Version 0.17.0 also split the debugger and DB viewer into a separate presence-debugger plugin, and Presence Scenes gained arrivals, coming-back, and fading-out scenes. By October 18, version 0.18.2 was already being tested against WordPress 7.1.3 by third-party developers.

Who Is Affected by the WordPress Presence API Changes

The WordPress Presence API matters most to three groups. Editorial teams and agencies that co-edit posts will finally see who holds a post lock and who else is online, instead of discovering conflicts the hard way. Multisite network operators — universities, franchises, media groups — gain network-wide visibility into activity across sites. And anyone running AI agents against WordPress (content pipelines, design agents like Andy Peatling’s Miles) gets an audit trail of what the agent touched and when, visible right in the admin.

Just as important is what the WordPress Presence API is not: it is not in WordPress 7.2. Real-time collaboration was deliberately left off the 7.2 roadmap, and 7.2 (beta 1 on October 20, 2026; final planned early December) ships without it. The October 12 meeting set the merge gate as three outside projects plus eight weeks without a breaking API change counted from 0.17.0 — making December 3 the earliest possible merge date. Gutenberg-sync-engines is the first outside consumer. In other words, the API is stabilizing in public so it can land in a release after 7.2, not during it.

Why the WordPress Presence API Matters

Two deeper trends make this worth watching. First, the editor is becoming multi-actor: humans, AI assistants, and automated pipelines will share the same posts, and invisible actors are a security and workflow liability. Labelling AI agents in the WordPress Presence API is the first step toward accountable agentic editing. Second, WordPress’s collaboration story has been stuck for years — post-lock conflicts and stale caches are the symptoms. A presence layer with its own table and short TTL is the unglamorous foundation that makes real-time collaboration possible without wrecking performance. The fact that the core-proposal milestone has all 37 issues closed tells you this is no longer an experiment; it is a merge candidate.

What to Do Now: 5 Steps for Site Owners

1. Nothing to install today. The WordPress Presence API is still a feature plugin, not part of core. Do not install it on production sites expecting 7.2 behavior — it is not in 7.2.
2. If you run a multisite network, follow the plugin. The Network Admin presence widgets will change how you monitor your network. Watch the plugin’s directory page for the core-merge decision.
3. If AI agents touch your WordPress site, plan for the Agent Users plugin. Agent visibility in the WordPress Presence API depends on agents being marked through that plugin — make it part of your agent-deployment checklist so every agent action is attributable.
4. Developers: test against the beta, and use the escape hatch only as a stopgap. If your plugin compares, caches, or hashes anything downstream of post locks or presence data, test now and report breakages on the GitHub repo rather than silencing them.
5. Audit your editing workflow. If your team hits post-lock conflicts weekly, the WordPress Presence API’s approach is the long-term fix. Until it merges, a documented checkout discipline — and managed website care plans that keep your editor stack updated — prevents most conflicts.

FAQ

Is the WordPress Presence API part of WordPress 7.2?
No. Real-time collaboration was intentionally left off the 7.2 roadmap. The API’s earliest core-merge date is December 3, 2026, based on the stability gate set in the October 12 meeting — so it targets a release after 7.2.

How does the WordPress Presence API show AI agents?
When an AI agent is marked by a plugin such as Agent Users (via the wpai_agent user meta), its presence rows carry an “Agent” label in Who’s Online, the admin bar, the Active Posts widget, and the Editors column. The agent registers itself with wp_set_presence() and its row expires automatically.

Does the WordPress Presence API slow down my site?
It is designed not to. Presence data lives in a dedicated table with a 150-second TTL and never touches wp_postmeta, so heartbeats do not invalidate cached post queries. A built-in Site Health check warns if Heartbeat cannot keep presence current.

Can I turn parts of the WordPress Presence API off?
Yes. Since version 0.17.0, Settings → Presence API offers a switch for each feature, so you can enable only the presence surfaces your site needs.

Conclusion

The WordPress Presence API’s October 2026 updates — AI-agent visibility, post locks moved into a dedicated presence table, multisite dashboards, per-site feature switches, and maturing developer tooling — are the clearest signal yet that WordPress is building the foundation for collaborative, AI-assisted editing. It will not ship in WordPress 7.2, and that is fine: the project is choosing stability over speed, with a merge gate built on real-world testing instead of a release deadline. For site owners, the takeaway is practical rather than urgent: know that the editor is going multi-actor, make sure your AI agents will be attributable when presence lands, and keep your WordPress stack maintained so you can adopt it the day it merges. If you would rather not think about any of that, our website care plans handle updates, security, and maintenance for you — and if you are planning a site built for the block-editor era, our professional web design team builds modern, easy-to-edit WordPress sites. Have questions? contact us — Qamar Digital Ventures LLC keeps WordPress sites secure, updated, and ready for whatever core ships next.

Sources

• WordPress.org plugin directory — Presence API: https://wordpress.org/plugins/presence-api/
• GitHub — Presence API issue #549 (AI agent visibility): https://github.com/WordPress/presence-api/issues/549
• GitHub — Presence API issue #550 (core proposal / status): https://github.com/WordPress/presence-api/issues/550
• Make WordPress Core — Presence API meeting summary, October 12, 2026: https://make.wordpress.org/core/2026/10/12/presence-api-meeting-summary-october-12-2026/
• WP More Issue 59 (October 2026): https://wpmore.net/wp-7-1-3-checkout-summit-plugin-pricing-cant-work-like-this-wp-more-issue-59/
• attowp.com — Presence API 0.18.2 tested on WordPress 7.1.3: https://attowp.com/wordpress-development/wordpress-real-time-collaboration-plugin-authors-test/