# NousResearch/hermes-agent · Langfuse plugin key-prefix validation for custom endpoints

## Open now

- Nothing open on GitHub.

These items address a bug where the Langfuse plugin incorrectly applies Langfuse Cloud key-prefix validation rules to custom endpoint configurations. The fix scopes that validation guard so it only applies to Langfuse Cloud hosts.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 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.

## Closed / duplicate issues

- #72484: \[Bug\]: Langfuse plugin rejects valid custom-endpoint credentials based on key prefix

## Prior & competing PRs

- **#72487: fix(langfuse): scope key-prefix placeholder guard to Langfuse Cloud hosts**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`
- **#73255: fix(plugins/langfuse): skip key prefix validation for custom endpoints (#72484)**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#72487`

## Fix status

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