mirror of
https://github.com/openai/codex.git
synced 2026-05-14 16:22:51 +00:00
d2c3ebac1f
## Why `codex-core` still owns a growing amount of product-specific behavior. This PR starts the extraction path by introducing a small, typed first-party extension seam: features can install the contribution families they actually own, while the host keeps lifecycle and state ownership instead of pushing a broad service locator into the API. See the `examples/` for illustration ## Known limitations * Tool contract definition will be shared with core * Fragments must be extracted * Missing some contributors
653 B
653 B
Everything becomes a good contributor design, which contributors do we need?
git attribution Context memories Context + Tool + Output guardian Context + Request goal Tool + Runtime image generation Tool + Output skills Context + Turn personality Context plugins / apps / connectors Context + Turn shell snapshot Runtime web search Tool AGENTS.md Context (Runtime too only if you want eager refresh/cache behavior) future sandboxing probably Request + Runtime