Edit Agent Configuration, plugins, and workspace files

These are the Configuration, Plugins, and Workspace files tabs of the Agent detail page. Configuration and plugin changes apply only after Deploy new version; a workspace file save applies at once.

Configuration tab

In the draft, Enable gateway password access stages the generated-password reference; authentication mode and proxy settings stay unchanged. The Compute Driver owns the password; the Console shows only its reference. If the saved reference is one OpenClaw cannot read, such as one without a provider, the page shows the refusal and Deploy new version stays disabled; use the button to replace it. If secrets.defaults holds an alias OpenClaw refuses, the page names that setting instead and hides the button: fix the alias in the editor first. If OpenClaw cannot read the generated reference on the default env alias, for example because that provider's allowlist omits OPENCLAW_GATEWAY_PASSWORD, the page states why and hides the button until you fix it.

Collaboration and safety shows two Gateway settings as a deployment of the draft applies them, and whether each value is the default or set in the Configuration:

• Other participants can steer a running turn (messages.queue.allowCollaborativeSteering, default on): another Gateway participant in the conversation can add guidance to a running turn. The turn keeps the identity and permissions of the participant who started it, even when the participant steering has fewer. Participants are channel users or local operators with distinct Gateway identities. OCE native admin and workspace access share one Gateway identity, so this setting does not separate OCE users. When steering is off, the Gateway queues their message as a separate turn by default. If you set messages.queue.collaborativeSteeringFallback to "reject", the Gateway asks the participant to resend the message with /followup.
• apply_patch changes files only in the workspace (tools.exec.applyPatch.workspaceOnly, default on).

Strict mode turns collaborative steering off and restricts apply_patch to the workspace. Turning Strict mode off removes those two settings. Setting an individual toggle back to its default removes just that value. Changing the toggles requires Configuration update. Save the draft, then deploy a new version.

Edit Configuration edits native JSON. Save Configuration requires an object; Cancel discards edits. Edit current Configuration opens the current draft's editor, not a historical copy. Without Configuration update, or Secret operate on a Secret the Configuration binds, it reads Open draft and opens the draft read-only. Saving preserves Secret bindings and saved versions; Deploy new version applies saved values, including for Agents sharing this Configuration on their next deployment.

If a number such as 1e400 exceeds JavaScript's finite range, the Console stops the save, keeps your draft, and shows the error under Configuration JSON. Replace the value with a number closer to zero, then select Save Configuration again.

If a draft contains security.preset, remove that field in Edit Configuration. If you used corporate, set the restrictions you relied on explicitly before saving. For example, set tools.fs.workspaceOnly to true to confine file tools to the workspace. When a channel is enabled, OCE already separates direct-message sessions by default (session.dmScope). Strict mode leaves those settings alone. Also review any restrictions you relied on for command approvals, elevated execution, session visibility, and messaging between Agents or conversations. OCE isolates each Agent and requires OpenClaw's own sandbox to stay off. See the former preset values and OCE's deployment defaults.

Unsaved edits, pending saves, and stale or unknown outcomes block deployment, tab switching, and version navigation. Save checks Configuration association and generation, and the API refuses later races. Reload stale drafts; after an unknown outcome, successfully reload saved state before retrying. Invalid JSON and failed saves retain text for correction. A save conflict keeps focus and text selection if you moved to another control while saving. If you stayed on Checking Configuration…, focus moves to Reload draft. Backend, execution mode, and Harness authentication are Agent fields, not native Configuration JSON. See the Configuration reference.

Plugins tab

In Open draft → Plugins, edit the Agent's existing selections and tool policies with Configure plugins or Plugin selections JSON. With a bound Service Accounts token Secret, the tab preloads the first catalog page for the picker. Search and tool lookups show loading indicators. Dedicated Codex browsing requires exact active Agent read/update and a catalog-capable Plugin Driver. The curated catalog needs no Secret. Hosted discovery uses the bound Service Accounts token Secret server-side and requires caller and Agent ServicePrincipal Secret operate; the browser never receives the token. Other execution modes cannot browse this catalog. Hosted results use the draft credential, which may differ from the running version's; neither catalog proves installation or runtime access. Existing selections and Plugin selections JSON remain editable when browsing is unavailable.

If Plugin selections JSON contains a number too large in magnitude to save, such as 1e400, the Console keeps the draft and asks you to correct it before saving or editing it in the picker. You can still browse the catalog if it is available. The Plugin Driver still validates its own policy fields when you save.

An open Slack approver search keeps its query and results when you return to the browser tab and still have Agent access. Moving to another Console control closes the results; focus the search field to open them again. Switching Agent tabs and returning keeps a completed query.

Select Save plugin selections to update the Agent's desired plugin map, then Deploy new version to apply it. Saving does not alter a saved version or the reusable Configuration. An empty map removes all Agent-owned plugin selections on the next deployment. The selected Plugin Driver validates policy at save and deployment; installation and app access are checked later during startup. A rejected save leaves the running version unchanged. For policy limits and errors, see Agent plugins. Without Agent update, the selections and default plugin approvers show as a read-only summary with no editor, and a note names the grant to ask for. Every Agent save also needs operate on each Secret and credential source that the Agent and its Configuration bind, and read on a ChatGPT service account it uses for authentication; without them, the selections show as that summary too, and a note says so.

If you see Plugin selections changed, the Console stopped before saving. If you see Outcome unknown, your changes may already be saved. Note any edits you want to keep, then select Reload plugin selections. Reload reads the Agent without repeating the save. A failed reload cannot resolve an unknown save outcome.

When you see Plugin selections reloaded, the saved selections and approvers have replaced your draft. If they match what you intended, continue to Deploy new version. Otherwise, edit the reloaded settings and save only the changes you still need.

When viewing a saved version, the Plugins tab shows that version's saved selection. Return to Open draft to make another edit. Native values.plugins in Edit Configuration controls the runtime's native plugin allowlist and is separate from these Agent-owned selections.

Workspace files tab

Workspace access is unavailable leaves the editor and Save disabled. The empty box does not mean the file is empty. Check gateway access, then use Reload.

These are live files belonging to the Agent, even when you browse an older version. They are not historical copies or Configuration fields.

Choose a file with its desktop tab or the phone Workspace file dropdown. The description explains its role. Switching files keeps unsaved text and each file's indicator shows Unsaved, Loading, Missing, Read-only, or Needs attention. Each editor loads independently. Its status reports loading, success, or failure. Reload replaces unsaved edits with current contents. Save immediately creates or replaces that one file; it does not deploy a version. Save is disabled until appropriate loaded, changed state is available.

Each file allows up to 16 KiB of valid UTF-8 text. Concurrent saves use the last writer's contents. Reading requires Agent read, saving requires operate, and access needs a selected version with a reachable gateway. Without operate, the files are read-only and a note above them names the grant. An uncertain save requires Reload to confirm contents or file absence before another save. A confirmed missing file opens an empty editor; read failures leave Save disabled. See Workspace Files.