OpenClaw on M4 Pro: Hitting Walls with Browser-Use, Computer-Use, and Codex
A developer running OpenClaw on a MacBook M4 Pro with ChatGPT 5.5 is hitting significant issues with automation browser detection, computer-use reverting to terminal, and degraded Codex outputs. The user posted a detailed breakdown of four blockers on r/openclaw, looking for config snippets and skill adjustments.
1. Automation Browser Detection
Even after installing the Browser-Use skill, the agent defaults to a basic automation browser, triggering immediate blocks on sites like X (Twitter) and Reddit. The goal is to interact with UI elements (buttons, fields) without getting flagged. The user asks if anyone has integrated a stealth browser or connected an existing Chrome/Brave profile to bypass detection.
2. Computer-Use vs. Terminal Loop
Despite having Computer-Use active, the agent almost exclusively uses the Terminal, rarely interacting with the macOS GUI. It feels sandboxed. The user asks about specific macOS permissions or environment variables to force visual interface usage instead of CLI.
3. Codex Integration & Broken Outputs
When using Codex, the agent claims to use the CLI, but the output code quality is significantly lower than when prompting Codex directly. The user wonders if the agent is piping prompts to Codex or hallucinating the integration, and asks how to ensure Codex is used as the high-level engine rather than falling back to self-written scripts.
4. Ghosting During Long Sprints
The user sets a 4-hour sprint with a schedule. The agent starts fine but then ignores mid-sprint corrections, forcing a 4-hour wait for potentially off-track results. They want a forced Interrupt/Listen loop so the agent checks for user input between sub-tasks.
Specs & Context
- OS: macOS (M4 Pro chip)
- Model: ChatGPT 5.5
- Tool: OpenClaw (Latest)
If you have config snippets, environment variable tweaks, or skill adjustments that worked for similar scenarios, the user is looking for practical advice on r/openclaw.
📖 Read the full source: r/openclaw
👀 See Also
Reddit user shares common Claude Code prompting mistakes with fixes
A developer using Claude for Node.js backend work identified 10 common prompting mistakes after months of use, including missing validation requirements and treating Claude as one-shot tool. They created a visual guide with fixes for each issue.
Stop Claude's Em Dashes with One Line in Preferences or Claude.md
Add a specific sentence to your Claude.ai profile preferences or Claude.md to reduce em dashes by ~98%. This is a practical tweak tested by the community.
Eight Prompting Techniques That Improve Claude Output Quality
A Reddit user shares eight specific prompting techniques that consistently improved their Claude output quality, including commands like "Think through every layer before answering" and "Find the 20% of actions that drive 80% of results."
Treating Agent Runs as Review Packets: A Practical Pattern for Claude Code & Codex
A developer shares how producing a structured folder per agent run (research, drafts, evals, approval packet, metrics, memory) makes failures visible and iterations faster.