r/openclaw • u/weedwacker1975 • 56m ago
Discussion OpenClaw + Codex: Persistent failures, incomplete tool calls, and timeouts. Is anyone actually running this reliably?
Title: OpenClaw + Codex: Persistent failures, incomplete tool calls, and timeouts. Is anyone actually running this reliably?
I’m looking for advice from experienced OpenClaw users and developers because I’ve been struggling with Codex reliability for a long time.
I’m relatively new to this technology, but I’ve invested considerable time in building an OpenClaw-based personal AI assistant called Hal. My goal is to create a dependable digital chief of staff that manages commitments, follows up on tasks, monitors systems, handles research, and helps coordinate daily work.
The potential is extraordinary. Unfortunately, the actual experience has been frustratingly inconsistent.
My setup:
Two Apple Mac minis, primary and secondary, connected through Tailscale.
OpenClaw 2026.11.3.
Official Codex plugin 2026.11.3.
GPT-5.6 Terra as the default model.
Claude Sonnet 4.6 through OpenRouter as fallback.
Local Ollama models available, although performance has been disappointing.
Telegram, Google services, local monitoring, and a custom Mission Control dashboard.
The recurring problem: Codex repeatedly fails to finish tasks.
The system often starts working, invokes tools, sometimes even writes useful files or updates records, and then fails before completing the response.
Some of the recurring errors include:
OpenClaw recorded a native Codex tool.call without a matching tool.result before the turn completed.
codex app-server execution budget timed out
CODEX_APP_SERVER_LOCAL_REQUEST_CANCELLED
We’ve also encountered:
Explicit auth order for openai has no usable profiles.
Interestingly, the gateway can report valid OpenAI OAuth credentials while isolated execution encounters authentication failures.
What makes this particularly frustrating is that the underlying system often works.
The gateway is running, both Mac minis are connected, backups are verified at the application-data level, and Google authentication checks have passed.
We’ve successfully moved some recurring tasks to deterministic local Python scripts. Those run quickly and reliably.
But as soon as we introduce more sophisticated AI-driven execution through Codex, reliability deteriorates.
One failed routine commitment-review task recorded approximately 380,000 total tokens, including cached tokens, before failing.
What we’ve already tried:
Reducing agent context.
Restricting tool permissions.
Separating local monitoring from AI-driven tasks.
Reducing the frequency of complex automations.
Verifying OAuth credentials and gateway connectivity.
Inspecting logs and plugin compatibility.
Testing isolated and gateway-based execution.
Preserving backups and avoiding unnecessary upgrades.
The failures persist.
My questions for the community:
Is anyone running OpenClaw with Codex reliably for sustained, autonomous task execution?
Has anyone encountered the missing tool.result error, and what actually fixed it?
Could this be a Codex app-server integration or session-management problem rather than a model problem?
Is there a more dependable way to use OpenAI models with OpenClaw without relying on this problematic execution path?
For a two-Mac setup, would you recommend local-first execution with cloud AI reserved for reasoning?
Are there known compatibility issues with the current Codex plugin or its authentication handling?
Why I think this matters beyond my particular setup:
For those of us who aren’t developers, AI agents promise to make sophisticated technology accessible without requiring us to become systems engineers.
But an assistant that works brilliantly one moment and fails silently the next is extremely difficult to trust.
I don’t expect perfection. I do expect tasks to either finish successfully or fail clearly, preserve their progress, and recover without constant human intervention.
Right now, I spend too much time maintaining the assistant instead of benefiting from it.
I’m not looking to criticize the developers. I appreciate the ambition and complexity of what they’re building.
I’m genuinely interested in understanding whether others have achieved a stable setup, what architecture they use, and whether there’s a known solution to these persistent Codex problems.
I’d especially appreciate practical, beginner-friendly advice based on configurations that are actually working—not just theoretical fixes.
Thanks in advance.