Reverting a Fix

An agent fixed it; you don’t like the fix. Revert fix surgically undoes that one change without touching anything that landed after it. Nothing else moves.

From the Cockpit

Select the fixed sub-issue and choose Revert fix in the Inspector (nitpin confirms first). An agent is dispatched to:

1. Undo that one fix. Every resolved fix records the commit that carried it, and the agent adds a new commit reversing exactly that — history is never rewritten, and later fixes stay put. If the commit no longer reverts cleanly, the agent reconciles by hand. If it can’t do that safely, it stops and explains in the thread rather than guessing.
2. Verify the build and land the revert the same way fixes land (your landing setting).
3. Reopen the sub-issue. It returns to the open backlog with a plain-language note about what was reverted and why, and its stale fix metadata cleared.

While it runs you’ll see a Reverting… row on the sub-issue.

From a terminal

nitpin revert --issue 3 --sub-issue 1
nitpin revert --issue 3 --sub-issue 1 --model opus   # escalate the redo

Revert vs. Reopen

• Reopen just flips the status back to unresolved. Use it when you rolled the code back yourself, or the fix never really landed.
• Revert fix does the git work too: undo the commit, then reopen.

After a revert, the sub-issue is an ordinary open item again. A common next move is re-dispatching it at a bigger model — Fix with ▸ and pick a tier up.