VeryGoodOpenSource / VeryGoodOpenSource/vgv-wingspan

feat: add support for Codex

Open
#226 0 comments 1 reaction 1 assignee View on GitHub

@ryzizub is already working on this.

Since Jul 21, 2026.

feature p1
Dominant language
Shell
Stars
105
Forks
15
Avg merge
13h 12m
Merged PRs (30d)
2

Description

Description

Codex (https://chatgpt.com/codex). Tier-2 target under epic #66 alongside Gemini CLI.

Codex is a "universal" agent: it reads .agents/skills/ directly, so once the repo is published to the open standard (skills.sh), the workflow skills land in Codex for free. Remaining work is the hook and MCP, plus the subagent-degradation decision.

Scope

  • Skills — verified to load from .agents/skills/.
  • Hook — port recommend-plugins to Codex hooks (hooks.json or inline [hooks] in config.toml; PreToolUse / UserPromptSubmit events). Caveats: experimental, feature-flagged ([features] codex_hooks = true), not on Windows. The host-aware version of recommend-plugins.sh from PR #220 already detects non-Claude hosts and is a starting point.
  • MCP — wire context7 via Codex ~/.codex/config.toml.
  • Subagents — Codex has full subagent support (GA March 2026): custom agents as TOML in ~/.codex/agents/, spawn_agent / wait_agent primitives, /agent. Convert our agents/*.md definitions to Codex TOML so the review/plan/research panels run natively.
  • CI — loader job asserting skills load in Codex.

Docs: https://developers.openai.com/codex/hooks

Requirements
  • Skills load in Codex via .agents/skills/
  • recommend-plugins hook ported to Codex hook format (caveats documented)
  • context7 MCP wired via config.toml
  • Agent definitions converted to Codex TOML (~/.codex/agents/); review/plan panels run natively
  • Codex loader CI job added
Additional Context

Part of epic #66. Tier 2 / wave 1 alongside Gemini CLI (#227) and OpenCode (#229).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.