Cairn

Bedrock regional client not reinitialized on model switch

NousResearch/hermes-agent · cluster 41296 · agent

Data as of

Nothing open on GitHub. Fix merged in #107658. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #107658. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where switching models mid-session to Bedrock fails to initialize or preserve the regional runtime client, causing ValidationException errors for regional inference profiles. Multiple fix attempts address client initialization and regional runtime preservation during model switches.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #107658 Bedrock Claude and Converse models survive /model, fallback and restore (one runtime binder for all wires)

    merged to main

    files: agent/agent_init.py, agent/agent_runtime_helpers.py, agent/bedrock_adapter.py, agent/client_lifecycle.py, hermes_cli/runtime_provider_backends.py, tests/run_agent/test_switch_model_bedrock_sigv4.py

4 PRs closed without merging

From the close comments: closed without comment 2 · done elsewhere 1 · other 1

  • #41322 fix(bedrock): preserve regional runtime on model switch · other
  • #65433 fix(bedrock): preserve regional runtime on model switch · closed without comment
  • #67948 fix(agent): initialize Bedrock clients on model switch · closed without comment
  • #67970 fix(agent): initialize Bedrock clients on model switch · done elsewhere → 942973a, #107658, #41296
Closed issues · 1
  • Closed#41296[Bug]: Mid-session /model switch to Bedrock never sets _bedrock_region — regional inference profiles (jp.*/eu.*/apac.*) fail with ValidationException "The provided model identifier is invalid"
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Merged PRs
#107658
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
11 Sep 2026

For your agent

The same facts, typed.

cluster/41296.json
cluster/41296.md