Repository navigation
[Bug] Hermes integration only updates the default profile and ignores other bot profiles #7674
Description
Client or integration
Other
Area
Proxy and routing
Summary
When I enable the Hermes integration in OpenCodex, the OpenCodex provider configuration is added only to the default Hermes profile. Other bot profiles do not receive the configuration.
Hermes uses a separate profile for each bot, with its own config.yaml. Updating the default profile therefore does not make the OpenCodex provider and model catalog available to the other bots.
Reproduction
- Set up Hermes with a default profile and at least one additional bot profile.
- In OpenCodex, enable the Hermes integration through Connect → Hermes.
- Check the default profile’s configuration.
- Compare it with the additional bot profiles’ configuration files.
On my Windows installation, the configuration files are located under:
- Default:
%LOCALAPPDATA%\hermes\config.yaml - Other profiles:
%LOCALAPPDATA%\hermes\profiles\<profile>\config.yaml
Actual behavior
The default profile receives the OpenCodex provider configuration, but the other profiles remain unchanged. Each additional bot consequently requires separate manual configuration to use OpenCodex.
Expected behavior
The integration should detect existing Hermes profiles and allow users to apply it to selected profiles, or to all existing profiles.
For each selected profile, it should add the OpenCodex provider and model catalog while preserving the profile’s current default model, other providers, and unrelated settings.
Impact
Enabling the Hermes integration appears to connect Hermes, but only the default bot is configured. Users with multiple bots must repeat the setup manually for each profile.
Suggested improvement
Show the detected Hermes profiles on the Connect page, with per-profile integration status and selection controls. This would make the scope of the integration clear and avoid uni
Version
2.91.0
Operating system
Windows 11
Provider and model
No response
Logs or error output
Screenshots and supporting files
No response
Redacted configuration
Checks
- I searched existing issues and documentation.
- I removed secrets, tokens, account details, request credentials, and personal data.
Activity
assets: Hermes profiles Connect screenshot (#7674)
Ingwannu commentedon Oct 25, 2026
Tracking the implementation in Draft #7700, which proposes named Hermes profile connections. It is not merged or released, and I have not certified that branch's Windows behavior.
The existing integration should not silently expand a default-profile connection into permission to write every profile. A named-profile design needs an explicit selected target, separate ownership/undo state per target, and the existing refusal on foreign edits or unsafe paths. Tests should preserve each profile's default model, unrelated providers/settings and unselected profiles, including refresh/disable after a profile is removed or renamed. The reported Windows paths should be exercised as fixtures without changing a running Hermes installation.
Background refresh is tracked separately by #7704 / Draft #7719; discovering profiles and granting unattended writes are separate steps. Leaving this report open until the selected-profile behavior is verified and lands.
feat(integrations): connect named Hermes profiles (#7674) (#7700)
lidge-jun commentedon Oct 25, 2026
Fixed on dev by #7700 (merge commit 6fc3c88).