PR #17539: feat(gateway): add optional systemd Conflicts= directive for multi-profile hosts

• Repository: NousResearch/hermes-agent
• Author: alexzhu0
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/17539

Description (problem / solution / changelog)

Closes #17396.

Summary

When multiple Hermes profiles live on the same host (per-environment / per-workspace separation), their generated gateway/api units can step on each other at start time — port 18800 collision, resource contention, etc. Until now the only protection has been a hand-written systemd drop-in, which hermes gateway install --force silently regenerates over.

Adds an opt-in top-level systemd_conflicts config key. When non-empty, generate_systemd_unit() emits matching Conflicts= and Before= directives in the [Unit] section so systemd enforces mutual exclusion at start time and gives a deterministic tie-break.

Config shape

# config.yaml (any profile)
systemd_conflicts:
  - hermes-api-hermes-infrastructure.service
  - hermes-gateway-hermes-transversal.service

Generated unit contains:

[Unit]
Description=Hermes Agent Gateway - Messaging Platform Integration
After=network-online.target
Wants=network-online.target
Conflicts=hermes-api-hermes-infrastructure.service hermes-gateway-hermes-transversal.service
Before=hermes-api-hermes-infrastructure.service hermes-gateway-hermes-transversal.service
StartLimitIntervalSec=600
StartLimitBurst=5
…

Backward compatibility

Default behavior unchanged. When systemd_conflicts is absent or empty (the default), the conflicts block is empty-string and the rendered unit is byte-identical to the pre-patch output. Existing installs don't need any action.

Both user-scope and system-scope units are covered.

Tests

4 new tests under TestGeneratedSystemdUnits:

• test_unit_omits_conflicts_when_not_configured — baseline preserved
• test_user_unit_includes_conflicts_when_configured
• test_system_unit_includes_conflicts_when_configured
• test_conflicts_entries_strip_whitespace_and_empties — defensive: empty / None entries are filtered so the output never contains Conflicts= with a trailing space or bare directive

Files

• hermes_cli/gateway.py: +26 / -2 (adds _get_systemd_conflicts() helper + injects a conflicts_block string into both user and system unit templates)
• tests/hermes_cli/test_gateway_service.py: +56

Changed files

• hermes_cli/gateway.py (modified, +37/-2)
• tests/hermes_cli/test_gateway_service.py (modified, +45/-1)

PR #17568: feat(gateway): add compression notifications for gateway platforms

• Repository: NousResearch/hermes-agent
• Author: HBastet
• State: closed | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/17568

Description (problem / solution / changelog)

Problem

In CLI (shell) mode, users see real-time compression notifications:

⚠️ Session compressed 2 times — accuracy may degrade. Consider /new to start fresh.

In gateway mode (Matrix, Telegram, Discord, Slack, etc.), compression was completely silent. Users had no visibility into when it happened or whether it was effective.

Solution

Add user-facing compression notifications in gateway mode:

• ⏳ Compaction du contexte en cours… — before compression starts
• ✅ Compaction terminée (XK → YK tokens) — after successful compression
• ⚠️ Compaction insuffisante — envisagez /new — when compression was ineffective (tokens still ≥ 95% of context)
• ⚠️ Session compactée N fois — when session has been compressed ≥2 times (quality degrades)
• ⚠️ Compaction échouée : error — on failure

Technical changes

1. gateway/hooks.py — Added session:compress to the documented events list. Hook system already supports any event via emit(), so no code changes needed.

2. gateway/session.py — Added hygiene_count: int = 0 to SessionEntry for tracking the number of times session hygiene has auto-compressed. Serialized/deserialized in to_dict()/from_dict(). Backward-compatible — old data defaults to 0.

3. gateway/run.py — Added notifications in the session hygiene section (lines ~3411-3570):

   • Pre-compression: emit session:compress hook with phase=start + send ⏳ Compaction… message
   • Post-compression: emit session:compress hook with phase=end + send success/insufficient/repeated warning messages
   • Error: send failure notification

4. Tests:

   • Updated test_session_hygiene_messages_stay_in_originating_topic to verify notifications ARE sent (previously asserted len(adapter.sent) == 0)
   • Added TestHygieneCount class in test_session.py for serialization/deserialization/backward-compat

Backward compatibility

• SessionEntry.hygiene_count defaults to 0 for old session data
• Hook session:compress is a new event — existing hooks are unaffected
• Notification messages are best-effort — failures are caught and logged, never blocking

Closes #17396

Changed files

• gateway/hooks.py (modified, +1/-0)
• gateway/run.py (modified, +114/-7)
• gateway/session.py (modified, +6/-0)
• tests/gateway/test_session.py (modified, +47/-0)
• tests/gateway/test_session_hygiene.py (modified, +16/-3)

PR #17635: feat(gateway): add dynamic Conflicts=/Before= directives for multi-profile gateway units

• Repository: NousResearch/hermes-agent
• Author: HBastet
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/17635

Description (problem / solution / changelog)

Problem

When Hermes generates multiple gateway profiles (infrastructure, transversal, hb), each profile creates an independent systemd service. If two profiles start simultaneously, they conflict on the same Matrix device ID, ports, and state — causing crashes and data corruption.

The only protection was a manual drop-in (10-conflicts.conf) or a masked service link, which is not automatic and disappears when the service is regenerated.

Solution

generate_systemd_unit() now automatically:

1. Detects other installed hermes-gateway*.service files on the machine
2. Injects Conflicts=<other>.service and Before=<other>.service directives into the [Unit] section
3. Normalizes these dynamic directives out during staleness comparison, preventing spurious repairs when profiles are added/removed
4. Refreshes other gateway units after installation to keep their conflict directives in sync

This ensures mutual exclusion at the systemd level — no manual drop-ins needed.

New functions

Test fixes (pre-existing, not caused by this patch)

6 tests were failing on root because generate_systemd_unit(system=True) refuses to create a system service for root without run_as_user, and _preflight_user_systemd() fails when the user D-Bus session is unavailable. All 6 now have the necessary mocks:

• test_system_unit_avoids_recursive_execstop_and_uses_extended_stop_timeout
• test_system_unit_includes_local_bin_in_path
• test_systemd_start_refreshes_outdated_unit
• test_systemd_restart_refreshes_outdated_unit
• test_systemd_restart_self_requests_graceful_restart_and_waits
• test_systemd_restart_recovers_failed_planned_restart

New tests

TestGatewayConflictDirectives class with 9 tests covering:

• Service discovery and self-exclusion
• Conflict directive generation with/without other services
• Normalization stripping only gateway/api conflict directives
• System and user unit generation including conflict directives
• Staleness check ignoring dynamic conflict directives

Test Results

All 116 tests pass (107 original + 9 new).

Closes #17396

Changed files

• hermes_cli/gateway.py (modified, +179/-3)
• tests/hermes_cli/test_gateway_service.py (modified, +187/-3)