# NousResearch/hermes-agent · Switch pending write IDs to sequential integers

## Open now

- 1 issue, 1 PR open on GitHub.
- #60446: Enhancement: Pending skill/memory IDs should be sequential instead of random UUIDs
- PR #60530: feat(approval): use sequential pending write ids

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.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#60530: feat(approval): use sequential pending write ids**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#60446`
  - files: `tests/tools/test_write_approval.py`, `tools/write_approval.py`
- **#60642: feat(tools): use sequential auto-incrementing IDs for pending writes**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#60530`, `#60446`

## Fix status

- No merged fix on record.
- Subsystem: `agent`