Fix API Key Paste Issues During Hermes Setup
Resolve issues where API keys won't paste during Hermes setup on WSL, Termux, or non-standard terminals.
When setting up Hermes on WSL, Termux, or web-based terminals, API keys may appear not to paste. This is usually a Python getpass limitation — the key IS being entered, it's just hidden. If that doesn't work, adding the key directly to .env bypasses the issue entirely.
Managed cloud · API costs included · Skill library · Cancel anytime
Before you start:
- ☑Hermes Agent installer running
- ☑Your API key ready to paste
- ☑Access to ~/.hermes/.env file
Steps
- 1
Understand the behavior
API key prompts use Python getpass which hides input for security — your paste IS working, it just doesn't show
- 2
Try pasting anyway
Paste the key and press Enter — it should work even though nothing appears on screen
- 3
Add key directly to .env
If paste still fails, add your key directly to ~/.hermes/.env: OPENROUTER_API_KEY=sk-or-...
- 4
Restart Hermes
Hermes will pick up the key from .env automatically on next start
Pro Tips
- 💡The hidden input is a security feature, just like sudo password prompts — paste and press Enter even though you see nothing
- 💡On Termux, you may need to grant clipboard permissions to the terminal app
- 💡Revoke and regenerate any API key you've accidentally exposed in screenshots or logs
Troubleshooting
❌ Nothing appears when pasting API key
✅ This is expected behavior with getpass. Paste the key and press Enter — it's working even though you can't see it.
❌ Key rejected after pasting
✅ Check for trailing spaces or URL-encoding artifacts (%3D instead of =). Copy the raw key from your provider dashboard and add it directly to ~/.hermes/.env
❌ Paste doesn't work at all on Termux
✅ Add the key manually: echo 'OPENROUTER_API_KEY=your-key-here' >> ~/.hermes/.env