GitHub Issuesdemand signalby Alek2077built with AIheuristic score

openai/codex: CLI: Add /rewind checkpoint restore that reverts both chat context and Codex-applied code edits

Opportunity

AI-buildable

Traction

Creativity

The take

effort: ~1-2 weeks

Heuristic estimate (AI scoring not configured). openai/codex: CLI: Add /rewind checkpoint restore that reverts both chat context and Codex-applied code edits shows 152 engagement on ghissues. Buildability is inferred from the description; add an AI gateway key for a tailored read.

Deliver it

A starter prompt for Claude Code, what you'll need, and how to reach them.

Build a minimal version of "openai/codex: CLI: Add /rewind checkpoint restore that reverts both chat context and Codex-applied code edits". Read the original at https://github.com/openai/codex/issues/11626 for the exact requirements, then scaffold a Next.js + Tailwind app, implement the smallest valuable slice first, and ship it. (Enable AI scoring for a tailored, detailed prompt.)

Prerequisites — cost & what to learn

Node.js + a Vercel accountFree · Free (hobby tier)✓ in your stack
Part of the operator's house stack.
Any APIs/data the find depends onFree tier · Varies — enable AI scoring for a real cost read.📚 needs study
Depends on the find — enable AI scoring for specifics.
Learn it: Search getting-started ↗

Setup steps

How you'd build it

1Open the project and list its 3-5 core user-facing features.
2Scaffold a Next.js + AI Gateway app and rebuild the smallest valuable slice first.
3Wire any external data/APIs it depends on; stub what you can't access.
4Ship a thin public version and measure whether the demand signal reproduces.

Risks & moats

Traction may be launch-day spike rather than durable demand.
Heuristic scoring can't judge true novelty or competition — verify manually.

Original context

### What variant of Codex are you using? CLI ### What feature would you like to see? Add a native `/rewind` checkpoint flow that restores both: - conversation state - Codex-applied workspace edits from the same selected checkpoint. **Current behavior**: Esc rewind only rewinds conversation/history (fork point), but does not revert code changes made after that point. **Requested behavior**: - `/rewind` shows recent checkpoints with: - timestamp - prompt snippet - files changed - Selecting a checkpoint rewinds chat and reverts Codex-made edits after that checkpoint. - Provide a pre-apply preview of file changes to be reverted. - Allow editing the restored prompt before resubmitting. Safety requirements: - Only revert Codex-created edits after the selected checkpoint. - Do not touch unrelated local changes that existed before checkpoint creation. - If any file cannot be cleanly restored, show conflicts and require explicit confirmation before partial apply. ### Additional information Repro for current gap: 1. Ask Codex CLI to modify files. 2. Press Esc twice to rewind a prior user message and fork. 3. Conversation rewinds, but prior