Skip to main content
Every answer here comes from a real support case. If yours is not covered, report it from the Support panel in the Command Center: it attaches diagnostics and a screen recording to the ticket, which is the fastest route to a fix.

​
Chat and responses

​
The chat timed out or stopped responding. Is my work lost?

Usually not. On heavy jobs (a full page build, copying a page, a large restyle) the agent often keeps working on the site even after the chat view reports a timeout. Before re-running the request, check the page or the Tasks panel first: re-running a job that actually finished does the work twice and meters twice. If the thread itself will not respond again, start a new conversation. Changes already applied to the site are saved on the site.

​
”We couldn’t resume this conversation.”

The session behind that thread expired or returned empty. Start a new conversation and continue from there. Nothing already applied to the site is affected.

​
”This conversation has reached its context limit.”

Long threads fill the model’s working context, and a thread that hits the limit cannot continue. Start a new conversation and state the goal fresh. The agent reads the current state of the site when it starts, so a new thread picks up from where the site is now, not from zero.

​
The Command Center is stuck on “Almost ready” and never replies.

Reload wp-admin and reopen the Command Center. If it still will not initialize, report it from the Support panel so the diagnostics reach the team with the ticket.

​
Credits

​
I was charged credits but the request failed.

Credits meter the agent’s work while it runs, so a run that errors out or times out still shows usage. If a run failed through no fault of the request, report it from the Support panel with that conversation open so the team can review the run itself. For big jobs, smaller scoped requests (one page, one section) fail less and cost less per attempt than one broad instruction.

​
Connecting sites

​
Writes to the REST API return 403, but reads work.

A firewall or bot protection layer (often Cloudflare or a security plugin) is challenging POST and PUT requests to /wp-json/ while letting GET requests through. Allowlist WPOS traffic in that layer, or exempt authenticated REST API writes from the challenge. If you need the current addresses to allowlist, ask through the Support panel.

​
My license key will not validate on another site.

Licenses are locked to a site’s domain, and each connected site uses one license slot from your plan; add more from Billing. The www and http/https variants of a domain count as the same site, but a different subdomain or a second domain is its own site. If the key belongs to that site and still refuses, wait a few minutes and try again: license results are cached briefly, so a just-fixed license can take a few minutes to start validating. Still stuck? Contact support with the domain exactly as it appears in the browser.

​
Connectors

​
A connector will not connect, or the sign-in popup fails.

First make sure the plugin is current: connectors added recently do not exist in older builds, which surfaces as an “unknown connector” error. Sites update automatically within seconds of a release, so a reload is normally enough. Then retry from the Connectors panel with popup blocking off for your wp-admin domain. If it still fails, the connector’s own page lists its connect flow step by step.

​
Files

​
Reading a PDF freezes the chat.

Some large or unusually built PDFs stall the viewer. Splitting the document or attaching the relevant pages as a smaller file gets past it. If a particular PDF freezes repeatedly, attach it to a Support panel ticket so the team can reproduce it exactly.