Cairn
NousResearch/hermes-agent

Deleting custom env keys leaves empty entries

Cluster 72552 · dashboard. Data as of

Nothing open on GitHub. Fix merged in #99310 on 31 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #99310. 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.

These members address a bug where clearing a custom environment variable key in the dashboard does not remove it, instead leaving an empty entry. The work involves allowing empty-value saves to trigger deletion and cleaning up removed keys from the env state.

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.

  • #99310 fix(credentials): removed API keys no longer resurrect across .env, auth.json, config.yaml, and the dashboard

    merged to main

    files: contributors/emails/[redacted:email], hermes_cli/config.py, hermes_cli/credential_lifecycle.py, hermes_cli/web_server.py, tests/hermes_cli/test_credential_lifecycle.py, tests/hermes_cli/test_env_export_line_lifecycle.py, tests/hermes_cli/test_model_assignment_env_key_mirror.py, web/src/lib/env-state.test.ts, web/src/lib/env-state.ts, web/src/pages/EnvPage.tsx

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #72568 fix(dashboard): remove deleted custom env keys · merged via another change → #99310, #72552
  • #73226 fix(dashboard): allow deleting custom keys from .env via empty-value save (#72552) · done elsewhere → #72552, #99310, #72568
Closed issues · 1
  • Closed#72552[Bug]: Dashboard cannot delete custom keys from .env; clearing leaves an empty entry
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.50: 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
dashboard
Merged PRs
#99310
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.

cluster/72552.json
cluster/72552.md