hermes-omp-acp
Use Hermes Agent with Oh My Pi (OMP) as its model backend through native ACP.
Hermes sends model requests to omp acp, and OMP handles inference with its configured models and credentials.
Requirements
- Hermes Agent 0.21.4 or later (release
v2026.9.21). - OMP 15.0.0 or later, with
ompon the Hermes process'sPATHand a configured model. - Python matching Hermes: 3.11–3.13 for Hermes 0.21.4; 3.14 for Hermes 0.22.x.
Quick start
1. Install and enable the plugin
Install and enable the plugin with Hermes:
hermes plugins install junghoon-vans/hermes-omp-acp
hermes plugins enable omp-acp-provider
Run both commands for the Hermes profile that should load the plugin. For a named profile, prefix the commands with hermes -p <profile>.
omp-acp-provider is the plugin ID used for installation and activation. omp-acp is the model provider ID used in model settings and --provider; do not replace it with the plugin ID.
2. Select a model
In that profile's config.yaml, merge the following settings into your existing configuration:
model:
provider: omp-acp
default: openai-codex/gpt-6.1-sol
base_url: acp://omp
api_mode: chat_completions
Replace the example model with a provider/model ID available to your OMP account. acp://omp identifies the subprocess backend; it is not a network endpoint.
An explicitly requested model must be selected successfully in the ACP session before the task runs. An unavailable model, failed selection, or returned model mismatch raises an error instead of running on OMP's default model.
3. Send a request
hermes chat --provider omp-acp --model openai-codex/gpt-6.1-sol \
--oneshot -q 'Reply with exactly OMP_OK. Do not use tools.'
For a running Hermes gateway, restart it after updating the configuration.
Python package installation
From the repository root, install the package into the same Python environment that runs Hermes:
python -m pip install .
The distribution is named hermes-omp-acp and exposes the hermes_agent.plugins entry point omp-acp-provider. Use the same activation command from step 1 after installing it. This package route is an alternative to Hermes's source installation command.
When a release is available on PyPI, install it into that same environment with:
python -m pip install hermes-omp-acp
Install Hermes and OMP separately; this package does not install either.
Configuration
| Environment variable | Default | Purpose |
|---|---|---|
HERMES_OMP_ACP_COMMAND |
omp |
Override the executable, for example with an absolute path. |
HERMES_OMP_ACP_ARGS |
acp |
Replace the complete argument list; parsed with shell-style quoting. Include acp when overriding. |
These variables must be available to the Hermes process, including a gateway launched as a service.
Official delegation model routes
To choose an OMP model per subagent task, use the official Advanced Delegation plugin, which requires Hermes 0.22.5 or later. Install and enable both plugins in the profile that delegates:
hermes plugins install advanced-delegation
hermes plugins enable advanced-delegation
The omp-acp-provider installation and activation steps above are also required. Merge this separate delegation configuration into that profile's config.yaml:
delegation:
backend: model_map
backends:
model_map:
options:
- name: omp-deep
description: Complex code analysis and implementation.
provider: omp-acp
model: openai-codex/gpt-6.1-sol
default: omp-deep
Replace model with an OMP model ID available to your account. Start a new Hermes session after changing routes.
Do not copy base_url: acp://omp from the main-model example into a delegation route. Hermes's delegation resolver treats an explicit base_url as a custom endpoint; use provider: omp-acp and let the provider resolve its executable and arguments.
This routes Hermes subagents to OMP models. The provider does not manage retained OMP sessions or worktrees; each completion starts a new ACP session. Route-level reasoning_effort and service_tier are not mapped to OMP settings by this provider.
Documentation
Development
See CONTRIBUTING.md for development setup, tests, builds, and publishing guidance.
The Python package is hermes_omp_acp, its distribution is hermes-omp-acp, the Hermes plugin ID is omp-acp-provider, and the model-provider ID is omp-acp.
License
MIT. Hermes and OMP remain subject to their own licenses.
Metadata
Release files for hermes-omp-acp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hermes_omp_acp-0.1.0.tar.gz | 17.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hermes_omp_acp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.6 kB
Release files / hermes_omp_acp-0.1.0.tar.gz
| Download URL | hermes_omp_acp-0.1.0.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e6321a84e6e3e3dd3e2b1ea299e3336d72ce3044b1dfe388d2295a7c1655a6a
|
|
BLAKE2b-256 checksum How to use checksums |
25cf5afb8032d45a10c7351a91e266760f41e909a737c4dacfb1e448936f9357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logRelease files / hermes_omp_acp-0.1.0-py3-none-any.whl
| Download URL | hermes_omp_acp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14a0e1ac6f10919b58f270c695c426132958ec0eaa3f201fd295a4c034290eea
|
|
BLAKE2b-256 checksum How to use checksums |
5be488e76844e9601029c138295696621a5e3e125050be877c4fa528b23d47ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for hermes-omp-acp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for hermes_omp_acp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.