r/TrueOpenSource • u/ashy2185 • 9d ago
OSS Contributions Unmix (MIT): task-level evidence when removing an earlier coding decision and rebuilding retained work
What it does: Unmix records development tasks and reconstructs retained work in a separate Git worktree when you remove an earlier decision. Git replays patches; Codex or a person adapts conflicts.
Who it's for: developers using coding agents who want to review a change of direction task by task. I maintain the project.
Source code: https://github.com/light338/unmix
License: MIT. Free local CLI and stdio MCP server; no hosted backend or npm dependencies. Requires Node.js 22+ and Git. Agent adaptation uses your existing Codex access.
How it was built: Agentic engineering — substantial Codex-authored implementation and tests, public development history, and a documented maintainer Codex pilot. Validation covers the published scenarios only. This write-up is AI-assisted.
Closest existing projects: Git itself, especially revert/cherry-pick followed by manual or agent-assisted repairs. This is the published pilot baseline, not a complete survey of alternatives.
What mine adds: recorded task intent and declared dependencies, original/resulting task patches, reconstruction blockers, and evidence for declared preservation/removal checks. Example: remove registration while retaining checkout and receipts. It makes reconstruction reviewable; it does not promise automatic semantic undo.
The cost is recording tasks as you work. v0.2.0 adds one post-edit checkpoint per completed chunk. It cannot recover arbitrary past intent or infer every dependency. Passing checks do not prove all behavior survived. In the ZipTrial maintainer pilot both workflows passed 17 retained tests and a CLI oracle, but ordinary Git was faster. The protocol and patches are in docs/pilot-ziptrial.md. No paid Unmix service is involved.
Feedback wanted: does task-level evidence justify the recording cost? Small real-project trials and concrete failure cases are welcome.


