Cairn

Keep llama-server API key out of argv and logs

NousResearch/hermes-agent · cluster 137804 · hermes cli

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These members all concern the local runtime supervisor exposing the llama-server API key, via command-line arguments and the plain-text llama-server.log. Three are fix-titled changes proposing to pass the key by file or otherwise keep it off argv and out of the log, and one is an issue reporting the logging.

Open issues1

  • Issue#137804Local runtime supervisor logs llama-server API key in plain text (llama-server.log)

Open PRs3

  • PR#137808fix(local_runtime): hand llama-server its api key by file, not argv
  • PR#137812fix(security): keep the llama-server API key out of argv and the spawn log
  • PR#137813fix(local-runtime): keep the llama-server API key off argv and out of its log
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
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/137804.json
cluster/137804.md