Hermes rewind scores 8 out of 10 from me: the edit and fork moves are about as safe as a conversation rewind can be, and the only real drag is that it lives in the terminal alone.

The feature shipped in Hermes Agent v0.23.0 on 5 November 2026, per the release notes.

Every score below is editorial judgement taken from the official docs, the release notes and the pull request that added it, not from a benchmark run.

If you want my team to look over your own agent stack, get your Backlink Gameplan, or try Polar Rank free for 3 days.

The Hermes Rewind Scorecard

CriterionScore /10Why
Getting into the picker8/rewind or a double Esc, but Esc Esc only opens on an idle, empty prompt.
Edit and resend9Nothing is cut until you send, and cancelling leaves the session as it was.
Fork9New session from just before the prompt, prompt prefilled and unsent, parent untouched.
Direct shortcuts8/rewind N and /rewind fork N skip the list entirely.
Audit trail8Cut turns are archived like /undo and still show in exports.
Surface coverage5TUI and classic CLI only; messaging-platform rewind is later work.
Picker detail7Newest-first list with preview and transcript jump, but image prompts cannot be picked.
Documentation7Docs and code are precise; one release-note sentence reads wider than the feature.

The eight scores average 7.62, which rounds to the headline 8.

How I scored it: a 9 means the docs describe behaviour I would not change, a 7 means it works with a caveat a new user will notice, and a 5 means the gap rules out a whole group of users.

Each reason in the table points to a line in the TUI guide, the CLI guide, the slash-command reference or the pull request.

I weighted every criterion equally, because a rewind tool that is safe but unreachable is as much use as one that is reachable but risky.

What Is Actually Being Rated

Rewind is a picker of your own earlier prompts, newest first.

From it you either rewrite one and resend it, or fork a new session that stops just before it.

The TUI guide and the classic CLI guide both describe it, and the CLI calls the same screen the backtrack picker.

It needs the shared gateway in the TUI, and v0.23.0 or later everywhere.

It is worth being clear about what it is not.

It is not a file undo, it is not a privacy delete, and it is not available from Desktop or chat apps through the same command.

The scores judge it on the job it claims: going back to an earlier prompt in a terminal session without losing control of the history.

Strength: Nothing Is Lost Until You Commit

This is the design choice that earns the high marks.

Pressing Enter on a prompt only loads it into the composer.

The cut happens when you send the edited text, and not a moment sooner.

Esc, Ctrl+C or an empty submit backs out with the session intact.

A rewind tool that trimmed history on selection would punish every slip of the arrow key.

This one does not.

In the TUI, Esc also steps back one level at a time, from editing to the list to closed, so there is always a way out that changes nothing.

Strength: Fork Keeps Both Timelines

Press f and Hermes builds a separate session holding everything before the highlighted prompt.

The prompt waits in the composer, unsent, so you can change it first.

The original session is not touched.

Forking the very first prompt simply opens a fresh session with that prompt prefilled, which is a tidy edge-case answer.

The pull request notes that the fork uses the same branching primitive Desktop's message-level branch already sends, which is a good sign: one mechanism, reused, rather than a second one to drift.

🔥 Get the setups behind these ratings. Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members testing Hermes features as they land. → Join the AI Profit Boardroom

Strength: An Honest Audit Trail

Edit and resend archives the chosen prompt and everything after it, using the same soft delete as /undo.

The sessions guide confirms exports carry messages removed by rewind or edit, each with its active flag.

For anyone who needs to show what an agent was told and when, that is the right call.

The flip side is that rewind is no privacy tool, and the docs say so plainly enough that nobody should be surprised.

Limit: Terminal Only

This is where the score drops.

The slash-command reference and the code mark /rewind as a terminal command: the TUI and the classic CLI.

Desktop has its own edit-and-resend already, so Desktop users are not stranded.

Chat-app users are: rewinding from Telegram, Slack or Discord is listed in the pull request as later work.

A team that runs Hermes mainly through a messaging gateway gets nothing from this release yet.

The TUI also needs the shared gateway running, and it tells you so with a clear message when it is missing.

Limit: The Double-Esc Has Sharp Edges

Esc Esc opens the picker only on an idle, empty prompt.

With a draft in the box it discards the draft.

Mid-turn, Esc interrupts the agent.

All three behaviours are documented and sensible on their own, but a new user will hit at least one of them.

Typing /rewind avoids the problem entirely.

In the classic CLI, a discarded draft can be pulled back with the Up arrow, which softens the blow.

Bonus: deny and redirect

The same pull request adds an approval choice in the TUI: "No, and tell Hermes what to do instead".

You deny the command and type a correction, and Hermes gets both in the running turn.

It is not part of the score, but it removes a lot of the cases where you would otherwise rewind at all.

Limit: Images And Files Sit Outside It

A prompt that carried an image is listed by number only and cannot be picked.

And rewind is about conversation history only.

Files the agent changed stay changed; that job belongs to /rollback, which needs checkpoints switched on first, per the checkpoints guide.

That split is reasonable, since chat history and files live in different places, but it means a careful operator runs both tools together.

I would like to see the picker warn when files changed after the chosen prompt; for now, check that yourself before you cut.

The Documentation Conflict Worth Knowing

The release highlight says the original session "stays exactly as it was" right after describing both moves.

The docs and the code are narrower: only the fork leaves the original alone.

Edit and resend does change the current session, by archiving the chosen prompt and the turns after it.

The same highlight says a fork starts "from that point", while the detailed notes and docs say it holds everything before the chosen prompt.

I scored the feature on the docs and code, which agree with each other.

📞 Want a second opinion before you roll Hermes out? Get your Backlink Gameplan and my team will check your agent workflows, your content and how they connect, or try Polar Rank free for 3 days. Backlink Gameplan or try Polar Rank free for 3 days

How It Compares With The Other History Commands

ToolBest atWeak at
/rewind editFixing an older prompt in one line of historyKeeping the first attempt
/rewind forkTrying a second approach from an earlier pointNothing major; it adds a session to manage
/undoRemoving only the last exchangeAnything older than one turn
/branchCopying the session as it stands nowGoing back to an earlier point
/compressShrinking a long sessionCorrecting a mistake

Compaction gets its own scorecard in my Hermes compaction verdict; it solves length, not wrong turns.

Who Should Use Hermes Rewind

  • Operators who run Hermes in the TUI or classic CLI every day.
  • Agencies that build one client deliverable, then need a variant for a second client from an earlier point.
  • Small teams writing customer emails or captions who want to compare two tones without retyping the setup.
  • Anyone who has ever started a new chat just to escape one bad prompt.

The common thread is a long, setup-heavy session where the early messages carry real value.

Rewind protects that setup; starting over throws it away.

Who Should Skip It For Now

  • Teams that only talk to Hermes through Telegram, Slack or another chat app.
  • Anyone hoping rewind will scrub sensitive text, since archived turns stay in exports.
  • Users who need file changes undone and have not switched on checkpoints.

Small-Business Examples That Fit The Score

  • An accountant's office forks a client newsletter draft into a plain version and a friendlier version, then the partner picks one.
  • A salon rewinds to the brief for appointment reminders, adds the missing cancellation wording, and resends it.
  • An online shop rewinds to a product-description prompt that used the wrong product name and sends the fix.

Each one is a single prompt fix or a single fork, which is exactly the job this feature does well.

None of them needs files restored, and all of them happen in a terminal session, which keeps them inside the feature's strong zone.

A plumbing firm that only talks to Hermes through a team chat app, by contrast, would score this feature far lower for its own use.

Final Verdict

Rewind is a careful, well-documented feature that solves a real annoyance in long agent chats.

The safe commit point and the clean fork are the best parts.

Terminal-only coverage holds it back from a 9.

Rating: 8 out of 10, and an easy yes for anyone already working in the Hermes terminal.

When messaging-platform rewind lands, coverage is the score I would revisit first.

🔥 Use this feature with a proven workflow behind it. Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video trainings and four live coaching calls a week with members who run Hermes daily. → Join the AI Profit Boardroom

If you want the team to sanity-check your setup, get your Backlink Gameplan, or try Polar Rank free for 3 days.

FAQ: Hermes Rewind Verdict

What score does Hermes rewind get?

8 out of 10, averaged from an eight-criterion scorecard built from the official docs, release notes and pull request.

What is the biggest weakness?

Coverage. Rewind runs in the TUI and classic CLI only, and rewinding from messaging platforms is still listed as later work.

Is edit and resend risky?

Less than it sounds. Nothing is cut until you send the edited prompt, and the cut turns are archived rather than wiped.

Does the release note overstate the feature?

One sentence reads that way. It says the original session stays as it was, but per the docs that holds for fork only; edit and resend changes the current session.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

  • I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
  • I've grown a YouTube channel to 400,000+ subscribers.
  • I wrote "Link Building Mastery".
  • My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Rated 8 out of 10: update, try one fork today, and get your Backlink Gameplan, try Polar Rank free for 3 days, or join the AI Profit Boardroom if you want help building around Hermes rewind.