#codex

1 messages · Page 1 of 1 (latest)

vale trench
#

I am using openai-codex and oauth authentication, and on gpt-5.4 model. It doesn't have access to file system or tool access for some reason. When I tell it to look at its workspace directory, it'll say this

I don’t have filesystem/SSH access from this chat session.

Is this a set up issue on my side, or this is a restriction when we use codex in openclaw?

Any help is highly appreciated!

proper currentBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

untold raftBOT
#

That message is not a Codex-OAuth restriction. Codex OAuth (openai-codex/gpt-5.4) is only how the model is authenticated. Filesystem access in OpenClaw comes from tools (read / exec / etc), and it’s totally possible to use those with Codex models.

If the model says “I don’t have filesystem/SSH access from this chat session”, it almost always means your session is running with tools disabled/restricted, e.g.:

  • tools.profile is set to minimal or messaging
  • you have a restrictive tools.allow that doesn’t include group:fs / group:runtime
  • you have a provider-specific restriction like tools.byProvider["openai-codex"].profile = "minimal"
  • you’re sandboxed (common in Discord channels) and tools.sandbox.tools.* is blocking exec/fs tools

Two quick checks:

  1. Version (first thing):
    openclaw --version

  2. Inspect effective sandbox/tool policy (this is the fastest “what’s actually happening?” command):
    openclaw sandbox explain

#

And config sanity checks:

  • openclaw config get tools
  • openclaw config get tools.byProvider

What you want for “can read workspace + run ls” is roughly: tools profile coding or full, and allowed tools include group:fs + group:runtime (and if you’re sandboxed, allow them in tools.sandbox.tools.* too).

Docs that map exactly to this:

If you paste the output of openclaw config get tools + openclaw sandbox explain, I can point to the exact key that’s blocking it.

vale trench
#

openclaw config get tools
give me

{
  "profile": "messaging"
}

can I change it to full?

untold raftBOT
#

Yes — that’s exactly what’s happening.

tools.profile: "messaging" intentionally strips out the filesystem/runtime tools, so the model can’t read/exec and will say it has no FS access.

Recommended change (gives FS + exec, without “everything”)

openclaw config set tools.profile coding

If you really want all tools

openclaw config set tools.profile full

Config reload is hot by default, so you usually don’t need a restart. If it still behaves the same after changing it, do: