Cairn

Agent session rows missing user_id, hardcoded None

NousResearch/hermes-agent · cluster 24321 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

A bug where _ensure_db_session hardcodes user_id=None instead of propagating the authenticated user's ID, causing background, cron, and delegate sessions to be recorded without an owner. Multiple fix attempts address this propagation gap.

Open issues2

  • Issue#24321AIAgent._ensure_db_session() drops user_id on session-row creation; bg/cron/delegate sessions land orphan in state.db
  • Issue#35407[Bug]: _ensure_db_session hardcodes user_id=None — never records the authenticated user

Open PRs2

  • PR#24333fix(agent): propagate user_id to session-row creation for bg/cron/delegate sessions
  • PR#24406fix(agent): namespace user_id for bg/cron/delegate sessions

3 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1 · superseded by another PR 1

  • #24608 fix(agent): propagate self.user_id in _ensure_db_session instead of hardcoded None · superseded by another PR → #24609
  • #24609 fix(agent): propagate self._user_id in _ensure_db_session instead of hardcoded None · duplicate → #24608, #24321
  • #67560 fix(agent): propagate _user_id to session DB + return text summary for non-vision computer_use (#35407 #35817) · merged via another change
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.26: 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
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/24321.json
cluster/24321.md