Use Avius to update content, inspect your setup, and work with site files through your AI agent. Pro adds project memory and instructions for supported plugins and themes.
Read the active plugins, theme, content, and relevant settings before deciding what to change. Your agent can investigate the current installation instead of relying on a description of it.
Start with a read-only request when connecting a site for the first time. A clear inventory makes the next instruction more specific.
Work with pages, posts, and structured content through the tools available on the site. For builder-specific work, dedicated abilities and playbooks give the agent a more appropriate starting point.
Ask for a small change, then inspect the rendered page. A successful tool response is a reason to verify the result, not proof that every layout is correct.
Explore integration coveragePHP execution, file operations, and WP-CLI access support tasks that reach beyond a page editor. These capabilities can affect the database, plugin behavior, and site configuration.
Use a development or staging installation with a current backup. File recovery mechanisms do not make every database change reversible.
Understand site accessSave project conventions and useful facts in site memory. A later session can retrieve them instead of asking you to repeat the same context.
Memory is a deliberate record, not a promise that every conversation is retained. Review it as the project changes, and avoid storing credentials.
Read about project memoryThe activity view records tool calls and their outcomes so you can follow an agent session. It helps you understand which operations ran and where a task needs attention.
An activity record is not a backup or an automatic approval barrier. Keep the same review discipline you would use for any change to a site.
