The Antimanual Companion Plugin (Chat + KB)

Summary: The Antimanual Companion Plugin connects Antimanual Builder Pro to AI providers for chat-based generation, refinement, and migration. It is optional for manual workflows, but required for guided AI features, secure provider settings, and knowledge-base-powered editing inside the builder.

The Antimanual Companion Plugin is the optional AI connection layer for Antimanual Builder Pro. It enables chat-based page generation, conversational refinement, and AI-assisted migration while keeping the builder focused on visual editing, imports, reusable components, and design control.

If your team works manually, you can continue using Antimanual Builder Pro without the companion plugin. If you want AI features, the companion plugin becomes the bridge between the builder and your chosen AI provider, allowing Builder to read provider settings securely from one central location.

What the Antimanual Companion Plugin Does

The companion plugin connects Antimanual Builder Pro to supported AI services and prepares the knowledge base used for guided, chat-driven workflows. This makes it possible to generate a page from a prompt, refine content through conversation, and restructure existing pages with AI assistance.

• Connects Antimanual Builder Pro to your selected AI provider
• Stores and exposes the provider, model, and API key settings securely
• Enables prompt-based generation and conversational editing
• Supports knowledge-base-style guidance for smarter refinement
• Assists with AI-powered migration and content restructuring

When You Need It

You need the Antimanual Companion Plugin when you want chat-driven AI workflows inside the editor. It is especially useful for teams that want to generate pages quickly, improve sections conversationally, or migrate content with AI assistance.

If your workflow is purely manual, the companion plugin is not required. Antimanual Builder Pro still provides drag-and-drop layout, inline canvas editing, responsive previews, templates, and content migration without any AI connection.

AI Source Options in Antimanual Builder

Antimanual Builder supports two practical AI source approaches. The best option depends on whether you need fast one-shot generation or a more guided chat experience with knowledge-base support.

• WordPress AI Connectors: best for direct, one-shot generation inside WordPress 7.0 and later
• Antimanual Companion Plugin: best for chat, refinement, and guided AI workflows
• Use the option that matches your team’s permissions, provider setup, and editing style

The companion plugin is the better choice when you want ongoing conversational editing, AI-assisted redesign, or a workflow that can use a knowledge base to shape responses more intelligently.

Supported AI Providers

Through the companion plugin, Antimanual Builder can work with several major AI providers. Your exact setup depends on the provider and API key you configure in the companion plugin settings.

• OpenAI
• Google Gemini
• Anthropic
• xAI Grok
• DeepSeek
• OpenCode Zen

For teams that prefer a minimal setup, WordPress AI Connectors can be used for simpler generation tasks. For deeper editing workflows, the companion plugin provides the broader chat-based experience.

How to Set It Up

Setup is straightforward once the free base plugin and Pro features are installed. After activation, open the Antimanual Builder Pro settings area and connect the companion plugin or enable the AI source you want to use.

• Install and activate the free Antimanual Builder base plugin
• Install and activate Antimanual Builder Pro
• Open the Builder Pro settings in the WordPress dashboard
• Install or activate the companion plugin from the settings screen if prompted
• Select your AI provider and enter the API key
• Save the settings and confirm the connection

Why the Companion Plugin Is Optional

The companion plugin is optional by design. This allows teams to start with manual building, keep the editor lightweight, and add AI later only when needed. It also helps preserve existing workflows for users who do not want provider integration at all.

If you later decide to use AI, you can activate the companion plugin without rebuilding your pages. This makes it easier to introduce automation gradually while keeping full manual control over the design process.

Best Practices

• Use the companion plugin only when you need AI-driven editing or migration
• Keep your provider API key stored in the companion plugin, not in page content
• Review AI-generated sections before publishing
• Use manual editing for final layout, spacing, and brand adjustments
• Check Spider Themes Helpdesk for deeper guidance when working through advanced workflows

Summary

The Antimanual Companion Plugin extends Antimanual Builder Pro with AI-powered chat, guided refinement, and migration support. Use it for intelligent page generation and conversational workflows, or skip it when you only need the visual builder and manual editing tools.