NousResearch/hermes-agent

Message edit failures due to ordinal mismatch bug

Cluster 88082 · apps/desktop. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #91302 on 21 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #91302. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #91302. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #91302, then check it covers your case.

Read #91302 Pick up a Lab task

These issues concern a bug where editing or restoring messages fails with a 4030 error, caused by client ordinals becoming window-relative rather than absolute during tail-only transcript prefetch in long sessions. Fixes target durable ID-based truncation and profile DB ordinal handling.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

#91302 fix: editing a message in an old session fails (profile DB + window-relative ordinal)

merged to main

files: apps/desktop/src/app/session/hooks/use-prompt-actions/index.test.tsx, apps/desktop/src/app/session/hooks/use-prompt-actions/rewind.test.ts, apps/desktop/src/app/session/hooks/use-prompt-actions/rewind.ts, tests/tui_gateway/test_session_profile_db.py, tui_gateway/methods_prompt.py, tui_gateway/methods_tools.py, tui_gateway/server.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#88092 fix(desktop): aim truncations by durable id alone (edit/restore refused 4030) · superseded by another PR → #91302, #76366

Closed issues · 1

Closed#88082[Bug]: Desktop — every message Edit refused with 4030 ordinal mismatch on long sessions (tail-only transcript prefetch makes client ordinal window-relative)

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: 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: apps/desktop
Merged PRs: #91302
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 21 Aug 2026

For your agent

The same facts, typed.

cluster/88082.json
cluster/88082.md