hermes - 💡(How to fix) Fix [Feature]: Add new keys via the Dashboard [1 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#14641Fetched 2026-04-24 06:15:45
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Problem or Use Case

The dashboard currently has some editing capability (e.g. adding cron jobs, toggle skills) which are great for non-technical users.

But currently only pre-set keys (from the .env file) can be edited, it is not possible to add new ones.

Proposed Solution

Make it possible to add new API keys in the .env file from the Dashboard interface "Keys" tab.

Alternatives Considered

No response

Feature Type

New tool

Scope

None

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

extent analysis

TL;DR

To add new API keys, modify the dashboard interface "Keys" tab to allow users to input and save new keys to the .env file.

Guidance

  • Identify the current implementation of the "Keys" tab and determine how it retrieves and updates the pre-set keys from the .env file.
  • Design a user interface to input new API keys, considering security and validation measures to ensure only valid keys are added.
  • Develop a backend mechanism to securely update the .env file with the new API keys, potentially using environment variable management libraries or APIs.
  • Consider implementing access controls and permissions to restrict who can add new API keys.

Example

No code example is provided due to the lack of specific technical details in the issue.

Notes

The solution may require careful consideration of security implications, such as validating user input and ensuring the .env file is not exposed to unauthorized access.

Recommendation

Apply a workaround by modifying the existing "Keys" tab to allow users to add new API keys, as this is a new feature request rather than a bug fix that would be addressed by an upgrade.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING