VeryGoodOpenSource / VeryGoodOpenSource/vgv-ai-flutter-plugin

feat: add support for Codex

Open
#46 2 comments 7 reactions 1 assignee View on GitHub

@ryzizub is already working on this.

Since Jul 21, 2026.

feature p1
Dominant language
Shell
Stars
162
Forks
23
Avg merge
2d 22h
Merged PRs (30d)
4

Description

Description

Codex is a popular agentic platform (https://chatgpt.com/codex). Tier-2 target under epic #51 — bring VGV best practices to more platforms and users.

Codex is a "universal" agent: it reads .agents/skills/ directly, so once the repo is published to the open standard (#50), skills land in Codex for free. The remaining work is MCP and hooks.

Scope

  • Skills — verified to load from .agents/skills/ and to degrade where a referenced MCP tool is absent (Phase 0).
  • MCP — wire dart and very-good-cli servers via Codex ~/.codex/config.toml.
  • Hooks — port the enforcement layer (auto analyze/format, CLI gating) to Codex hooks. Codex loads hooks from hooks.json or inline [hooks] in config.toml, with PreToolUse / PostToolUse / UserPromptSubmit events. Caveats: experimental, feature-flagged ([features] codex_hooks = true), disabled by default, not available on Windows. Adapt ${CLAUDE_PLUGIN_ROOT}-style path vars as needed.
  • Subagent — Codex has full subagent support (GA March 2026, custom agents as TOML in ~/.codex/agents/). Convert the flutter-reviewer agent to Codex TOML so it dispatches natively.
  • CI — loader job that installs the skills and asserts they load in Codex.

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

Requirements
  • Skills load in Codex via .agents/skills/
  • dart + very-good-cli MCP wired via config.toml
  • Enforcement hooks ported to Codex hook format (with Windows / feature-flag caveats documented)
  • Codex loader CI job added
  • All CI/CD checks are passing.
  • There is no drop in the test coverage percentage.
Additional Context

Part of epic #51. Tier 2 / wave 1 alongside Gemini CLI (#125) and OpenCode (#127).

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.