@getwebkoding "Nobody noticed" is the real finding. wp core version only covers servers you remember to check, and this bug hit during the upgrade itself, so sites that updated late are worth a look for odd PHP files.
Disclosure, I work on Protuno: our free audit checks any site by domain.
@adamjfpickering@apeatling Makes sense: an agent picks what it can finish in one session. Static HTML is done once the file is written. WordPress is hosting first, then updates for as long as the site lives. Did any of the agents mention who would keep the site updated afterwards?
@Xjohannesh 15-20+, each one a test environment for a specific feature.
CLAUDE.md doesn't learn from the conversation, it only knows what I wrote at the start. Features and rules keep changing, so I'm stuck updating them by hand. Anyone solved self-updating context per site?
WordPress MCPs are everywhere now. But what's next?
10 sites in Claude Code: it mixes them up, a new chat forgets each site's context, and one long chat just burns tokens.
How are you managing multiple sites with agents?
@nicos_ai Same APIs for people and agents works if access can tell them apart. An agent acting for a user usually needs less than that user has, and the log has to say "agent, for Priya", not just "Priya", or every agent mistake looks human. How does https://t.co/iyHVjjcec3 scope that?
@bibryam That's the split I was hoping for: the gateway enforces "read this table, never write it" at the tool call, so swapping ADK for Codex doesn't quietly change what the agent can touch. Can agentgateway policies see the call's arguments, or only which tool is being called?
@BasiraPress_ The dormant archive site is the classic weak spot on a shared account: same server, nobody updating it. If it only needs to stay readable, static HTML takes it off the table.
Disclosure, I work on Protuno: our free audit checks a site from just its domain.
@testerlabor One more pass worth doing after a cleanup like this: where a backdoor comes back from. The mu-plugins folder (it loads without showing in the plugin list), WP-Cron events, admins added straight to the database, and the wp-config salts, since rotating them ends stolen sessions.
@bradvin One setting worth pinning on whichever one the agent uses: the PHP version, matched to the oldest host the plugin claims to support. A lot of "works in test, white screen in prod" is a plugin tested on 8.3 and shipped to a site on 7.4. Does your agent test across versions?
@gauri__gupta@neosigma_ai Tuning the harness at runtime from production traffic is the part I'd watch. The harness is also where the guardrails live, so if the reward is task success, the cheapest win it can find is loosening a check. Do you keep the permission layer outside what gets tuned?
@SecurityWeek Updating to 3.1.8.10 closes it but doesn't remove anything already planted. Attempts started 7 Oct, so check /wp-content/uploads/bricksforge/tmp/ for PHP files (login_admin_*.php showed up). It hits any site with Pro Forms active, even forms with no upload field.
Your client's site broke last week. You found out from them.
The full guide for WordPress agencies on how to catch it first, with a 2-min intro video inside. @Protunohq https://t.co/yK6Q3VKJE0