Integration proposal: Codex CLI plugin bundle with lifecycle hooks (auto-drafted 2026-06-29)

[NativeTeachingAidsB]

Score: 12 — Codex v0.117.0 plugin system enables one-command install + SubagentStart/Stop hooks. Labels to add manually: integration-proposal, auto-generated, urgent.

Auto-generated by the weekly-landscape-scan routine. Draft spec in docs/superpowers/specs/2026-06-29-integrate-codex-plugin.md (on branch docs/landscape-report-2026-06-29). Do not promote to approved without human review.

What changed

Codex CLI v0.117.0 (March 26, 2026) elevated plugins to first-class primitives. A plugin plugin.yaml bundles: MCP server config + skills + hooks + app integrations. 10 lifecycle hook events: PreToolUse, PostToolUse, SessionStart, SubagentStart, SubagentStop, UserPromptSubmit, Stop, PermissionRequest, PreCompact, PostCompact.

docs/integrations/codex-cli.md only covers the legacy ~/.codex/config.toml path.

What this spec proposes

1. Author a plugin.yaml for codetalker bundling: MCP config + SessionStart, SubagentStart, SubagentStop, Stop hooks.
2. Submit to Codex marketplace.
3. Update codex-cli.md with codex plugin add codetalker instructions.

Hook-driven narration (the big win)

hooks:
  - event: SubagentStart
    tool: tts_speak
    args: { text: "Subagent starting: {{subagent.label}}" }
  - event: SubagentStop
    tool: tts_speak
    args: { text: "Subagent done: {{subagent.label}}" }

Auto-narrates subagent lifecycle without users having to prompt for it.

Key open questions

• Do Codex hooks support direct MCP tool calls, or only shell commands? (May need thin wrapper.)
• Template variable syntax ({{subagent.label}}) — needs verification.
• Codex marketplace submission: self-serve or OpenAI approval?

Effort

Medium — 3–5 days (plugin manifest + hook verification + marketplace submission + docs update).

---

Routine run: 2026-06-29 | Landscape report: docs/landscape-reports/2026-06-29.md