Skip to content

fix(gateway): load display config from routed profile - #58413

Closed
tianma-if wants to merge 1 commit into
NousResearch:mainfrom
tianma-if:codex/multiplex-profile-display-config
Closed

fix(gateway): load display config from routed profile#58413
tianma-if wants to merge 1 commit into
NousResearch:mainfrom
tianma-if:codex/multiplex-profile-display-config

Conversation

@tianma-if

Copy link
Copy Markdown
Contributor

Summary

  • read gateway config from the active profile runtime scope when multiplexed turns set a profile-specific Hermes home
  • preserve the existing module-level _hermes_home path for normal gateway config reads and tests that patch it directly
  • add a regression test covering root vs routed-profile display settings

Fixes #58395.

Tests

  • .venv/bin/python -m pytest tests/gateway/test_multiplex_phase0.py -q
  • .venv/bin/python -m ruff check gateway/run.py tests/gateway/test_multiplex_phase0.py
  • git diff --check

@alt-glitch alt-glitch added type/bug Something isn't working comp/gateway Gateway runner, session dispatch, delivery area/config Config system, migrations, profiles P2 Medium — degraded but workaround exists labels Jul 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/config Config system, migrations, profiles comp/gateway Gateway runner, session dispatch, delivery P2 Medium — degraded but workaround exists type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

multiplex_profiles: per-profile display settings ignored, always read from root config

2 participants