← Back to AI Insights
Gemini Executive Synthesis

Codex-native harness timeout when routed through OpenAI-compatible gateway (OpenRouter).

Technical Positioning
Seamless integration and compatibility with OpenAI-compatible gateway providers for `codex-native` agents.
SaaS Insight & Market Implications
This issue reveals a critical integration failure for Omnigent's `codex-native` harness when interacting with OpenAI-compatible gateway providers like OpenRouter. The inability to start a thread and subsequent timeout, despite `pi` harness functionality and direct Codex CLI operation, indicates a specific compatibility gap within the `codex-native` bridge. This directly impacts users leveraging third-party gateways for cost optimization, rate limiting, or unified API access. The misleading error message further complicates debugging. For a platform aiming to be a "meta-harness for all your AI agents," such integration failures with common proxy solutions limit its utility and increase operational friction for enterprise users dependent on flexible provider routing.
Proprietary Technical Taxonomy
codex-native worker OpenAI-compatible gateway OpenRouter kind: key wire_api: chat wait_for_thread_started bridge thread state executor turn

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Jun 14, 2026
Repo: omnigent-ai/omnigent
codex-native times out at thread start over an OpenAI-compatible gateway (OpenRouter); surfaces as 'Codex native bridge state is missing'

## Summary

When a `codex-native` worker is routed through an OpenAI-compatible **gateway** provider (here: OpenRouter, `kind: key`, `wire_api: chat`), the Codex app-server never starts a thread. `wait_for_thread_started` times out after 30s, the bridge thread state is never written, and the next executor turn fails with the misleading error **`Codex native bridge state is missing`**.

The same gateway works fine for the `pi` harness, and the Codex CLI works fine on its own ChatGPT subscription, so this is specific to `codex-native` over a gateway provider.

## Environment

- omnigent 0.1.0 (uv tool install)
- codex-cli 0.139.0 (`codex login status` → "Logged in using ChatGPT")
- Python 3.12, macOS (arm64)
- Agent: bundled `examples/polly` `codex` sub-agent (`harness: codex-native`, no explicit model)

## Reproduction

`~/.omnigent/config.yaml` providers block (secrets elided) makes a gateway the default for the `openai` family:

```yaml
providers:
codex:
cli: codex
kind: subscription # exists, but NOT a default for openai
openrouter:
kind: key
default: [openai, pi] # gateway is the openai-family default -> captures codex-native
openai:
base_url: openrouter.ai/api/v1
wire_api: chat
models: { default: moonshotai/kimi-k2.6 }
```

Dispatch any `codex-native` task (e.g. a polly `codex` sub-agent). It is routed to the gateway because `default_provider_for_harness("codex-native")` resolves the `openai` family, whose o...

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from omnigent-ai/omnigent.

Extracted Positioning
Native Windows support for Omnigent, specifically addressing POSIX assumptions.
Cross-platform compatibility, including native Windows, or clear documentation for WSL2 as the intended Windows environment.
Extracted Positioning
Feature request for OpenCode harness support.
Expand supported AI agent harnesses.
Extracted Positioning
Feature request for Google Antigravity harness integration in `omni setup`.
Broaden agent ecosystem support and simplify initial setup for new users.
Extracted Positioning
Pi sub-agent workspace isolation failure within Omnigent.
Consistent session workspace management across all integrated AI agent harnesses (Claude Code, Codex, Pi).

Frequently Asked Questions

Market intelligence mapped to Codex-native harness timeout when routed through OpenAI-compatible gateway (OpenRouter)..

How is Codex-native harness timeout when routed through OpenAI-compatible gateway (OpenRouter). positioned in the market?
Based on our AI analysis of the original developer request, its primary technical positioning is: Seamless integration and compatibility with OpenAI-compatible gateway providers for `codex-native` agents.
What are the foundational technologies related to Codex-native harness timeout when routed through OpenAI-compatible gateway (OpenRouter).?
Our proprietary extraction maps Codex-native harness timeout when routed through OpenAI-compatible gateway (OpenRouter). to adjacent architectural concepts including codex-native worker, OpenAI-compatible gateway, OpenRouter, kind: key.

Engagement Signals

0
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like codex-native worker and OpenAI-compatible gateway by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.