Turnback

Name: Turnback
Author: MFaizR77

by MFaizR77version 0.9.1i★ –iRuns on your computer

Registry nameio.github.MFaizR77/turnback

Install

Overview

Description from the maker (original English)

Undo a coding agent turn, including shell commands and untracked files.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "turnback": {
      "command": "npx",
      "args": [
        "-y",
        "turnback",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add turnback -- npx -y turnback mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "turnback": {
      "command": "npx",
      "args": [
        "-y",
        "turnback",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "turnback": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "turnback",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account MFaizR77, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32589 servers in this category
Published to the registry more recently than 62% of the other 32589 servers in this category
Basic checks equal to or better than 100% of the other 32589 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Turnback safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.1) reached the registry 24 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Detailing Manager

by RadoslavMoshev

Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Undo for AI coding agents, even after `rm -rf`.

One undo history for Claude Code, Codex, Cursor, Gemini CLI, OpenCode, and Antigravity CLI.

A real Turnback run. The agent is simulated with Claude Code's hook payloads; the rm -rf and every Turnback line are real. Recreate it with python scripts/demo/make_demo.py.

Why

Agent checkpoints track the agent's own edit tools. Claude Code's documentation says it plainly: "Checkpointing does not track files modified by Bash commands." So when an agent runs rm -rf, mv, a code generator, or git checkout -- ., rewind cannot bring those files back.

Turnback snapshots the workspace before every shell command and edit, into a shadow git repo under ~/.turnback:

Undo a whole turn, or go back to just before one step of it.
Tracked, untracked, and gitignored files (like .env) up to 5 MB are covered.
Nothing writes to your project's .git unless you run turnback export --commit, and hooks never block the agent.
One history across six agents. Through MCP, the agent can list and diff its own turns and restore them in two steps: a plan first, then the change.

Install

In Claude Code:

claude plugin marketplace add MFaizR77/turnback

claude plugin install turnback@turnback

Then use /turnback:turns, /turnback:diff-turn, /turnback:undo, and /turnback:report.

In Codex (available in the next npm release):

codex plugin marketplace add MFaizR77/turnback

codex plugin add turnback@turnback

Start a new session, review and trust Turnback's hooks in /hooks, then use $turnback:turns, $turnback:diff-turn, $turnback:undo, and $turnback:report.

The plugin needs Turnback 0.9.1 or later. To try unreleased plugin changes from a checkout, see local testing.

For Codex, Cursor, Gemini CLI, OpenCode, Antigravity CLI, or the CLI on its own (Node.js 22+ and Git 2.25+):

npm install -g turnback

turnback install all # user-level hooks and MCP for every agent turnback install codex --project # or one agent, in this project only

Claude Code, Codex, OpenCode, and Antigravity CLI have been tested live; Gemini CLI and Cursor are covered by tests built from their documented hook payloads. Details per agent: installation.

Compared with Claude Code's `/rewind`

	`/rewind`	Turnback
Edits made by the agent's edit tools	✅	✅
Files changed by shell commands (`rm`, `mv`, codegen)	❌	✅
Untracked and gitignored files	only files its edit tools changed	✅ up to 5 MB
Other agents	❌	Codex, Cursor, Gemini CLI, OpenCode, Antigravity CLI
Go back to a point inside a turn	❌	✅ `--before-step`
Rewind the conversation	✅	❌ files only

They work side by side: rewind the conversation with /rewind, and the files with Turnback.

Everyday use

turnback --help                     # commands, options, and quick-start examples

turnback list # recent turns with their prompts turnback diff # what a turn changed turnback undo --dry-run # show the plan turnback undo --yes # undo the latest turn turnback redo --yes # changed your mind turnback steps # each edit and shell command in a turn turnback restore --before-step 3 --yes turnback mark "before migration" # a checkpoint of your own turnback run -- npm run codegen # any command as an undoable turn, no agent needed turnback recover src/app.ts # bring back one file (or a folder) an agent deleted turns ago turnback blame src/auth.ts # which turn and prompt wrote each line turnback report --pr --apply # add which prompts wrote this branch to its pull request turnback du # Turnback's disk use for every workspace turnback ui # timeline in the browser

Without an agent

turnback run records any command as a turn, so a code generator, a codemod, or an agent without hooks gets the same undo. blame shows which turn wrote each line, and recover brings back a single file:

All commands, including log, search, report, compare, and export: commands. More: restore, MCP, scope and limits.

How it works

The hook before a mutating tool takes the turn baseline. The hook before a shell command captures the whole tree; later edits capture the affected paths. The end of the turn captures the result. The initial snapshot is warmed in the background on install and session start. Hooks always let the agent continue when recording fails; a failed, skipped, or unprotected state is visible through status.

Tracked, untracked, and gitignored files up to 5 MB are covered. Build output and dependency directories are excluded. Extra rules use gitignore syntax in .turnbackignore; global rules go in ~/.turnback/config.json as {"exclude":["pattern"]}.

Workspaces above 100k files or 2 GB switch to edits-only mode: only paths touched by edit tools are snapshotted, shell commands are recorded as unprotected, and restore touches only recorded paths. Turns older than 7 days and outside the last 50 turns are cleaned up automatically, at most once a day, in every workspace and not only the one in use. Data of a workspace that was deleted is removed after 30 idle days; set {"autoClean": false} in ~/.turnback/config.json to keep it.

Contributing

Issues labeled good first issue are small and say which files they touch, and support for more agents is welcome. Start with CONTRIBUTING.md and the architecture overview. Questions and ideas go to Discussions.

Contributors

Every merged pull request is credited in the release notes.

Development

Module	Contents
`src/cli/`	`main.ts`: CLI and hook entry point (built as `dist/cli.js`); `args.ts`: argument parsing
`src/core/`	`recorder.ts`: snapshot rules per event; `store.ts`: journal, snapshots, turns, steps, marks, status, `gc`; `restore.ts`: restore planning and execution, undo, redo; `format.ts`: text output; `quote.ts`: shell-safe arguments; `journal.ts`, `lock.ts`, `config.ts`, `types.ts`
`src/git/`	`shadow.ts`: shadow git repo wrapper
`src/workspace/`	`workspace.ts`: workspace scanning and exclusion rules
`src/agents/`	`adapters.ts`: each agent's hook payload → `HookEvent`; `install.ts`: hook and MCP installation per agent; `opencode-plugin.ts`: generated OpenCode plugin
`src/mcp/`	`server.ts`: stdio MCP server
`src/ui/`	`server.ts`: read-only local server for `turnback ui`; `page.ts`: its single page

npm run check

npm run bench

The benchmark creates a temporary 10k-file repo and reports latency without making it a strict CI gate. CI runs the tests and benchmark on Windows, macOS, and Linux × Node 22/24.

From a clone, run npm ci && npm run build and use node dist/cli.js in place of turnback.

Releasing

Set the same version in package.json and in both version fields of server.json, commit, then push a v tag. The Publish workflow checks that the versions match, runs the tests, publishes to npm through trusted publishing (provenance is attached automatically), and publishes server.json to the MCP registry as io.github.MFaizR77/turnback.

Also update src/core/config.ts, both plugin manifests, and the npm ranges in .claude-plugin/marketplace.json and .agents/plugins/marketplace.json.

npm trusted publishing is configured on the package page at npmjs.com (repository MFaizR77/turnback, workflow publish.yml), which needs the package to exist. The first version is therefore published once by hand with npm publish --access public; pushing its tag afterwards skips npm (the version exists) and only publishes to the MCP registry. Later tags do both.

License

MIT

Turnback

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Detailing Manager

README from the maker

Why

Install

Compared with Claude Code's /rewind

Everyday use

Without an agent

How it works

Contributing

Contributors

Development

Releasing

License

Compared with Claude Code's `/rewind`