> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/start-here/install-and-activate.md). # Install and activate Requirements, license activation, installation, upgrades and the setup checklist. ## Requirements | Requirement | Detail | | ----------- | ------------------------------------------------------------------------------------------------------------ | | WordPress | 7.0 or newer (tested up to 7.1). WP AI Manager uses the WordPress core AI Client added in 7.0. | | PHP | 8.1 or newer | | Account | An administrator who can install plugins and manage options | | License | A WP AI Manager license, activated through the Freemius screen the plugin adds | | AI provider | At least one WordPress AI Connector plugin and its API key, for Chat and model-backed Tasks | | Optional | Elementor, WooCommerce 10.9+, Rank Math / Yoast SEO / Slim SEO, a form plugin, UpdraftPlus, stock-image keys | Elementor is optional. Gutenberg and standard WordPress content work without it. ## Install {% stepper %} {% step %} ### Back up the site Take a full-site backup with your usual tool before adding any plugin. {% endstep %} {% step %} ### Upload the ZIP In WordPress go to **Plugins > Add New > Upload Plugin**, choose the WP AI Manager ZIP from your licensed download, and select **Install Now**. You can also upload the folder to `/wp-content/plugins/wordpress-ai-manager/`. {% endstep %} {% step %} ### Activate and enter your license Activate **WP AI Manager**. The Freemius activation screen opens. Enter your license key. License activation and renewal are handled by Freemius; its **Account** screen sits under the WP AI Manager menu. {% endstep %} {% step %} ### Open Home Go to **WP AI Manager > Home**. The **Needs you** area lists what is still missing, and the setup checklist links to each fix. {% endstep %} {% endstepper %} ## The setup checklist Home and **Settings > Onboarding** track six items. Each has a button that opens the right screen. | Item | Fix it with | | -------------------- | ----------------------------------------------------------------------------------------------------- | | License active | **Activate** opens the Freemius activation screen | | AI connector ready | **Open Connectors** goes to WordPress **Settings > Connectors** | | Models chosen | **Pick models** opens **Settings > AI Models** (optional: recommended models are used if you skip it) | | Brand Kit filled in | **Edit Brand Kit** opens Site Knowledge | | Site Context written | **Add Context** opens Site Knowledge > Context | | First task run | **Run a task** opens Tasks; start with Site health check | You can hide the onboarding banner from **Settings > Onboarding** once you are done. ## License states | State | What you see | What still works | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | | Active | **Settings > License** says the site has an active license | Everything | | Never activated | "Activate your WP AI Manager license to use AI chat and tasks" on admin screens, and an **Activate your license** card in Chat | Settings, Integrations, History | | Expired, within grace | Normal operation for **7 days** after a license that was valid is first seen as expired | Everything | | Expired, after grace | "Your WP AI Manager license expired. AI chat, tasks and scheduled runs are paused" with a **Renew** link, and a **Renew license** card in Chat | History and Undo | The grace period applies only to a license that was activated and then expired. A site that never activated a license gets no grace period. ## Upgrading from an earlier version 1. Back up the site, then upload the new ZIP and choose **Replace current with uploaded**. 2. Hard-refresh the admin (Shift + reload) so your browser loads the new scripts. 3. Open **Home** and **Integrations** to confirm nothing new needs setting up. 4. Before scheduled Tasks run again, open **Playbooks > Tasks and runs** and check each schedule. 5. If you connect external MCP clients over WP-CLI, restart them so they load the new code. Old menu addresses (Modules, Connection, Sandbox, MCP Log, Tasks) redirect to their new places in the workspace, so bookmarks still open, possibly on a different tab. ## Uninstall Deactivating keeps your data. Deleting the plugin from **Plugins** removes its settings, conversations, Task and skill posts, scheduled actions, backup folders under uploads and per-user notice flags. Download any backups you want to keep first. Next: [Connect AI and choose models](/documentation/start-here/connect-ai-and-choose-models.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.3techagency.com/documentation/start-here/install-and-activate.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.