Bug type
Regression (worked before, now fails)
Summary
Summary
In a sandboxed Telegram session, OpenClaw file-tool writes failed with:
moltbot-sandbox-fs: 2: python3: not found
Earlier in the same session, direct shell writes to /workspace also failed with:
cannot create STYLE.md: Read-only file system
Current upstream docs/repo indicate the default sandbox image should already contain python3, so this looks like a sandbox FS bridge / image / stale-container problem, possibly with a separate workspace mount issue.
Environment
• OpenClaw version: 2026.3.13
• Session type: main Telegram direct session
• Runtime: Docker sandbox
• Model: openai/gpt-5.4
• Expected sandbox image: openclaw-sandbox:bookworm-slim
• Host: macOS gateway host, agent running in Docker sandbox
Observed errors
- File tool write failed with:
moltbot-sandbox-fs: 2: python3: not found
- Direct shell write to workspace failed earlier with:
cannot create STYLE.md: Read-only file system
Why this looks like a bug
Current upstream Dockerfile.sandbox appears to install:
• bash
• ca-certificates
• curl
• git
• jq
• python3
• ripgrep
So python3: not found suggests one of:
• stale or misbuilt sandbox image
• stale sandbox container not recreated after image update
• sandbox FS bridge invoking assumptions that do not hold in the running image
• another regression in sandbox FS bridge setup
Steps to reproduce
Steps to reproduce
- Run OpenClaw with sandbox enabled for the active session
- Ensure file tools are available
- Ask the agent to create a simple file in the workspace, e.g. STYLE.md
- Observe failure from the file-tool bridge:
moltbot-sandbox-fs: 2: python3: not found
Expected behavior
- write should succeed
- the sandbox FS bridge should be able to invoke python3 if using the current default sandbox image
- /workspace should be writable when sandbox config allows it
Actual behavior
• file-tool bridge fails before write completes
• in the same environment, /workspace also appeared read-only during shell write attempts
OpenClaw version
2026.3.13 (61d171a)
Operating system
macOS (Apple Silicon, Mac Mini M4 Pro)
Install method
Homebrew (brew install openclaw), running as LaunchAgent
Model
openai/gpt-5.4
Provider / routing chain
OpenAI API (direct, no proxy)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Bug type
Regression (worked before, now fails)
Summary
Summary
In a sandboxed Telegram session, OpenClaw file-tool writes failed with:
moltbot-sandbox-fs: 2: python3: not found
Earlier in the same session, direct shell writes to /workspace also failed with:
cannot create STYLE.md: Read-only file system
Current upstream docs/repo indicate the default sandbox image should already contain python3, so this looks like a sandbox FS bridge / image / stale-container problem, possibly with a separate workspace mount issue.
Environment
• OpenClaw version: 2026.3.13
• Session type: main Telegram direct session
• Runtime: Docker sandbox
• Model: openai/gpt-5.4
• Expected sandbox image: openclaw-sandbox:bookworm-slim
• Host: macOS gateway host, agent running in Docker sandbox
Observed errors
moltbot-sandbox-fs: 2: python3: not found
cannot create STYLE.md: Read-only file system
Why this looks like a bug
Current upstream Dockerfile.sandbox appears to install:
• bash
• ca-certificates
• curl
• git
• jq
• python3
• ripgrep
So python3: not found suggests one of:
• stale or misbuilt sandbox image
• stale sandbox container not recreated after image update
• sandbox FS bridge invoking assumptions that do not hold in the running image
• another regression in sandbox FS bridge setup
Steps to reproduce
Steps to reproduce
moltbot-sandbox-fs: 2: python3: not found
Expected behavior
Actual behavior
• file-tool bridge fails before write completes
• in the same environment, /workspace also appeared read-only during shell write attempts
OpenClaw version
2026.3.13 (61d171a)
Operating system
macOS (Apple Silicon, Mac Mini M4 Pro)
Install method
Homebrew (brew install openclaw), running as LaunchAgent
Model
openai/gpt-5.4
Provider / routing chain
OpenAI API (direct, no proxy)
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response