Ext Ops Panel
Open dashboard
Comparison

delegate-to-codex vs thread-keeper

delegate-to-codex is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.

delegate-to-codex is a plugin bundle for AI coding tools published by Alec Foster. No marketplace we read lists it any more. thread-keeper is an MCP server published by po4erk91. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedelegate-to-codexthread-keeper
Community marketplace alectivism/cross-model-agent-delegation Removed on 2026-10-16
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.13.1
Downloads/month (PyPI): 1 654
Downloads/week (PyPI): 45
Forks (GitHub): 4
Stars (GitHub): 13
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

delegate-to-codex vs thread-keeper
Factdelegate-to-codexno longer listed · thread-keeper
Marketplaces that list it (differs)01
Stars (GitHub) (differs)113
Forks (GitHub) (differs)04
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (threadkeeper)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)11Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/alectivism/cross-model-agent-delegationgithub.com/po4erk91/thread-keeper
Changes in the last 7 days (differs)40
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of delegate-to-codex

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Codex Delegate

    Bridge AI coding hosts to the OpenAI Codex CLI for delegated implementation.

    by andreilungeanu · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Orchestrator

    Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.

    by crAK1644 · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • Codex Subagent

    Delegate coding tasks to the OpenAI Codex CLI, installed separately, with explicit model and effort.

    by parisbs · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • reevesagents

    Run and steer other AI coding CLIs (Claude Code, Codex, Kimi, Qwen, OpenCode, Gemini CLI, Cline CLI, Crush, Goose, Kilo Code, Letta Code, Mistral Vibe, Grok Build, Kiro CLI…

    by Mert Kaya · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • SkillGild

    Search and run hosted AI agent skills for Claude Code, Codex, Cursor and Gemini CLI.

    by SkillGild · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

delegate-to-codex

In its own words, on Community GitHub marketplaces:

Install in Claude Code. Routes worker tasks out to the Codex CLI (GPT-6 Astra, Sol, Luna).

thread-keeper

In its own words, on Official MCP Registry:

Multi-agent shared brain across Claude, Codex, Antigravity, Gemini, Copilot, and VS Code.

How to run each

delegate-to-codex

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

thread-keeper As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio thread-keeper -- uvx threadkeeper

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: delegate-to-codex · What it can do: thread-keeper · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built