Skip to content

fix(gateway): respect explicit platform disable for HA and wrap kanban auto-decompose in profile scope - #76864

Closed
bwoliveira wants to merge 1 commit into
NousResearch:mainfrom
bwoliveira:fix/kanban-multiplex-auto-decompose
Closed

fix(gateway): respect explicit platform disable for HA and wrap kanban auto-decompose in profile scope#76864
bwoliveira wants to merge 1 commit into
NousResearch:mainfrom
bwoliveira:fix/kanban-multiplex-auto-decompose

Conversation

@bwoliveira

Copy link
Copy Markdown

Summary

Fixes two related issues when running Hermes Agent in multiplexed gateway mode ():

  1. ****: Home Assistant platform overrides did not check when was present in the environment. In multiplexed setups, secondary worker profiles with were force-enabled during env override processing, causing duplicate credential errors on startup.
  2. ****: Embedded ran on background threads () without entering . When invoked LLM calls via , threw secret-scope errors in multiplexed mode, silently failing triage auto-decomposition every 15s.

Validation

  • Unit tests run via (all passed cleanly).
  • Verified live on multiplexed gateway setup: secondary worker profiles load without duplicate credential errors, and triage tasks automatically decompose on the 15s tick.

…decompose in profile scope

- Respect explicit enabled: false in config.yaml for Home Assistant platform during env overrides to prevent secondary profiles in multiplexed mode from failing startup on duplicate credential checks.
- Wrap embedded kanban auto-decompose tick in _profile_runtime_scope so LLM calls via auxiliary.kanban_decomposer succeed in multiplexed mode without raising get_secret errors.
@alt-glitch alt-glitch added type/bug Something isn't working comp/gateway Gateway runner, session dispatch, delivery comp/cron Cron scheduler and job management area/config Config system, migrations, profiles P2 Medium — degraded but workaround exists sweeper:risk-compatibility Sweeper risk: may break existing users, config, migrations, defaults, or upgrades duplicate This issue or pull request already exists labels Aug 2, 2026
@alt-glitch

Copy link
Copy Markdown
Collaborator

This was generated by AI during triage.

Duplicate of #57837 for the kanban auto-decompose secret-scope repair: both install profile secret scope around the same gateway watcher tick. This PR also carries an unrelated Home Assistant enablement change, which should be submitted separately.

@teknium1

teknium1 commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Thanks for identifying two real multiplexed-gateway failure modes.

Problems

  • This combines two independent fixes. The existing maintainer comment identifies the kanban repair as overlapping fix(kanban): run auto-decompose tick under the profile secret scope #57837 and requests the Home Assistant change separately.
  • No regression tests accompany either change. Current HA coverage only verifies env-driven enablement (tests/gateway/test_homeassistant.py:236-251), while current auto-decompose coverage only verifies live settings resolution (tests/gateway/test_kanban_auto_decompose_live.py:17-27). Neither protects these regressions.

Suggested changes

Automated hermes-sweeper review.

@bwoliveira

Copy link
Copy Markdown
Author

Closing this combined PR in favor of #57837 (for the kanban secret-scope fix) and #76871 (standalone PR for the Home Assistant explicit-disable fix). Thanks!

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 area/profiles Multi-profile isolation, HERMES_HOME scoping comp/cron Cron scheduler and job management comp/gateway Gateway runner, session dispatch, delivery duplicate This issue or pull request already exists P2 Medium — degraded but workaround exists sweeper:blast-moderate Sweeper blast radius: moderate — a subsystem or single platform sweeper:risk-compatibility Sweeper risk: may break existing users, config, migrations, defaults, or upgrades sweeper:risk-security-boundary Sweeper risk: may affect sandboxing, auth, credentials, or sensitive data type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants