# NousResearch/hermes-agent · Gateway crash when display config is null

## Open now

- Nothing open on GitHub.

A bug where a bare or null \`display:\` key in gateway config causes an AttributeError crash, along with multiple fix attempts guarding against null display config values in related code paths.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #106305. Verify it addresses your case.
- **Recommended:** read PR #106305 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-106305`. 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.50`: 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

- #105674: gateway: AttributeError crash when profile config has \`display: null\` (0.21.x)

## Prior & competing PRs

- **#106305: fix(gateway): a bare \`display:\` key in config.yaml no longer crashes every gateway turn (#105674, salvage #105680)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/run_turn_runner.py`, `tests/gateway/test_display_null_turn_wiring.py`
- **#105680: fix(gateway): guard display config reads against present-but-null values**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `6459c406b0`, `#106305`
- **#105817: fix(gateway): guard display: null in _wire_turn_agent_callbacks (#105674)**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#105680`, `#105674`

## Fix status

- Merged to main in PR #106305 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-09`.