Cairn
NousResearch/hermes-agent

Alibaba provider API key env var naming fixes

Cluster 9506 · agent. Data as of

3 open items. Fix merged in #10563 on 15 Apr 2026. Check it covers your case.

The short answer

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

Multiple fixes and a bug report addressing the Alibaba/DashScope provider's handling of ALIBABA_API_KEY and DASHSCOPE_API_KEY environment variables, including accepting both as valid inputs and correcting error messages that displayed the wrong variable name.

Open issues0

No open issues.

Open PRs3

  • PR#9714fix(alibaba): accept ALIBABA_API_KEY alias and correct missing-key hints
  • PR#9749fix(alibaba): accept both DASHSCOPE_API_KEY and ALIBABA_API_KEY env vars
  • PR#10105fix: show correct env var name in provider-not-configured error

Fixes on record

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

  • #10563 fix: show correct env var name in provider API key error

    merged to main

    files: run_agent.py

5 PRs closed without merging

From the close comments: closed without comment 2 · done elsewhere 1 · stale or abandoned 1 · superseded by another PR 1

  • #9511 fix: accept ALIBABA_API_KEY as fallback for alibaba provider · closed without comment
  • #9523 fix: accept ALIBABA_API_KEY as fallback and fix error messages for alibaba provider · stale or abandoned
  • #9710 fix(alibaba): accept ALIBABA_API_KEY alias and correct missing-key hints · superseded by another PR → #9714
  • #9987 fix(provider): show DashScope env var for Alibaba · closed without comment
  • #10557 fix(run_agent): use DASHSCOPE_API_KEY hint for alibaba provider · done elsewhere → #10563, #9506
Closed issues · 1
  • Closed#9506[Bug]: `alibaba` provider error message shows wrong env var name (ALIBABA_API_KEY instead of DASHSCOPE_API_KEY)
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.20: 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
#10563
Closed issues
1
Attempts
5 PRs closed without merging
Fix link checked
15 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/9506.json
cluster/9506.md