NousResearch/hermes-agent

Fix inline comment parsing in .env config values

Cluster 76544 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

A bug where inline comments were incorrectly retained as part of unquoted .env values, causing broken base URLs and opaque 404 errors. The members cover the bug report and two proposed or applied fixes to the .env parser.

Open issues1

  • Issue#76544config: _parse_env_value keeps inline comments as part of .env values (broken base URLs, opaque 404)

Open PRs1

  • PR#77218fix(config): strip inline comments from unquoted .env values (#76544)

1 PR closed without merging

From the close comments: partial fix 1

  • #76545 fix(config): parse .env through pinned python-dotenv instead of hand-rolled parser (#76544) · partial fix → b4debdf, #76544, #76545, #77218, #1, #15803, #14532, #6, #9, #374151, #4338
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.67: 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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.