Original Summary

I am building Unmix, a free MIT-licensed developer tool for the moment you change your mind about an earlier feature after adding other work on top of it. Built with substantial Codex assistance. Example: you added mandatory registration, then checkout, receipt export and a rounding fix. Now you want guest checkout while keeping the other changes. A file revert does not describe which behaviors should survive. Unmix records tasks before editing: intent, declared dependencies, snapshots and checks. It reconstructs the retained changes in a separate Git worktree and asks Codex or a human to adapt conflicts. It keeps the original checkout intact and provides a task-by-task review report. Feedback from two developers led to separate manual interaction checks, an optional preservation checklist, and in v0.1.9, recorded browser/account/session conditions. A previously passed interaction becomes stale after relevant file or declared-condition changes. Passing automated tests cannot satisfy a required missing manual check. It is still an experiment: 70 tests pass and an earlier live Codex/MCP run handled one synthetic example. I do not have confirmed external users yet. It requires recording tasks upfront and does not infer every dependency or guarantee behavior preservation. Browser conditions are declared by the observer, not automatically monitored. Source and walkthrough: https://github.com/light338/unmix Runs locally with Node.js 22+, Git and your existing Codex access. No npm dependencies, hosted backend or telemetry. I would value feedback on the main tradeoff: would you record tasks before each edit to make later changes of direction easier? A small trial that shows where reconstruction breaks would be particularly useful.   submitted by   /u/ashy2185 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/19 23:29:30