VigIA · Version history
VigIA changelog and version history
- Latest version
- 2.8.5
- Nov 9, 2026 (today)
- Releases
- 65
- since 2026
- In the last year
- 65
- about one every 5 days
- Tested up to
- WordPress 7.1.4
- PHP 7.4 or later
202665 releases
VigIA 2.8.5Latest
- With Visibility 3.2.4 or later, the home page carries a single WebSite node, the one Visibility prints with its site name, and the AI Discovery pointers of VigIA go into it.
- Improved: The AI Discovery pointers (llms.txt, llms-full.txt and Markdown for agents) now go into the WebSite node that Visibility prints, without repeating the ones Visibility already announces for what it serves itself. That includes a site where Visibility prints its own Site Identity: until now…
- Fix: With Visibility 3.2.4 or later, which prints a WebSite node on the home page with a site name of its own, earlier versions of VigIA printed a second one with the same identifier and the site title as its name. On the home page Visibility then left its own out, so the site name set there never…
VigIA 2.8.4
- Keeps caches in front of the site that follow Cache-Control from showing people the Markdown version of a page when an AI agent asked for it first, or from passing on cookies set by other plugins. Purge that cache after updating.
- Fix: A page asked for with an Accept: text/markdown header, which is how some AI agents ask for the Markdown version, now gets that Markdown as private, so caches in front of the site that follow Cache-Control no longer store it. Some hosting caches keep one copy per address and ignore the Vary: Ac…
- Fix: When another plugin had already given the response a cookie, as a store or a consent banner does when it opens its session, the .md addresses and the llms.txt and llms-full.txt files served by WordPress still went out as public for an hour, so a cache in front of the site could keep that cooki…
VigIA 2.8.3
- Fixes the visitor address behind proxies that add a port, keeps the network root files for network administrators, warns when the server sends llms.txt without UTF-8, closes an MCP window left by updates from 2.7, and fixes formatting in llms-full.txt.
- Improved: The Delivery section of llms.txt warns when the web server sends the physical files without saying they are UTF-8. Browsers and some AI tools then show accented letters as odd symbols, although the file is correct. VigIA asks the server each time the files are generated from the admin, pr…
- Fix: On hosts whose proxy writes the port next to the visitor address in X-Forwarded-For or X-Real-IP (Azure App Service does, as 203.0.113.7:51234 or [2001:db8::1]:443), the block list and the visit log saw the address of the proxy, so a visitor blocked by IP was never matched there. VigIA now dro…
- Fix: A site updated from 2.7.x or earlier counted the MCP switch as on until somebody opened wp-admin, and since 2.8.1 that also let the abilities answer on the core REST route during that time. The switch is now decided on its first read, wherever it happens: on only where a client had been connec…
- Fix: On a multisite network, an administrator of the main site who is not a network administrator could change the robots.txt, llms.txt and llms-full.txt at the network root, which every site of the network serves. Those changes now need a network administrator: the AI crawler rules when there is a…
- Fix: In llms-full.txt, a line break no longer starts a bold run and an image no longer starts an italic one, a line break without a new line after it no longer glues two lines together, and a heading written right after other text now goes on a line of its own.
- Fix: Code cleanup. The robots.txt compliance query is now prepared as a single statement, and the remaining database suppressions say why on their own line. What the query returns does not change.
VigIA 2.8.2
- Blocking by IP can no longer be bypassed with a forged proxy header, and the visit log no longer takes the visitor address from headers that anybody can send.
- Improved: New vigia_trusted_proxies filter, to declare the addresses or ranges of a load balancer, or of a CDN other than Cloudflare, that sits in front of the site, so VigIA reads the visitor from its X-Forwarded-For header. Declaring a proxy stops VigIA from trusting the site’s own network on its…
- Fix: A visitor blocked by IP got the page back by sending an X-Forwarded-For, CF-Connecting-IP or X-Real-IP header with any other address, and any visitor could write the address they wanted into the visit log. VigIA now uses the address of the connection. It believes CF-Connecting-IP only from Clo…
- Fix: Behaviour change that comes with the previous fix: behind a CDN other than Cloudflare, a load balancer with a public address, or a proxy with a public address between Cloudflare and the site, the visit log and the block list now see the address of that proxy until it is declared with the new f…
- Fix: A blocked IPv6 address written differently from the way the server reports it (upper case, leading zeros) never matched, and neither did an IPv4 address that reached the site written as IPv6.
VigIA 2.8.1
- The MCP switch now governs the VigIA abilities on every channel, not only the endpoint of this plugin, the nine abilities are now listed in the WordPress abilities directory, and two of them no longer fail when a client sends no parameters.
- Improved: The MCP switch now governs the nine VigIA abilities on every channel. With the server off they reject every call, whichever way it arrives. Behaviour change: until now the switch closed only the endpoint of this plugin, and an ability stayed callable through an MCP server that another plu…
- Improved: New vigia_abilities_require_mcp_switch filter, to untie the abilities from the switch on a site that reaches them through the core REST route and wants nothing to do with MCP. Capability checks are not affected by it.
- Improved: The nine abilities declare the public meta flag, so they show up in the WordPress abilities directory at /wp-abilities/v1/abilities, which WordPress 7.1 turns into the canonical way for an agent to find them. Listing is not calling: a call still needs manage_options, and the four write ab…
- Fix: Two abilities, vigia/get-blocked-items and vigia/get-robots-rules, refused a call that carried an empty object of arguments, which is what an MCP client sends for a tool that takes no parameters. They declared an empty input schema, and WordPress answers ability_missing_input_schema when the s…
VigIA 2.8.0
- The MCP server is now off by default and runs on the free MCP Adapter plugin, which VigIA no longer bundles, so the package is half the size. Where an AI client was already connected it stays on, and VigIA tells you if MCP Adapter has to be installed.
- New: The MCP server has a switch, in VigIA > Extras > MCP, and it is off by default. Until now its endpoint was registered on every site running WordPress 6.9 or later, whether or not anybody had connected an AI client. Turn it on only if you use it.
- New: The MCP tab says which MCP Adapter the server runs on, with its version, and offers to install or activate the MCP Adapter plugin when the site does not have it. Its status now reports whether the endpoint is really registered, not whether the adapter could be loaded.
- Improved: VigIA no longer bundles the MCP Adapter. The server runs on the official MCP Adapter plugin, free on WordPress.org, which is how its authors now ask plugins to use it, or on the copy that another active plugin already runs. The package goes from 293 files to 35 and its zip from 747 KB to…
- Improved: On update, a site where an AI client had been connected (one with the VigIA MCP Application Password) keeps the server on. If no MCP Adapter is running there, a notice on the dashboard says so, and the server is back as soon as the MCP Adapter plugin is installed and active. On every othe…
- Improved: VigIA no longer starts the adapter itself, so the adapter’s own default server (/wp-json/mcp/mcp-adapter-default-server) is only there when the MCP Adapter plugin or another plugin starts it.
- Improved: Quick Connect names the MCP server after the site (for example vigia-example-com) instead of a fixed vigia, so several sites with VigIA can be connected from the same client. Connections already set up keep working: the name only lives in the client.
- Improved: The MCP tab points to the Authorization header test of Site Health for the client that answers 401.
- Fix: The safe merger wrote every site as vigia, so merging a second site into a Cursor or Claude Desktop config replaced the first one. Each site now goes in under its own name, and an old vigia entry is only replaced when it points at this same site.
- Fix: Saving the JSON-LD settings, or running the AI Visibility analysis, ended in a fatal error on PHP 8 when a URL field arrived as a list instead of a text. Only an administrator could cause it, on their own request.
- Fix: Deleting the plugin with its data left the MCP read-only setting and the stored version number in the database.
- For older changelog entries, please check the changelog.txt file
VigIA 2.7.0
VigIA 2.6.8
VigIA 2.6.7
VigIA 2.6.6
VigIA 2.6.5
VigIA 2.6.4
VigIA 2.6.3
VigIA 2.6.2
VigIA 2.6.1
VigIA 2.6.0
VigIA 2.5.0
VigIA 2.4.5
VigIA 2.4.4
VigIA 2.4.3
VigIA 2.4.2
VigIA 2.4.1
VigIA 2.4.0
VigIA 2.3.0
VigIA 2.2.0
VigIA 2.1.0
VigIA 2.0.3
VigIA 2.0.2
VigIA 2.0.1
VigIA 2.0.0
VigIA 1.12.1
VigIA 1.12.0
VigIA 1.11.0
VigIA 1.10.2
VigIA 1.10.1
VigIA 1.10.0
VigIA 1.9.5
VigIA 1.9.4
VigIA 1.9.3
VigIA 1.9.2
VigIA 1.9.1
VigIA 1.9.0
VigIA 1.8.1
VigIA 1.8.0
VigIA 1.7.1
VigIA 1.7.0
VigIA 1.6.1
VigIA 1.6.0
VigIA 1.5.0
VigIA 1.4.1
VigIA 1.4.0
VigIA 1.3.0
VigIA 1.2.9
VigIA 1.2.8
VigIA 1.2.7
VigIA 1.2.6
VigIA 1.2.5
VigIA 1.2.4
VigIA 1.2.3
VigIA 1.2.2
VigIA 1.2.1
VigIA 1.2.0
VigIA 1.1.1
VigIA 1.1.0
VigIA 1.0.0
Questions about VigIA’s releases
What is the latest version of VigIA?
2.8.5, released on Nov 9, 2026 (10 hours ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.
How often is VigIA updated?
65 releases in the last year, about one every 5 days. Its first release on WordPress.org dates from January 2026.
Know when your rivals ship
Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.
Start freeRelease dates come from the day each version’s folder was made in VigIA’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.