hermes-agent

mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-07-25 17:18:11 +00:00

History

Rain bc7212cf93 feat(moa): per-reference-model max_tokens override MoA reference_max_tokens is preset-level — one cap for all reference models. When mixing a verbose model with a terse one, a single cap is either too tight for the terse model or too loose for the verbose one. Now each reference slot can optionally carry its own max_tokens: reference_models: - provider: openrouter model: deepseek/deepseek-v4-pro max_tokens: *** # per-slot cap, overrides preset-level - provider: openai-codex model: gpt-5.5 # no max_tokens → falls back to preset-level reference_max_tokens _clean_slot (moa_config.py) preserves an optional max_tokens field on the slot dict, coerced via _coerce_int_or_none. _run_reference (moa_loop.py) reads slot-level max_tokens first, falling back to the preset-level cap passed by the caller. Slots without the field are unaffected — backward compatible. Type hints on slot-handling functions updated from dict[str, str] to dict[str, Any] to reflect the now-heterogeneous slot shape.	2026-07-23 16:17:27 -07:00
..
emails	feat(moa): per-reference-model max_tokens override	2026-07-23 16:17:27 -07:00
README.md	fix(ci): make tests, workflows, and attribution reliable under load (#66373 )	2026-07-17 20:55:24 +00:00

Rain bc7212cf93 feat(moa): per-reference-model max_tokens override

MoA reference_max_tokens is preset-level — one cap for all reference
models. When mixing a verbose model with a terse one, a single cap is
either too tight for the terse model or too loose for the verbose one.

Now each reference slot can optionally carry its own max_tokens:

  reference_models:
    - provider: openrouter
      model: deepseek/deepseek-v4-pro
      max_tokens: ***        # per-slot cap, overrides preset-level
    - provider: openai-codex
      model: gpt-5.5
      # no max_tokens → falls back to preset-level reference_max_tokens

_clean_slot (moa_config.py) preserves an optional max_tokens field on
the slot dict, coerced via _coerce_int_or_none. _run_reference
(moa_loop.py) reads slot-level max_tokens first, falling back to the
preset-level cap passed by the caller. Slots without the field are
unaffected — backward compatible.

Type hints on slot-handling functions updated from dict[str, str] to
dict[str, Any] to reflect the now-heterogeneous slot shape.

2026-07-23 16:17:27 -07:00

emails

feat(moa): per-reference-model max_tokens override

2026-07-23 16:17:27 -07:00

README.md

fix(ci): make tests, workflows, and attribution reliable under load (#66373 )

2026-07-17 20:55:24 +00:00

README.md

This directory replaces appending entries to AUTHOR_MAP in scripts/release.py. The old dict caused constant merge conflicts when several salvage PRs landed at once — every PR edited the same lines of the same file. Here, each mapping is its own file, and file additions never conflict.

Adding a mapping

One file per commit-author email, under emails/:

python3 scripts/add_contributor.py <email> <github-login>
# or by hand:
echo "<github-login>" > contributors/emails/<email>

File name = the exact commit-author email (as shown by git log --format='%ae').
File content = the GitHub login on the first non-comment line. Lines starting with # are comments (use them for the PR reference).

Example — contributors/emails/jane.doe@example.com:

janedoe
# PR #12345 salvage (gateway: fix session key routing)

Rules

Do NOT add new entries to AUTHOR_MAP in scripts/release.py. That dict is frozen legacy data; the release tooling merges it with this directory (directory entries win on duplicates).
GitHub noreply emails (<id>+<login>@users.noreply.github.com and <login>@users.noreply.github.com) auto-resolve — no file needed.
The Contributor Attribution Check CI job fails a PR whose commits carry an unmapped email; the failure message prints the exact command to run.

README.md

Contributor email → GitHub login mappings

Adding a mapping

Rules