# NousResearch/hermes-agent · custom_instructions ignored in mem0 OSS backend config

## Open now

- Nothing open on GitHub.

A bug where custom_instructions set in mem0.json are silently dropped because OSSBackend hardcodes its config key list, along with associated fixes to pass that field through properly.

## 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

- #114201: mem0 OSS: custom_instructions in mem0.json is silently dropped (OSSBackend hardcodes the config key list)

## Prior & competing PRs

- **#114205: fix(memory/mem0): pass custom_instructions through OSSBackend**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#114206`, `#114201`
- **#114206: fix(memory): honor OSS custom extraction instructions**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `aa4be410564`

## Fix status

- No merged fix on record.