Novamira HQ is a free desktop app that connects multiple WordPress sites running Novamira AI to your AI agent through one central connection. If you manage several websites, it brings site connections, Novamira Pro setup, and supported hosting tasks into one place.
Our quick look focuses on connecting sites, exploring the desktop app, and testing a small content migration, rather than providing a complete tutorial. The setup begins with a hosting account, although you can also add sites manually.
Key Takeaways
- Novamira HQ is a free desktop app that connects multiple WordPress sites running Novamira AI to an AI agent through a single connection.
- Sites can be added through supported hosting accounts or connected manually, and the dashboard can combine sites from different hosts.
- HQ supports remote Novamira Pro installation and selected hosting tasks, including staging pushes and backup requests, depending on the connected host.
Novamira HQ—Quick Look Video

One Connection for Multiple WordPress Sites
Without HQ, setting up Novamira across multiple websites means repeating the connection process for each site. Adding another website means returning to that setup work before bringing it into your AI workflow.
Novamira HQ’s free desktop app gives you a central place to handle those connections. You can bring in sites through a hosting account, add them manually, or combine both methods.
You can also mix hosts. For example, we use Kinsta in the walkthrough, but sites hosted with Rocket.net or many other hosting solutions could sit alongside those Kinsta sites in the same HQ dashboard.
Novamira is an InfluenceWP partner. You can see the Novamira listing and exclusive offer, and our earlier first look at Novamira AI covers the underlying WordPress capabilities in more detail.
Connect Hosting Accounts and Authorize Sites
Choose a Host or Add Sites Manually
Connecting a hosting account lets HQ fetch its websites, so you don’t have to enter every site separately.
At the time of our recording, the connection options included Rocket.net, Pressable, Pantheon, WP Engine, InstaWP, Hostinger, WHM, Plesk, cPanel, SandyWP, Cloudways, xCloud, and Kinsta.
We chose the hosting-account route for this demonstration. Manual connections remain available for sites you want to add outside those integrations.
Connect Kinsta With an API Key
We started with an empty HQ site list and connected our Kinsta test account:
- Open Hosting Accounts in HQ, choose Connect Hosting Account, and select Kinsta.
- Enter an account name, then open Kinsta to create an API key.
- In Kinsta, open the username menu, go to Company Settings, and select API Keys.
- Create a named key, choose its expiration, and copy it into HQ’s credential field.
- Select Save and Connect, then open View Sites.
For the test, we named the key Novamira HQ and selected a non-expiring option. HQ identified the Kinsta company ID from the API key, so we didn’t need to enter that separately.
The app fetched our two sites and displayed the available staging environment. We then selected Connect for each site and completed its authorization. Both sites were shown as connected afterward.
Push Changes Between Staging and Live
HQ includes a push feature for moving changes between a site’s staging and live environments. This lets you handle the operation without opening each site’s WordPress dashboard.
In the walkthrough, we opened New Push and selected staging as the source and live as the destination. The setup offered database and file options, including the ability to push both.
When the database is part of the operation, HQ also provides an option to search and replace URLs. After choosing the settings, Save Push submits the operation.
The direction can also go the other way. You can pull live data into staging before doing further work there.
We explored the push setup rather than demonstrating a completed deployment. The important connection is that staging and live environments are available within the same app where you manage the rest of the site’s HQ connection.
Connect an AI Agent to HQ
HQ also provides connection options for the AI tools you use to work with your sites. At the time of recording, the choices included Claude Desktop, ChatGPT Desktop, Cursor, Open Code, Claude Code CLI, Codex CLI, VS Code, GitHub Copilot, and Anti-Gravity.
We used Cursor. After selecting it in HQ, we chose Add to Cursor and confirmed the installation. Cursor then showed Novamira HQ as installed and connected.
For broader setup details, Novamira’s AI client connection documentation covers connecting compatible clients to WordPress.
To check our HQ connection, we asked the agent, “Show me my sites in Novamira HQ.”
The agent returned the two connected sites. That confirmed we could work with them through the single HQ connection.
We used voice to speak to the agent during the walkthrough. HQ also provides a command you can copy into your AI chat window for that initial check.
Install and License Novamira Pro Remotely
Save the Pro License in Settings
HQ has a Novamira Pro tab under Settings. If you hold a Pro license, you can store the key there for use on connected websites.
That saved license supports the remote installation process. Instead of opening each WordPress dashboard to install Pro and enter its license, you can start the process from HQ.
This applies to sites you own and client sites where you intend to use your Pro license.
Install Pro From the Site Menu
On our second test site (Novamira HQ 2), the free Novamira plugin was already installed, but Pro wasn’t present.
We opened the site’s three-dot menu in HQ and selected Install Novamira Pro. The app referenced the license saved in Settings, checked the site, and offered Activate License and Install Pro.
After HQ reported that installation was complete, we refreshed the site’s WordPress plugin screen. Novamira Pro was installed, active, and licensed.
One Pro feature we highlighted was memory. It can reduce the number of round trips an AI agent needs to make. Fewer round trips can reduce token use, which can also reduce AI costs.
For agencies, the immediate convenience is being able to repeat the installation process across connected sites without visiting every WordPress dashboard.
Use Read Mode as a Guardrail
Novamira’s read mode lets an AI agent inspect site information while limiting write operations.
The examples we discussed included reading PHP versions, plugin versions, WordPress versions, and sales information. Tasks such as changing a site’s design, adding posts, or creating products require write operations instead.
Our preference in the walkthrough was to leave read mode on until we needed to make changes. We enabled it from HQ, then refreshed the WordPress dashboard to confirm that the site’s status had changed to read mode.
Read mode is a guardrail, not a security boundary. Explicit prompting can bypass its intended limits, so it shouldn’t be treated as a security tool or a guarantee that changes are impossible.
It still adds a useful control to routine AI work. Later in our migration test, read mode on the source site prevented the agent from deleting the original post.
That distinction matters: the setting affected an actual operation in the demonstration, but it doesn’t replace other controls over what an agent can access or do.
Run Hosting Tasks From the Site Menu
The three-dot menu includes actions such as renaming or disconnecting a site. It also provides hosting tools and backup controls, with the available options depending on the connected host.
Because we connected Kinsta, the walkthrough showed the tools available through that integration.
Submit a Cache-Clearing Request
We explored the cache-clearing action and its report. HQ can send the request to the host, while the report lets you inspect the status and details.
The interface also provides a request you can copy into the AI chat if you want to work through it there and see what’s happening.
These controls provide you a starting point for host-related operations without having to compose the request yourself each time.
Create and Restore Host Backups
Next, we selected Create Backup from the site menu.
When we switched to MyKinsta, its dashboard showed the backup operation running. That confirmed HQ was communicating with the hosting account to start the backup.
HQ also includes Restore From Backup. Through the host connection, it can access the backups available in MyKinsta and provide the restoration action.
We demonstrated starting a backup, not completing a restore. The available backup controls here belong to the connected hosting workflow.
Choose How Cursor Handles a Migration Request
For the AI test, we moved into Cursor’s agent mode. This mode can perform actions, so a request can lead directly to changes on a connected site.
Cursor also offers plan mode for working through a proposed approach and ask mode for asking questions. We discussed those options because they affect how you begin a task and how quickly the agent may act.
Our migration request included an instruction to ask questions before proceeding. That gave the agent room to clarify the destination, publishing choices, and treatment of the original post.
Even in agent mode, this particular test didn’t immediately execute every requested action. The agent first returned questions and then a plan for us to review.
The distinction is important when following the walkthrough: agent mode makes action possible, but the agent may still request clarification or approval along the way.
Plan a Post Migration Between Connected Sites
The test used one post on Novamira HQ 2 and an empty destination site. It was a smaller version of a task we’d already used HQ for: moving posts in a particular category to another site because they fit better under a different brand.
Ask the Agent to Clarify the Move
We asked the agent to migrate the post on Novamira HQ 2 to our other connected site and to ask any questions needed to make the move successful.
The agent could see both live and staging environments, so its first questions included where the post should land.
It also asked about the destination post’s status, its URL slug, what should happen to the source post, and which details to copy.
These are separate decisions. A request to “move a post” doesn’t, by itself, explain whether the destination should be a draft or whether the original should remain published.
We also discussed redirects and permalink structure as considerations that can arise during this kind of move.
Set the Destination and Content Choices
For this test, we selected the live destination and chose to publish the copied post. We kept the existing slug and asked the agent to copy everything.
The source post contained a Gutenberg paragraph, used the Uncategorized category, and had no tags. Those were the details the agent identified during its questions.
We also requested deletion of the original after a successful copy. However, that deletion did not complete during the walkthrough.
Check the Migration Result and Source Deletion
After answering the questions, we reviewed the agent’s plan and told it to proceed.
The post appeared on the destination site after we refreshed its Posts screen. It was published and included the content and details involved in the test.
The source deletion required more attention. The agent checked back with us, and we explicitly told it to delete the original.
We then found the reason it couldn’t finish that part of the task: the source site was still in read mode.
The destination copy had succeeded, but the original remained because the source site’s setting prevented that write operation. We didn’t demonstrate switching off read mode and completing the deletion.
At first, we considered whether Novamira’s confirmation behavior explained the extra check-ins. The later read-mode finding gave us a concrete explanation for the blocked deletion. We didn’t run a separate comparison with Novamira bypassed, though.
Where Novamira’s WordPress Knowledge Helps
An AI agent already knows a great deal about WordPress. During the walkthrough, we discussed that some simpler tasks may be possible by working with the agent directly, without using Novamira or HQ.
Moving a basic post was our example. We suggested that an agent might handle it directly, but we didn’t test that route in this video or compare its speed.
Novamira’s WordPress capabilities become more relevant when a task needs deeper access to WordPress or support for a particular plugin.
We used a forms plugin as an example. If you need to move forms between sites and Novamira supports that plugin’s abilities, the agent can work with the plugin’s features and data rather than treating the task as a basic content copy.
That example depends on support for the plugin involved. The walkthrough didn’t claim that every forms plugin, or every WordPress tool, has an integration.
The distinction is between a general WordPress request and work that needs knowledge of the site’s particular technology stack.
Bring Agency Work Into One Workflow
The agency benefit we focused on was reducing repeated setup.
Without HQ, adding another site could mean installing Novamira, installing Pro, activating it, applying the license, and connecting that site to the AI tool. HQ brings those steps into a central workflow.
We also described how hosting operations and AI work can fit together. You can start a backup, handle another site’s task while it runs, then return to your AI agent after confirming the backup is ready.
Staging pushes, backup controls, and remote Pro installation all sit alongside the site connections. That reduces the number of separate dashboards involved in getting ready for a task.
The same benefit applies to freelancers managing several websites, not only agencies with large client lists.
HQ itself is free. Novamira Pro is separate and adds features such as memory, so the free desktop app and the Pro license are distinct parts of the setup.
Fewer Repeated Connections Across Managed Sites
Our strongest takeaway is the single HQ connection for working with multiple WordPress sites. Remote Pro installation and host-level controls make that central connection more useful than a simple site list.
For agencies and freelancers, HQ brings the setup and preparation closer to the AI work itself, without requiring a fresh connection process every time another site joins the workflow.
Frequently Asked Questions About Novamira HQ
What Is Novamira HQ?
Novamira HQ is a free desktop app for connecting multiple WordPress sites running Novamira AI to an AI agent through one central connection. It also brings supported hosting tasks and Novamira Pro setup into the same app.
How Do You Connect WordPress Sites to Novamira HQ?
You can connect a supported hosting account so HQ can find its sites or add sites manually. In the walkthrough, connecting a Kinsta account required creating an API key, entering it in HQ, and authorizing the sites.
Does Novamira HQ Include Novamira Pro?
No. HQ is free, while Novamira Pro is a separate product. If you have a Pro license, you can save it in HQ and use the app to install and activate Pro on connected sites.
Can Novamira HQ Move Posts Between WordPress Sites?
The walkthrough tested copying a post between two connected sites. The destination copy succeeded, but the agent couldn’t delete the original because the source site was in read mode.
Can Novamira HQ Manage Backups and Staging?
HQ can start supported hosting tasks, including backup requests and pushes between staging and live environments. Available actions depend on the connected hosting provider, and the walkthrough explored the push setup and started a backup without demonstrating a completed deployment or restore.