NousResearch/hermes-agent

Camofox auth token key name mismatch fix

Cluster 77088 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These items concern a bug where the wrong environment variable name (CAMOFOX_API_KEY instead of CAMOFOX_ACCESS_KEY) was being sent as the Bearer token, causing 401 errors on all Camofox browser routes. The members cover the bug report and related fix attempts.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · stale or abandoned 1

  • #77108 fix(browser): use CAMOFOX_ACCESS_KEY as the global Camofox auth token (#77088) · stale or abandoned
  • #77119 fix(browser): use Camofox access key for route auth · closed without comment
Closed issues · 1
  • Closed#77088[Bug]: Camofox backend sends CAMOFOX_API_KEY as global Bearer token, but the server gates all routes with CAMOFOX_ACCESS_KEY → 401 on every browser call
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
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.