# NousResearch/hermes-agent · Alibaba provider API key env var naming fixes

## Open now

- 0 issues, 3 PRs open on GitHub.
- PR #9714: fix(alibaba): accept ALIBABA_API_KEY alias and correct missing-key hints
- PR #9749: fix(alibaba): accept both DASHSCOPE_API_KEY and ALIBABA_API_KEY env vars
- PR #10105: fix: show correct env var name in provider-not-configured error

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.

## TL;DR

- 10 member(s): 0 open issue(s), 1 closed issue(s), 3 open PR(s), 1 merged PR(s), 5 PR(s) closed without merging.
- A fix was merged to main in PR #10563. Verify it addresses your case.
- **Recommended:** read PR #10563 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-10563`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.20`: the share of member 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.

## Closed / duplicate issues

- #9506: \[Bug\]: \`alibaba\` provider error message shows wrong env var name (ALIBABA_API_KEY instead of DASHSCOPE_API_KEY)

## Prior & competing PRs

- **#9710: fix(alibaba): accept ALIBABA_API_KEY alias and correct missing-key hints**. closed without merge · fix tier `suggested`
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#9714`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#10563: fix: show correct env var name in provider API key error**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `run_agent.py`
- **#9511: fix: accept ALIBABA_API_KEY as fallback for alibaba provider**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#9523: fix: accept ALIBABA_API_KEY as fallback and fix error messages for alibaba provider**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`
- **#9714: fix(alibaba): accept ALIBABA_API_KEY alias and correct missing-key hints**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#10563`, `#9506`
  - files: `agent/auxiliary_client.py`, `hermes_cli/auth.py`, `hermes_cli/doctor.py`, `run_agent.py`, `tests/hermes_cli/test_api_key_providers.py`, `tests/hermes_cli/test_runtime_provider_resolution.py`
- **#9749: fix(alibaba): accept both DASHSCOPE_API_KEY and ALIBABA_API_KEY env vars**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`
  - files: `hermes_cli/auth.py`, `run_agent.py`
- **#9987: fix(provider): show DashScope env var for Alibaba**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#10105: fix: show correct env var name in provider-not-configured error**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `2918328009ca6ce556fdc3d7fcf8c0cc9a0a3972`, `#10563`
  - files: `agent/auxiliary_client.py`, `run_agent.py`, `tests/hermes_cli/test_runtime_provider_resolution.py`
- **#10557: fix(run_agent): use DASHSCOPE_API_KEY hint for alibaba provider**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#10563`, `#9506`

## Fix status

- Merged to main in PR #10563 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-15`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.
- Subsystem: `agent`