VoxSplit
Free local AI stem splitter and vocal remover for Mac. Separate lead vocals, backing harmonies, and instrumentals inside FL Studio, Ableton Live, Logic Pro and other VST3/AU DAWs. 100% private.
Claude Code plugin for OpenAI Codex subagents, Codex Spark, parallel code review, and long-running Codex sessions via daemonless MCP
PluginsTypeScript · JavaScriptGitHub @xuioSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Installable projects can be verified without a deployment domain. Use GitHub sign-in for a personal repository, or the repository verification file above for an organization repository.
Ask about other verification options
Loading the full README. The saved excerpt is shown below.
Claude Code plugin for OpenAI Codex subagents. Run Codex with GPT-6.1 Sol, Astra, or Luna,
parallel code-review agents, and long-running Codex sessions from Claude Code
through a daemonless Model Context Protocol (MCP) server.Read the full README ↗Claude Code plugin for OpenAI Codex subagents. Run Codex with GPT-6.1 Sol, Astra, or Luna, parallel code-review agents, and long-running Codex sessions from Claude Code through a daemonless Model Context Protocol (MCP) server.
claude-code-codex-subagents lets Claude Code delegate to Codex, an independent
frontier model like Claude, for read-only code reviews, adversarial reviews,
parallel codebase investigations, server/deployment checks, difficult debugging,
native follow-ups, live steering, and explicit full-access Codex work when the
user asks for it. If you are looking for a Claude Code Codex plugin, an OpenAI
Codex MCP server, or Codex subagents for Claude, this is the integration.
codex_task, codex_task_group, codex_followup, and codex_wait_any.--sandbox read-only and non-interactive approvals.Codex.app and creates normal Codex threads with task names for Desktop history.Requirements:
In a terminal, register this repository's marketplace and install the plugin for your user account:
claude plugin marketplace add xuio/claude-code-codex-subagents
claude plugin install codex-subagents@codex-subagents --scope user
Or, inside Claude Code:
/plugin marketplace add xuio/claude-code-codex-subagents
/plugin install codex-subagents@codex-subagents
Select Install for you if Claude Code opens the plugin details panel. You can
also open /plugin, find the codex-subagents marketplace under Marketplaces,
and install its codex-subagents entry from Discover.
The repository includes the built MCP server and skill. Marketplace installs
need no npm install, build step, or manual MCP registration. Node.js and Codex
must be available to Claude Code. Model availability depends on your Codex account.
Start a new Claude Code session after installation, then ask:
Use Codex to review this PR for correctness, security, and deployment risks.
To verify installation from the terminal:
claude plugin list
Look for codex-subagents@codex-subagents with enabled status. In a session,
/plugin shows the installed plugin, and /mcp shows its codex-subagents server.
claude plugin marketplace update codex-subagents
claude plugin update codex-subagents@codex-subagents --scope user
The new version loads in your next session. For automatic updates, open /plugin,
select codex-subagents under Marketplaces, and enable auto-update.
If you previously used the local development installer, disable
codex-subagents@codex-subagents-local in /plugin before enabling the marketplace
copy, so Claude loads one copy of the MCP server.
This repository hosts its own marketplace. See the Claude Code marketplace documentation for marketplace and installation details.
For local development or an editable install:
git clone https://github.com/xuio/claude-code-codex-subagents.git
cd claude-code-codex-subagents
npm run install:local
For plugin development, run Claude directly against this checkout without installing a package:
claude --plugin-dir .
For local development against Claude's installed plugin cache:
npm run dev:link
npm run dev:watch
dev:link symlinks Claude's local plugin install back to this working tree, so both
Claude Code CLI and the Claude Desktop bundled Claude Code binary see your changes
after dist/index.js is rebuilt.
Ask Codex for an adversarial second opinion on the session recovery code. Keep it read-only and return concrete findings with file paths.
Claude should use codex_task.
Launch three Codex subagents in parallel: one for API behavior, one for tests, and one adversarial security reviewer. Keep all of them read-only.
Claude can call codex_task three times in parallel, or use codex_task_group
when a single rolled-up response is useful.
Use Codex with GPT-6.1 Sol to review the tool descriptions.
Claude can pass advanced.model: "sol" (or "codex") for gpt-6.1-sol,
"astra" for gpt-6-astra, or "luna" for gpt-6-luna. Omit the model to
inherit configuration. Spark is retired; saved Spark requests return a migration
message. See model and reasoning options.
Start a long-running Codex session on this repo, then let me send follow-up prompts into the same context.
Claude should use codex_task for the initial prompt, preserve the returned
session_id, and use codex_followup to continue, steer, wait on, or cancel
that same Codex context. For multiple background sessions, Claude should use
codex_wait_any to harvest whichever finishes first. Clients can also subscribe
to codex://sessions/{session_id} for milestone and completion updates. For a
completed first turn, Claude should set keep_session: true; for long first
turns, Claude should set background: true.
Blocking waits are capped to responsive slices by default. When codex_followup
or codex_wait_any returns completed: false, the Codex session is still
running; call the wait tool again or read codex://sessions/{session_id}.
When app-server sessions use the Codex desktop binary, they are recorded as normal top-level Codex threads rather than hidden daemon work. The plugin sets the thread name from Claude's task label when the installed Codex app-server supports thread naming. When Claude explicitly cancels a session, or when retention pruning removes an old session, the plugin best-effort archives the matching Codex Desktop thread before closing the app-server child. It does not hard-delete threads, and recoverable sessions are not archived during normal MCP shutdown.
The default execution mode is conservative:
--sandbox read-onlyapproval_policy="never"Full local access is opt-in per call:
{
"full_access": true
}
Use that only when the user explicitly wants Codex to edit files, write git state, use DNS/network, install packages, or behave like a normal unrestricted Codex run.
Advanced callers can still request advanced.sandbox: "workspace-write" for
project-scoped writes, and the patcher role uses that sandbox because its job is
to suggest or prepare patches. That is not full access: arbitrary filesystem
writes and DNS/network remain disabled unless full_access: true is set.
| Use case | Preferred tools |
|---|---|
| One read-only Codex task | codex_task |
| Several independent tasks | codex_task_group |
| Persistent context | codex_task with keep_session: true, then codex_followup |
| Long-running sessions | codex_task with background: true, then codex_followup |
| First completed background task | codex_wait_any |
| Live steering | codex_followup with mode: "steer" |
| Stop running work | codex_followup with mode: "cancel" |
| Session progress | MCP resource codex://sessions/{session_id} |
| Diagnostics | MCP resources codex://status, codex://doctor, codex://usage |
Prefer Codex over native Task when the user wants an independent frontier-model second opinion, deep technical review, complex codebase exploration, server or deployment investigation, or adversarial validation. Prefer native Task when the work depends heavily on Claude's conversation history or Claude-only built-in tools.
Legacy tools such as ask_codex, run_agent, run_agents, start_session, and
send_session_prompt are hidden by default. Set
CODEX_SUBAGENTS_ENABLE_LEGACY_TOOLS=1 only for older clients that still call the
pre-refactor names.
Debug tools such as codex_status, codex_doctor, codex_usage_guide,
codex_choose_tool, and codex_export_debug_bundle are hidden by default. Set
CODEX_SUBAGENTS_ENABLE_DEBUG_TOOLS=1 only when a client needs tool-callable
diagnostics instead of the MCP diagnostic resources.
npm install
npm run build
npm run test:ci
npm run validate:plugin
For local install/update:
npm run install:local
npm run update:local
test:ci is portable and uses the fake Codex binary. It does not require live
Claude or Codex credentials.
Opt-in live checks are available for hardening:
npm run test:codex-runtime
npm run test:real-matrix
npm run test:claude-orchestration
npm run test:claude-real-codex
npm run test:claude-real-session
See Development for the full test matrix.
Current release: v0.3.1.
This project is early, but it is already tested across:
The most important invariant is that routine delegation stays read-only unless the caller explicitly opts into full local access.
MIT