Cairn
NousResearch/hermes-agent

Switch pending write IDs to sequential integers

Cluster 60446 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and PRs propose replacing random UUIDs with sequential auto-incrementing IDs for pending skill/memory writes. The change affects how pending write items are identified in the approval workflow.

Open issues1

  • Issue#60446Enhancement: Pending skill/memory IDs should be sequential instead of random UUIDs

Open PRs1

  • PR#60530feat(approval): use sequential pending write ids

1 PR closed without merging

From the close comments: duplicate 1

  • #60642 feat(tools): use sequential auto-incrementing IDs for pending writes · duplicate → #60530, #60446
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/60446.json
cluster/60446.md