Problem or Use Case
I'm trying to use Hermes with a Copilot subscription available through a Github Enterprise organization.
When using the native Copilot CLI (or the gh CLI) the user can select whether to ise the standard, open Github endpoint (github.com) or a custom one.
However, when configuring Hermes to use Copilot directly, thia option is not available and the standard endpoint is always used.
Proposed Solution
Add the capability to select, during Copilot model configuration, the API endpoint to use. The authentication flow does not change if the endpoint is changed to another Github instance. The base API URL should be saved in .env file aside the other Github credentials.
Alternatives Considered
I tried using the Copilot ACP approach with a Copilot instance already authenticated to the GHE endpoint, but it is much slower and the output, if some tools are used, seems broken.
Feature Type
Configuration option
Scope
Medium (few files, < 300 lines)
Contribution
Problem or Use Case
I'm trying to use Hermes with a Copilot subscription available through a Github Enterprise organization.
When using the native Copilot CLI (or the
ghCLI) the user can select whether to ise the standard, open Github endpoint (github.com) or a custom one.However, when configuring Hermes to use Copilot directly, thia option is not available and the standard endpoint is always used.
Proposed Solution
Add the capability to select, during Copilot model configuration, the API endpoint to use. The authentication flow does not change if the endpoint is changed to another Github instance. The base API URL should be saved in .env file aside the other Github credentials.
Alternatives Considered
I tried using the Copilot ACP approach with a Copilot instance already authenticated to the GHE endpoint, but it is much slower and the output, if some tools are used, seems broken.
Feature Type
Configuration option
Scope
Medium (few files, < 300 lines)
Contribution