NousResearch/hermes-agent

Add /diff command to review agent session changes

Cluster 4250 · agent. Data as of 2026-10-26 12:29 UTC

1 open item. Fix merged in #72240 on 27 Jul 2026. Check it covers your case.

open issue

open PRs

items grouped

Known?: Yes. 5 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #72240. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 1 issue and 0 PRs.

Next step: read #72240, then check whether your report is the one still open.

Read #72240 Pick up a Lab task

These issues and pull requests concern the absence of a /diff command and proposals to add one, allowing users to review git changes made by the agent during a session.

Open issues1

Issue#4865[UX] No /diff command to see what the agent changed this session

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#72240 feat(diff): cross-surface /diff with staged/all/session modes (salvage of #4839 by @SHL0MS)

merged to main

files: cli.py, gateway/run.py, gateway/slash_commands.py, hermes_cli/cli_commands_mixin.py, hermes_cli/commands.py, locales/af.yaml, locales/ar.yaml, locales/de.yaml, locales/en.yaml, locales/es.yaml, locales/fr.yaml, locales/ga.yaml, locales/hu.yaml, locales/it.yaml, locales/ja.yaml, locales/ko.yaml, locales/pt.yaml, locales/ru.yaml, locales/tr.yaml, locales/uk.yaml (+10 more)

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

#4839 feat: add /diff command to show git changes in working directory · merged via another change → #72240
#53527 feat(diff): /diff — review everything Hermes changed this session · done elsewhere → #72240

Closed issues · 1

Closed#4250[UX] No /diff command to see what the agent changed this session

How this cluster was grouped

Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
Members outside that structural core may belong to a different underlying problem.
Pairwise link density 0.34: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: agent
Merged PRs: #72240
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 27 Jul 2026

For your agent

The same facts, typed.

cluster/4250.json
cluster/4250.md