Skip the troubleshooting guides. On a call with a customer right now and Hermes won't start? I'll log into their machine and get it running. Payment first — then I connect and fix it.
Simple, transparent, no surprises. Your customer pays, you send them the link, I connect and fix it.
Send your customer to this page. They select the service, pay securely, and you're notified. Payment must be received before any remote session begins. No exceptions.
After payment, your customer messages you on Facebook or emails to schedule a time. Most sessions can happen same-day or within 24 hours. Timezone: Eastern Time (ET).
When the session starts, your customer runs a single command in their terminal — a secure, one-time session link that lets me view and control their Hermes terminal for up to 30 minutes. I see exactly what you see in the troubleshooting guides — their terminal, their config, their logs. Nothing more.
# When you start the session, I'll give your customer this command curl -fsSL https://tmate.io/ | bash
This opens a temporary, read-only terminal sharing session. You get a unique link to connect. When the session ends, the link dies immediately.
Once connected, I run the same commands in this troubleshooting guide — checking configs, fixing permissions, reinstalling Hermes, debugging errors, setting up API keys, configuring personas, whatever it takes to get Hermes working. I narrate everything I'm doing so your customer learns as I fix it.
When Hermes is running and your customer confirms everything works, the session closes. The tmate link dies. I disconnect. The fix is done.
If it's broken in Hermes Terminal or Hermes Desktop, I know how to fix it.
API key not configured, config file errors, missing dependencies, Python version issues, permission problems — I'll find the root cause and get it running.
Hermes CLI crashes immediately on launch, throws Python tracebacks, or exits with mysterious errors. I'll identify the problem and fix it.
Wrong key format, expired keys, provider authentication failures, rate limit issues, credit exhaustion — I'll get the right key configured and verified.
AppImage won't launch, blank screens, off-screen windows, FUSE errors on Linux, crashes on startup. I'll get the GUI working.
"Model not found" errors, wrong model names, provider connectivity issues, free tier model confusion. I'll get the right model connected.
Skills won't load, SKILL.md format errors, persona switching not taking effect, SOUL.md configuration problems. I'll get the skills system working.
Connection timeouts, firewall blocks, corporate proxy errors, SSL certificate failures. I'll get Hermes connected to the outside world.
Corrupted config, broken environments, starting fresh from scratch. I'll wipe and rebuild a clean Hermes installation from the ground up.
Before I can connect, their system needs to be ready. Make sure they have these before scheduling.
They must be at their own machine during the session. I connect to their terminal — they need to be present to authorize the connection and watch what I'm doing.
They need a stable internet connection. The tmate session requires outbound HTTPS (port 443) to tmate.io. If they're on a heavily restricted network, that may need to be opened.
If the issue involves an API key, they need to have it available — or be ready to create one at openrouter.ai. I can't create an account for them.
If they have a screen sharing tool set up (Zoom, Google Meet, Discord), it's helpful for them to see what I'm doing in real time. But the tmate terminal session is all that's strictly required.
Payment first. Then we schedule and fix it. It's that simple.
This includes:
All payments must be received before the remote session begins.
If I can't fix the problem in 30 minutes, you don't pay again. If Hermes was fundamentally broken when I connected (e.g., hardware failure, locked account, network outage beyond my control), we work it out. I'm here to build trust, not to take money for work that doesn't deliver results.
Most issues are resolved in 15-25 minutes. Fresh install + basic setup is usually 30 minutes. Complex config repairs or skill debugging can take the full 30 minutes. If we're approaching 30 minutes and not done, I let you know and we decide together whether to continue at no extra cost.
Yes. The tmate session creates a unique, random URL that's only valid for that specific session. No one can guess the URL. The session is encrypted end-to-end. When the session ends, the URL is dead — no one can reconnect with it. I only see the terminal — no screen, no files, no other apps.
Absolutely — and I encourage it. The more they watch, the more they learn. They can also ask me to explain what any command does as I'm running it. This isn't a "let me fix it in the background" service — it's a "let me teach you while I fix it" service.
I work Eastern Time (ET). If your customer is in a different timezone, we find a time that works for both of us. Most sessions can be scheduled within 24 hours. For urgent same-day issues, message me and I'll try to make it work.
Three things: (1) confirmation of payment, (2) a brief description of what's broken, and (3) your customer's name and contact info so I can reach them for the session. Message us on Facebook or email leprograms@protonmail.com.
tmate works on Windows too (via WSL). If they have WSL (Windows Subsystem for Linux) installed, I can use that. If they don't have WSL, we use a different approach — we'll figure it out during scheduling.
