NousResearch/hermes-agent

Pending clarify card timing around transcript hydration

Cluster 108718. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #121529 on 25 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #121529 Pick up a Lab task

These items address the ordering and timing of pending clarify card restoration or publication relative to transcript REST hydration during session switches on desktop. Multiple fix attempts and a related issue explore this sequencing problem.

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.

#121529 fix(desktop): publish pending clarify before transcript hydration

merged to main

files: apps/desktop/src/app/session/hooks/use-session-actions.test.tsx, apps/desktop/src/app/session/hooks/use-session-actions/index.ts, apps/desktop/src/app/session/hooks/use-session-actions/transcript-provenance.test.ts, apps/desktop/src/app/session/hooks/use-session-actions/transcript-provenance.ts

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

#108739 fix(desktop): answer pending clarify before transcript hydration lands · done elsewhere → #108718, #121529
#108857 fix(desktop): restore pending clarify through SessionView hydration · other

Closed issues · 1

Closed#108718Desktop: pending clarify card restoration waits for transcript REST hydration after session switch

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.50: 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

Merged PRs: #121529
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 25 Sep 2026

For your agent

The same facts, typed.

cluster/108718.json
cluster/108718.md