Documentation
Forge Pro
Settings

Settings

Go to Settings → Windcodex Forge Pro. There are five tabs.

TabPurpose
ConnectionConnector URL, OAuth discovery, connected apps, static client
ToolsTurn tool groups on or off; enable the live-site override
GeneralConnector status, safety acknowledgements, limits, data cleanup
ActivityTool-call log, sandbox draft browser with diff viewer, snapshots
LicenseActivate a key for automatic updates

Connection

See Connecting an AI Platform.

Tools

One toggle per group with a risk badge, plus the environment status. See the Tools Reference. If the site is detected as production, the tab explains that power tools are blocked and offers the hostname-typed override. See Live-Site Block.

General

Connector

OptionDefaultDescription
Connector statusOnTurn off to immediately stop every connected AI platform from reaching the site
Read-only modeOffStrips every tool that is not marked read-only
Acting userCurrent adminUsed only for calls not tied to an OAuth user. Power tools still require an Administrator at call time
Max results per list call50Cap on rows returned by list and query tools
Requests per minute120Per-user cap (10-600). The highest-risk tools also have a separate 10 per minute cap
OAuth auto-registrationOnLet platforms register themselves

Safety

OptionDefaultDescription
I have a backup in placeOffRequired before wp_execute_php and wp_create_admin_access_link will run
Allow direct live writesOffExposes wp_write_file. Drafts remain available without it
Live-site overrideOffLets power tools run on a production-detected site, locked to the current domain. Turn it off here; turn it on from the Tools tab

Data & Privacy

OptionDefaultDescription
Delete all data on uninstallOffOn: settings, OAuth data, logs, snapshots, jobs, memories, and tables are removed on deletion. Off: everything stays for a later reinstall

Activity

The log records tool calls, including the full PHP code or command run. It also hosts the draft browser for the sandbox (with diff, promote, and discard) and the list of snapshots.

License

See License.

⚠️

The audit log stores full PHP code and commands so you can see exactly what happened. If a command contains a secret, the secret is in the log. Avoid putting credentials in commands.