Remote OpenClaw Blog
OpenClaw Codex Web Search Guide: What Native Codex Search Changed in 3.31
What should operators know about OpenClaw Codex Web Search Guide: What Native Codex Search Changed in 3.31?
Answer: OpenClaw 3.31 adds native Codex web search support for embedded Pi runs. The interesting part is not just that “search works.” It is that OpenClaw now knows when Codex has native search and can suppress overlapping managed search tooling instead of doubling the retrieval path. This guide covers practical setup, security, and operations steps for running OpenClaw in.
OpenClaw 3.31 adds native Codex web search for embedded Pi runs. Here is what changed, when to use it, and why managed-tool suppression matters.
Marketplace
Free skills and AI personas for OpenClaw — deploy a pre-built agent in 15 minutes.
Browse the Marketplace →Join the Community
Join 1k+ OpenClaw operators sharing deployment guides, security configs, and workflow automations.
OpenClaw 3.31 adds native Codex web search support for embedded Pi runs. The interesting part is not just that “search works.” It is that OpenClaw now knows when Codex has native search and can suppress overlapping managed search tooling instead of doubling the retrieval path.
What Did OpenClaw 3.31 Actually Add for Codex?
The release note says three things clearly: native Codex web search support exists for embedded Pi runs, config and docs coverage were added, and managed-tool suppression kicks in when native Codex search is active.
That means this is not an accidental side effect. OpenClaw intentionally supports Codex-native search as part of the runtime model now.
Why Does Managed-Tool Suppression Matter?
If native Codex search is already available, layering a separate managed search path on top can create duplicate retrieval, messy tool choice, and harder-to-debug behavior. Suppression matters because it keeps the search surface clean.
The result is a simpler loop: Codex handles the search path it already knows how to use, and OpenClaw does not interfere unless you explicitly want a different search stack.
When Should You Use Native Codex Search?
Use it when you specifically want Pi/Codex to reason with its own native web search capability and you do not need another provider inserted into the middle of that loop. This is especially helpful for coding, research, and hybrid editing tasks where you want the embedded Codex runtime to stay coherent.
If your deployment needs a different search backend for privacy or control reasons, that is where something like the SearXNG provider can still matter. The right choice depends on whether you want the provider-native path or the OpenClaw-managed path.
How Should You Test It?
After enabling the relevant Pi/Codex path, run a prompt that clearly requires retrieval and confirm that the result behaves like native Codex search rather than a duplicated tool chain. Then compare it against a managed search configuration so you understand which path is active.
The goal is not only to get a good answer. The goal is to confirm that the runtime is using the search surface you intended.
What This Feature Does Not Mean
It does not mean every OpenClaw search workflow is now “Codex search.” It also does not mean you should never use another search provider. It means embedded Pi runs can now use Codex-native search more cleanly, and OpenClaw is better at staying out of the way when that path is active.