Agent ControlSafer WordPress access for AI
English
Buy a license
Menu

A simple setup path

Decide what the assistant needs before you connect it.

Start with one specific job. Create a separate WordPress profile, choose the most limited access level that can complete the work, and keep the connection password outside this website.

Plan your first profile
From one job to a finished accessPlan these steps before connecting
  1. 01Name the jobBe clear about the result you need
  2. 02Create a separate accountDo not reuse a human administrator
  3. 03Choose an access levelUse the most limited level that fits
  4. 04Connect the assistantKeep credentials outside this website
  5. 05Check the work and end accessRemove access when the job is complete

From start to finish

Set up the access, check the work, then close the door.

A separate assistant identity moving through setup, access, review, and completion while a person remains in control.Conceptual illustration · not product UI
A simple illustration of the access lifecycle. It is not a screenshot of the plugin.

See the real setup screen

Agent Control starts by asking what you want to connect.

Real 0.9.0 interface · safe demonstration data

Agent Control guided setup asking whether Claude Code, Codex, or another REST assistant will connect. Real 0.9.0 interface · sanitized demo data
The real first step in Agent Control 0.9.0. The listed tools are setup choices, not a promise that every version or connection method is supported.

Interface evidence only: this capture attests what the distributed 0.9.0 interface displays, not that every displayed capability or behavior is assured.

A workstation with two generic command-line windows and a separate WordPress identity card.Conceptual illustration · not product UI
A generic assistant-workstation scene, not a real Codex, Claude Code, or Agent Control screen.

Your AI tool is only one part of the setup

Codex or Claude Code may connect, but WordPress still needs its own access decision.

These are examples of tools a WordPress owner may evaluate. The exact connection method and supported versions must be checked separately. Agent Control focuses on the WordPress side: which account the assistant uses, what kind of work it is for, and when the access should end.

Examples only. This page does not promise MCP or universal client compatibility.

Keep setup understandable

Make the important decisions before dealing with technical details.

You should be able to explain which account is used, what the assistant is expected to do, and when access will end before choosing a protocol or handling credentials.

Exact connection steps, logged fields, refused actions, and recovery states will be published only after they are tested against the distributed version.