openai / openai/codex

Curated marketplace review request: Codex WIP continuity plugin

Open
#42,725 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement skills
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App and CLI

What feature would you like to see?

Please consider Codex WIP for the OpenAI curated Codex plugin marketplace.

Codex WIP is a local, skill-only continuity plugin for long-running coding tasks. It preserves recoverable engineering state across usage-limit exhaustion, provider/account changes, inaccessible conversations, crashes, context loss, and machine migration.

The core workflow is intentionally repository-grounded rather than conversation-dependent:

  • $wip checkpoint — persist a lightweight, verifiable checkpoint while a session is healthy
  • $wip handoff — prepare a provider/account/session/machine handoff
  • $wip recover — reconstruct interrupted work from Git, tests, code relationships, and saved WIP evidence
  • $wip resume — verify checkpoint freshness and continue from the first verified next action
  • $wip status — report checkpoint freshness and repository drift without changing business code
Source and package

The repository is also directly addable as a Codex marketplace:

codex plugin marketplace add MuzhiCoder/codex-wip-skill --ref main
codex plugin add codex-wip@codex-wip-skill
Validation and safety
  • Skill-only plugin; no MCP server, hosted service, account, or external authentication is required.
  • Snapshotting is metadata-only by default: it does not persist raw diffs, file contents, environment-variable values, API keys, access tokens, cookies, passwords, or authorization headers.
  • Recovery explicitly freezes business-code edits until state reconstruction is complete.
  • The skill never runs git reset --hard, git clean, force-push, history rewrite, commit, or push as an automatic recovery action.
  • Important recovered claims are labeled VERIFIED, INFERRED, REPORTED, or UNKNOWN instead of treating interrupted-session output as ground truth.
  • Work items are classified as VERIFIED_DONE, IMPLEMENTED_UNVERIFIED, PARTIAL, BLOCKED, NOT_STARTED, or UNKNOWN.
  • Repository CI tests the snapshot/validator behavior and validates the plugin marketplace package on Windows and Linux with Python 3.11–3.13.
Why this belongs in the marketplace

Usage limits, context compaction, provider changes, and machine changes are normal operational boundaries for long-running agentic coding work. Codex WIP gives users a conservative, inspectable recovery workflow that keeps continuity in Git + project-local WIP artifacts rather than relying on a single cloud thread being accessible forever.

The plugin is especially useful when a ChatGPT-account Codex session becomes unavailable and the developer continues in a fresh API-key/custom-provider session, or when work moves to another machine.

Thanks for considering it for curated marketplace review.

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.

Research direction

Review the linked marketplace.json and plugin.json files, then inspect the packaged skill and the repository's stated Windows and Linux CI validation. Compare the plugin's scope and safety claims with the Codex curated marketplace requirements; done means recording an accept, request-for-changes, or rejection decision.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, python
Domain
cli, developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.