hermes - 💡(How to fix) Fix Enforce role identity and action policy for L

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

What to build

Add role-based identity and action policy enforcement to the L bridge. The bridge should distinguish owner, owner agent, partner agent, external person, and guest identities, then apply the auto, confirm, and forbidden action policy before responding or routing work.

Acceptance criteria

  • The bridge can classify request actors into owner, owner_agent, partner_agent, external_person, or guest from configuration or authenticated metadata.
  • The bridge enforces auto, confirm, and forbidden decisions before executing or proposing actions.
  • Attempts to access leo_private or act on Leo's behalf require owner confirmation.
  • Tests cover at least one allowed, one confirmation-required, and one forbidden action.

Blocked by

  • #23838

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Enforce role identity and action policy for L