PR #23182: fix: reload default model from config.yaml on /reset and /new

• Repository: NousResearch/hermes-agent
• Author: Burgunthy
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/23182

Description (problem / solution / changelog)

Summary

Fixes #23131

• new_session() in cli.py now re-reads the default model from config.yaml when _model_is_default is True
• Explicit model choices via -m flag are preserved (won't be overridden)
• Picks up mid-session config.yaml changes on /reset and /new

Root Cause

The model was loaded once in __init__ and never re-read on session reset. Users who changed models mid-session (e.g. /model gpt-5) or updated config.yaml between sessions would not see their config default restored.

Changes

• cli.py: Added model reload from fresh load_cli_config() in new_session() when _model_is_default is True
• tests/cli/test_cli_new_session.py: Added 2 regression tests:
  • test_reset_reloads_default_model_from_config — verifies config default is restored
  • test_reset_preserves_explicit_model — verifies explicit -m choices are kept

Test plan

• All 8 tests in test_cli_new_session.py pass
• Manual: set model.default: openrouter/auto in config.yaml, run hermes, change model with /model, run /reset → should revert to openrouter/auto
• Manual: run hermes -m anthropic/claude-haiku-4-5-20251001, run /reset → model should stay claude-haiku-4-5-20251001

🤖 Generated with Claude Code

Changed files

• cli.py (modified, +10/-0)
• tests/cli/test_cli_new_session.py (modified, +62/-0)

---

PR #23262: fix(cli): reload configured default model on new session

• Repository: NousResearch/hermes-agent
• Author: LeonSGP43
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/23262

Description (problem / solution / changelog)

What does this PR do?

This fixes #23131 with a narrow bugfix that keeps the affected path aligned with the current Hermes behavior without widening the change surface.

Related Issue

Fixes #23131

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• reload model.default / model.model from config when /new or session resets rebuild the CLI session state
• add a regression test that proves a configured default model overrides the transient startup model after new_session()
• Files: cli.py, tests/cli/test_cli_new_session.py

How to Test

1. Run uv run --frozen pytest -q -o addopts='' tests/cli/test_cli_new_session.py -k reloads_default_model_from_config
2. Run uv run --frozen ruff check cli.py tests/cli/test_cli_new_session.py
3. Confirm the affected workflow in #23131 now follows the expected behavior.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

<!-- Not applicable. -->

Screenshots / Logs

New-session model reload regression test and Ruff checks passed locally on macOS.

Changed files

• cli.py (modified, +18/-0)
• tests/cli/test_cli_new_session.py (modified, +19/-0)

---

PR #23342: fix(cli): reload default model from config on /reset and /new

• Repository: NousResearch/hermes-agent
• Author: mehmetkr-31
• State: closed | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/23342

Description (problem / solution / changelog)

When a user switched models mid-session via /model, subsequent /reset or /new commands continued using the switched model instead of reverting to the config.yaml default. This reloads the default only when the original session was started without an explicit -m CLI override.

Closes #23131

Changed files

• cli.py (modified, +15/-0)
• scripts/release.py (modified, +1/-0)