Feature request: per-automation sandbox/profile overrides (isolate permissions per automation)

Open 💬 4 comments Opened Apr 3, 2026 by TheAlexDev23

What variant of Codex are you using?

App (MacOS)

What feature would you like to see?

Codex automations currently use default sandbox settings and global rules, which makes it hard to grant narrow permissions to a single automation without affecting normal interactive threads.

I have one recurring automation that needs network + one specific command prefix:
node .agents/skills/openclaw-skills-reddit-search/scripts/reddit-search.ts

I want this permission only for that automation, not globally for all threads.

Today:

  • Automations inherit default sandbox settings
  • Rules/prefix allowlists are global
  • There is no documented per-automation profile binding in automation.toml

This creates a security/usability gap:

  • Over-permissive: grant global allowlist and impact normal threads
  • Over-restrictive: keep strict defaults and break the automation

Any one of these would solve it:

  1. profile = "<name>" support in automation.toml (or UI equivalent)
  2. Per-automation sandbox/network/approval settings in UI + schema
  3. Per-automation command allowlist attached to automation config

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗