openclaw.json5.example

{
  // openclaw worker kit: example config posture
  //
  // this is not a drop-in config file.
  // it shows the posture this kit recommends for a first worker.
  //
  // before using any of these keys:
  // 1. confirm the key names and structure against your installed openclaw version
  // 2. check the current openclaw docs for any changes to config format
  // 3. test in a non-production setup first
  //
  // openclaw config structure and key names change between versions.
  // the posture below is what matters. the exact syntax may need adjustment.

  // browser posture:
  // start with the managed openclaw browser profile.
  // do not attach to your real signed-in browser session by default.
  // the managed profile is isolated from your personal logins and cookies.
  browser: {
    defaultProfile: "openclaw",
    // use "user" only when the job requires your real login state
    // and you have explicitly approved it.
  },

  // approval posture:
  // enable exec approvals to reduce accidental execution.
  // this is a guardrail, not an identity boundary.
  // it does not replace trust-boundary design.
  approvals: {
    exec: {
      enabled: true,
    },
  },

  // sandbox posture for non-main sessions:
  // if you run group chats, they land in non-main sessions.
  // sandboxing non-main sessions gives them a narrower tool set
  // while your main dm lane keeps full access.
  agents: {
    defaults: {
      sandbox: {
        enabled: true,
      },
    },
  },

  // tool restrictions for sandboxed sessions:
  // start narrow. widen only after review proves the worker needs more.
  tools: {
    sandbox: {
      allow: ["messaging", "sessions"],
      deny: ["runtime", "fs", "ui", "nodes", "cron", "gateway"],
      // these category names are illustrative.
      // check your openclaw version for the current tool group names.
    },
  },
}