VigIA 2.8.6 has 0 actions and 13 filters, read directly from its source code on Nov 18, 2026. The list updates automatically when a new version is released.
How to use these hooks
Actions let you run your own code at a specific moment. Filters let you change a value before the plugin uses it. Put your code in a child theme's functions.php or a code-snippets plugin, never in the plugin's own files, because updates overwrite them.
// Change a value VigIA is about to use
add_filter( 'robots_txt', function( $virtual, $blog_public ) {
// Change $virtual here.
return $virtual;
}, 10, 2 );Parts of a name in {braces} are filled in at runtime (for example a post type or field ID). Choose Example on any hook for a ready-to-edit snippet.
All hooks
-
/** * Filter the virtual robots.txt content. This is the same filter WordPress * applies, so plugins like VigIA that add rules will have their content * included. */ apply_filters( 'robots_txt', $virtual, $blog_public ); -
/** * Filter to disable write operations exposed through the Abilities API. */ apply_filters( 'vigia_can_write_via_abilities', true ); -
/** * Filter to untie the abilities from the MCP switch. */ apply_filters( 'vigia_abilities_require_mcp_switch', true ); -
/** * Filters whether an entry may be published on the AI surfaces (Markdown for * Agents, llms.txt, llms-full.txt and the excerpts derived from the content). */ apply_filters( 'vigia_content_is_public', $is_public, $the_post ); -
/** * Filter whether VigIA defers an emission signal to the Visibility sibling. */ apply_filters( 'vigia_defer_emission_to_visibility', true, $signal ); -
/** * Filter whether a post is eligible for markdown output */ apply_filters( 'vigia_markdown_post_eligible', true, $the_post ); -
/** * Filter whether a taxonomy term is eligible for markdown output. */ apply_filters( 'vigia_markdown_term_eligible', true, $term ); -
/** * Filters the capability required to reach the VigIA MCP endpoint. */ apply_filters( 'vigia_mcp_transport_capability', 'manage_options' ); -
/** * Filters the blocks left out of whatever is built for everybody from a * request that carries a session (llms.txt and llms-full.txt, built from * wp-admin). Add the block of any other plugin that paints the basket, the * notices or the name of the visitor. */ apply_filters( 'vigia_session_blocks', array( 'woocommerce/mini-cart', 'woocommerce/mini-cart-footer-block', 'woocommerce/mini-cart-title-items-counter-block', 'woocommerce/product-button', 'woocommerce/store-notices', 'woocommerce/classic-shortcode', 'woocommerce/cart', 'woocommerce/checkout', ) ); -
/** * Filters the shortcodes left out of whatever is built for everybody from a * request that carries a session. See `vigia_session_blocks`. */ apply_filters( 'vigia_session_shortcodes', array( 'woocommerce_cart', 'woocommerce_checkout', 'woocommerce_my_account', 'shop_messages', 'woocommerce_messages', ) ); -
apply_filters( 'the_content', $the_post->post_content ); -
apply_filters( 'vigia_markdown_term_posts_limit', 20, $term ); -
apply_filters( 'vigia_trusted_proxies', array() );
Generated from VigIA's GPL-licensed source code. Hooks inside bundled third-party libraries are not listed.
Done for you
Rather have it built for you?
Tell us what should change and we’ll write and test the code using these hooks.
Custom hook snippet
from $49
A small, update-safe change built on the plugin’s own hooks.
- Code written against the plugin’s actions and filters
- Tested on a staging copy of your site
- Install instructions included
Typical turnaround: 2–3 business days
Choose thisPlugin customisation
from $149
New features or changed behaviour, without editing the plugin’s files.
- Built as a companion plugin, so updates never wipe it
- Exact quote before we start
- Tested on staging, then deployed
Typical turnaround: 3–7 business days
Choose thisNot sure which fits? Describe what you need and we’ll suggest the simplest option.
Can't find the right hook?
We can build the customisation for you. Describe what you need: