[cmunley1]

No description provided.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[cmunley1]

/claude review

[claude]

SHIP — no reliability concerns.

Two additive, backward-compatible config knobs on the Pydantic HermesAgentConfig. Defaults preserve existing behavior (chat_template_kwargs_enabled=True keeps the thinking-kwargs injection; api_key defaults to the prior "gym" sentinel when unset and env is empty). os is already imported; no async paths, verifier/scorer logic, or public API surface touched. The sibling Pydantic fields already carry Python-side defaults not mirrored in the exemplar YAML, so this follows the established pattern.

NOTE — api_key env fallback (app.py:293). self.config.api_key or os.environ.get("OPENAI_API_KEY", "gym") means a globally-set OPENAI_API_KEY (common in dev shells) is now forwarded as the credential to whatever base_url the model server resolves to. Harmless when that's the local Gym model server (key ignored), but it silently sends a real credential to an internal endpoint where the code previously always sent the inert "gym". Author's call — if the intent is only to override for external providers, gating on an explicit config value rather than the ambient env var would be tighter. Not a blocker.