copass-hermes-agents
Copass agent primitives for the Hermes API server (NousResearch hermes-agent), routed to LLMs via OpenRouter.
This package owns the Hermes-specific backend and the
CopassHermesAgent(BaseAgent) convenience subclass. Hermes itself runs
inside a per-(user, sandbox) Daytona sandbox; this client speaks
HTTP/SSE to the sandbox endpoint via httpx.AsyncClient.
Spike-locked posture (ADR 0008 Phase 1b)
- Stateless
/v1/chat/completionsonly. The full conversation history is sent inmessages[]on every turn — Hermes' on-disk session DB is unused. Authorization: Bearer <API_SERVER_KEY>on every call. The bearer is the per-sandbox caller-side key minted at provision time; it is NOT an LLM key.- Single OpenRouter credential-pool entry per sandbox (no rotation). Hermes resolves the OpenRouter key from process env at agent construction time.
- Model strings use the
hermes/<openrouter-model-id>shape; the backend strips thehermes/prefix before forwarding to Hermes.
Conversation metadata: speaker + participants
When auto_record=True (the default when window is supplied), the
agent constructs a CopassTurnRecorder that auto-populates the
envelope's typed metadata on every turn:
speaker— set from theauthorconstructor arg on assistant turns; falls back to"User"/"Assistant"from the role on user turns.participants— defaults to["User", author or "Assistant"]. The roster rides on every turn so downstream retrieval can resolve second-person pronouns.
agent = CopassHermesAgent(
identity="support",
system_prompt="You are helpful.",
sandbox_url=os.environ["HERMES_SANDBOX_URL"],
api_server_key=os.environ["HERMES_API_KEY"],
window=window,
author="agent:support-bot", # → speaker on every assistant turn
# participants auto-defaults to ["User", "agent:support-bot"]
)
If you need a richer roster (multi-party threads) or a logged-in user
identity, build a CopassTurnRecorder directly with participants=...
and user_speaker="Alice", then pass auto_record=False to the agent
and drive recording yourself. See
copass-context-agents for the recorder
surface and full envelope semantics.
Metadata
Release files for copass-hermes-agents 1.4.9
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 | Actions |
|---|---|---|---|---|
| copass_hermes_agents-1.4.9.tar.gz | 13.5 kB | With provenance | Details for copass_hermes_agents-1.4.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| copass_hermes_agents-1.4.9-py3-none-any.whl | Python 3 | none | any | Details for copass_hermes_agents-1.4.9-py3-none-any.whl |
Total release size: 26.2 kB
Release files / copass_hermes_agents-1.4.9.tar.gz
| Download URL | copass_hermes_agents-1.4.9.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
453b938d2e8a053f9fb7619249d2630279af1cdf97bf1715addb262beead4969
|
|
BLAKE2b-256 checksum How to use checksums |
a9b954f09596abc97072fe4effb93b6237dd86b13d166e333d54a8a5d4dfeabb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 5, 2026.
Transparency logRelease files / copass_hermes_agents-1.4.9-py3-none-any.whl
| Download URL | copass_hermes_agents-1.4.9-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a83426504729c2f1117d07172a082c9dbc017f96fd8bacce561e1de9534f9a2b
|
|
BLAKE2b-256 checksum How to use checksums |
68bf5e0ff50aa9e5f5bc45254fb331980b8b1a1e3cec6df7ac13f3ff789d7796
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 5, 2026.
Transparency logSecurity for copass-hermes-agents 1.4.9
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 copass_hermes_agents-1.4.9.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 Jun 5, 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.