Scope desktop pet RPCs to profile secret

NousResearch/hermes-agent · cluster 130450 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

A bug was identified where pet generation RPCs (generate, generate.status, hatch) ran without a profile secret scope, causing fallthrough to Nous Portal under multi-profile hosting. Two fixes address binding or scoping these RPCs to the correct profile secret scope.

Open issues1

  • Issue#130450[Bug]: pet.generate / pet.generate.status / pet.hatch run with no profile secret scope — desktop pet generation always falls through to Nous Portal under multi-profile hosting

Open PRs2

  • PR#130452fix(tui): scope pet generation RPCs to profile
  • PR#130466fix(tui-gateway): bind the profile secret scope on the desktop pet RPCs
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
0 PRs closed without merging

For your agent

The same facts, typed.