Settings

The Agent section of AI’s Settings decides which user roles may use the Agent. Its Agent access card lists every role on the site, including roles added by plugins, each with a switch; turn on the roles that may use the Agent and save. The address of the Agent page of earlier releases, #/ai/agent, opens the same section.

By default only administrators may use the Agent; on a multisite network, super admins always may. On a single site, the Administrator row applies to administrators like any other row. A user with several roles may use the Agent when any of their roles may.

For a role that is off, the shortcut does nothing for that user and the Agent does not open.

What other roles can do

A role that may use the Agent loads the models, keeps its own conversations and lists and runs WordPress abilities. Each ability still checks the user’s own WordPress capabilities, so an editor’s Agent can do only what the editor could. Chatbots, settings, API keys and custom models stay with administrators.

From the command line

wp sleek ai agent caps list shows every role’s Agent capabilities, and wp sleek ai agent caps set changes one:

wp sleek ai agent caps set editor --cap=useAgent=1

Besides useAgent, each role stores createModes, shareModes, manageAllModes and usePluginMode. The Agent itself uses only useAgent; the next three apply to stored custom modes, which the Agent does not offer in this release (see Modes), and usePluginMode is kept from earlier versions and has no effect. The CLI reference lists the options.