feat(providers): add Hermes to the Provider enum#9
Merged
Conversation
The backend added `hermes` to UserCapabilities.PROVIDER_CHOICES (MantisAPI #1807), so the SDK's Provider enum and MantisAPI's sdk_contract manifest no longer match it — the sdk-compatibility contract check fails on every MantisAPI PR until all three agree. Add `Provider.Hermes = "hermes"` so the SDK enum equals the backend's provider set again. Capability-gated like claude_code (opencode stays the only universal one), so the existing `_assert_available` gating covers it with no special-case. Bump 0.12.0 -> 0.13.0 (additive, backward compatible).
There was a problem hiding this comment.
Code Review
This pull request bumps the SDK version to 0.13.0 and adds a new agent-execution runtime provider, Hermes ("hermes"), to the Provider enum. There are no review comments to address, so no additional feedback is provided.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
Provider.Hermes = \"hermes\"to the SDK'sProviderenum.Why
The backend added a third agent-execution runtime provider,
hermes, toUserCapabilities.PROVIDER_CHOICESin MantisAPI #1807 ("HERMES ACP COMPOSER"). MantisAPI'ssdk-compatibilityCI check cross-checks three provider sets and fails if any disagree:UserCapabilities.PROVIDER_CHOICES→{opencode, claude_code, hermes}Providerenum →{opencode, claude_code}← behindsdk_contractmanifestSDK_PROVIDER_KEYS→{opencode, claude_code}← behindThe observed CI failure:
This PR fixes the SDK side.
hermesis capability-gated likeclaude_code(opencode remains the only universally-available provider), so the existingAgentsResource._assert_availablegating already covers it — no special-casing needed.Changes
Provider.Hermes = \"hermes\"inmantis_sdk/enums.py.0.12.0→0.13.0(additive, backward compatible) inpyproject.toml+__init__.py.Verification
Providerenum now equals the backend set exactly:{opencode, claude_code, hermes}.Follow-up (separate MantisAPI PR)
The
sdk_contractmanifest (SDK_PROVIDER_KEYSinsrc/sdk_contract/contract_manifest.py) also needshermesadded. Since the compat check installsMantis_SDK@main, this PR must merge first, then the manifest PR will go green.