A2A wrapper service for codex
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"codex-a2a-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# codex-a2a-server > Turn Codex into a stateful, production-oriented A2A agent service. `codex-a2a-server` exposes Codex through standard A2A interfaces and adds the operational pieces that raw agent runtimes usually do not provide by default: authentication, session continuity, streaming contracts, interrupt handling, and documentation for running it as a service. ## Why This Project Exists Most coding agents are built first as interactive tools, not as reusable service endpoints. This project turns Codex into an agent service that can be embedded into applications, gateways, and orchestration systems without forcing each consumer to re-implement transport bridging, auth, or runtime operations. In practice, `codex-a2a-server` acts as: - a protocol bridge from A2A to Codex - a security boundary around the Codex runtime - a stable contract layer for session, streaming, and interrupt behaviors ## Vision Build a reusable adapter layer that lets coding agents behave like service infrastructure rather than local-only tools: - standard transport contracts instead of provider-specific glue - explicit runtime boundaries instead of ad-hoc shell wrappers - production-friendly runtime behavior and observability instead of demo-only setups ## What It Already Provides - A2A HTTP+JSON and JSON-RPC entrypoints for Codex - SSE streaming with normalized `text`, `reasoning`, and `tool_call` blocks - session continuation and session query extensions - interrupt lifecycle mapping and callback validation - bearer-token auth, payload logging controls, and secret-handling guardrails - released-CLI startup and source-based runtime paths ## Logical Components ```mermaid flowchart TD A["A2A client"] --> B["FastAPI transport layer"] B --> C["A2A task/message mapping"] C --> D["Codex client adapter"] D --> E["Codex app-server / CLI"] B --> F["Auth and request logging"] C --> G["Shared contract normalization"] G --> H["Streaming blocks"] G --> I["S…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.