How to Use the Hermes Webapp with DeepSeek (November 2026)
By Cameron Voss and West Mao · Updated
TL;DREnable the Hermes Webapp on your local gateway, start a DeepSeek conversation in the terminal and reopen that same session in your browser. The Webapp opens the workspace, while the Web Dashboard manages the installation.
Which Hermes interface should you open?
Use the Webapp to continue a DeepSeek session in a browser. It brings the Desktop workspace to the browser through your Hermes Gateway. Use the Web Dashboard for management tasks such as checking configuration, models and profiles. The Dashboard has its own chat view, so seeing a chat box alone does not identify the interface. Webapp support was introduced in the November 5, 2026 Hearth release, v0.23.0.
| Interface | How to open it | Use it for |
|---|---|---|
| Webapp | hermes webappDefault local port 9120 | Working in the browser with the gateway’s sessions and workspace. |
| Web Dashboard | hermes dashboardDefault local port 9119 | Managing profiles, model settings, API keys and the installation. |
| Native Desktop | Open the installed Hermes Desktop app. | Using the workspace in a desktop application. See the Hermes Desktop setup guide. |
How do you turn on the Webapp on your computer?
Enable the Webapp for the Hermes profile you use, restart its running local gateway, then open it with the CLI. Check that your build recognizes hermes webapp before changing any settings. The documented default listen address is 127.0.0.1 on port 9120.
hermes --version
hermes webapp --help
hermes config set webapp.enabled true
hermes gateway restart
hermes webapp
Run these on the Hermes host and keep its default local bind for this walkthrough. If there is no running gateway to restart, the Webapp command can start it. On first launch it can take time to build the browser bundle. When the command opens or prints a one-use sign-in link, open it promptly and keep it private. If it expires, rerun hermes webapp for a fresh link.
How do you continue the same DeepSeek chat in your browser?
Start a normal interactive CLI chat and open that session from the Webapp’s session list. Both clients need to connect to the same gateway and use the same Hermes profile. For the direct DeepSeek API, the provider’s example uses deepseek-v4-pro. Start with the DeepSeek connection guide if your profile needs setup.
- In the terminal, run
hermes chatand confirm the provider and model in that session. Send “My test label is Cedar-42. Reply with only that label.” - In the Webapp, select the matching profile and find the existing conversation. Check that the terminal messages are already visible before typing anything.
- In that conversation, ask “What was the test label? Reply only with the label.” A reply of
Cedar-42plus the visible prior messages is the expected result for this check.
If historic messages are visible but the new turn fails, you have established that session continuity works. Check the model connection for that turn separately.
Why does the Webapp open without my chat?
Check the gateway and profile first. One computer can have separate Hermes installations in Windows and WSL, and a desktop client may be configured to use a gateway on another machine. Opening a Webapp against a different gateway can give you a working workspace with a different session list.
| What you see | What to check |
|---|---|
| The browser opened a settings dashboard | Confirm you used hermes webapp and check the port against the Webapp’s configured listener. |
| The sign-in link failed | Open a fresh link from hermes webapp. Local one-use links expire after 60 seconds. |
| The browser cannot reach the workspace | Run hermes webapp --status. Check whether the gateway is serving it and whether the configured port is in use. |
| The workspace opens with the wrong history | Check the machine, gateway and profile against the terminal session, then reopen the existing thread. |
Common questions
Does the Webapp read a separate copy of my DeepSeek configuration?
Chats run through the gateway for the chosen profile. Verify the provider and model in the session you open, especially after switching profiles or gateways.
Can I open the local address from another device?
The default loopback address works only on the Hermes host. For access from another device, use Hermes Desktop’s Web Access setup and its sign-in flow. Avoid forwarding the Webapp port directly from your router.