# AI use cases for Hermes Console (xP3ta/hermes-console) Repo: [xP3ta/hermes-console](https://github.com/xP3ta/hermes-console) | Use cases: 4 | Page: https://dedupedai.com/use-cases/xp3ta-hermes-console/ Console is a free, self-hosted Android app that connects directly to your Hermes Agent Dashboard to chat with the agent, manage its jobs, and reach your machine over SSH. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Connect your Android phone to your own Hermes agent: https://dedupedai.com/use-cases/xp3ta-hermes-console/connect-phone-to-self-hosted-hermes/ - Follow the agent's work and cron jobs from your phone: https://dedupedai.com/use-cases/xp3ta-hermes-console/watch-agent-work-and-cron-from-phone/ - Close the old Gateway port left open by a previous setup: https://dedupedai.com/use-cases/xp3ta-hermes-console/close-old-gateway-network-exposure/ - Get back into Console after losing the Dashboard password: https://dedupedai.com/use-cases/xp3ta-hermes-console/recover-access-after-forgotten-password/ ## How to connect your Android phone to your own Hermes agent with Hermes Console Repo: [xP3ta/hermes-console](https://github.com/xP3ta/hermes-console) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Run one setup command on your computer, then scan a code in Console to reach your agent from your phone. **Who it is for:** A person who runs Hermes Agent on a home computer or server and wants its chat on their Android phone, with no extra account. **The problem:** Hermes runs on a machine you own, but there is no simple way to reach it from a phone without setting up pairing codes, a gateway or API keys. **The outcome:** The phone is connected to the Hermes Dashboard, and you can chat with the agent from Console. ### Steps 1. On the computer where Hermes lives, paste `curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-dashboard-setup.sh | sh` into Terminal (Linux, macOS), or `& ([scriptblock]::Create((irm https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-dashboard-setup.ps1)))` into PowerShell (Windows). 2. When the command finishes, note the address, username, password and QR code it shows. 3. Open Console and tap I already have Hermes, then scan the QR code. 4. Without a camera, tap Connect manually and type the address, username and password. 5. Optional check: on the phone, open the Dashboard address on port 9119 in a browser and confirm the sign-in page appears. ### Prompt to paste into your agent ```text For the repo xP3ta/hermes-console, run the Dashboard setup command from the xP3ta/hermes-setup README on and report the address, username and QR code it prints. Verify that http://:9119 returns the Dashboard sign-in page before telling the user to connect Console. ``` ### Caveat Console only reaches a Dashboard on a private address such as your home network or Tailscale, so a server on the open internet needs Tailscale or equivalent protection first. Risk, remote script: The setup command downloads a script from the internet and runs it with sh or PowerShell, so read it before running it on a machine you care about. Risk, credentials: The command prints a Dashboard password and a QR code that grants access, so do not share the screen or the code with anyone else. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xp3ta-hermes-console/connect-phone-to-self-hosted-hermes/ ## How to follow the agent's work and cron jobs from your phone with Hermes Console Repo: [xP3ta/hermes-console](https://github.com/xP3ta/hermes-console) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README See the reasoning, tools and tasks behind each reply, and check scheduled jobs, while away from your desk. **Who it is for:** A person who has Hermes running scheduled work and wants to check on what the agent did from their phone. **The problem:** An agent working on a computer gives little visibility from elsewhere, so you cannot tell what it did or whether its scheduled jobs ran. **The outcome:** You can read the agent's reasoning, tool use and tasks in the chat, and review cron jobs on a board or a list. ### Steps 1. Connect Console to your Hermes Dashboard, if you have not already. 2. Open the chat and read the reasoning, tools and tasks the agent shows in plain words. 3. Open the cron jobs and tasks view and switch between the board and the list to find the job you want. 4. Check the status of the job and the work it produced before deciding on the next step. ### Prompt to paste into your agent ```text Using the xP3ta/hermes-console app, connect to the Dashboard at and list the cron jobs and tasks shown in the app. Expected output: a short list of job names with their status. Verify that the list matches what the Dashboard shows in a browser. ``` ### Caveat The app needs a working Dashboard connection, so these views are only available while your Hermes computer is on and reachable from the phone. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xp3ta-hermes-console/watch-agent-work-and-cron-from-phone/ ## How to close the old Gateway port left open by a previous setup with Hermes Console Repo: [xP3ta/hermes-console](https://github.com/xP3ta/hermes-console) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Remove the network exposure from an older helper so only the Dashboard stays reachable from your phone. **Who it is for:** A person who installed Hermes with an older setup helper, uses Console 1.3 on all phones, and wants to stop the Gateway from listening on the network. **The problem:** An older helper saved an API_SERVER_KEY and opened port 8642 on your network, which is more exposure than Console needs. **The outcome:** The Gateway no longer listens on your network, Console still connects through the Dashboard, and the old key is kept unless you choose to remove it. ### Steps 1. Update every phone that uses Console to version 1.3 or newer, because the cleanup is meant to run only after that. 2. On the computer, run `curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-dashboard-setup.sh | sh -s -- --retire-gateway-exposure`, or the PowerShell form with `-RetireGatewayExposure` from the README. 3. Keep the API_SERVER_KEY, or add `--also-remove-api-key` to the command if you want it removed too. 4. Optional: if you do not use Hermes' API server for anything else, delete the API_SERVER_KEY line from `~/.hermes/.env` and restart the Gateway with `hermes gateway restart`. 5. Open Console and confirm it still connects to your Dashboard. ### Prompt to paste into your agent ```text In the xP3ta/hermes-console setup, run the retire-gateway-exposure option from the xP3ta/hermes-setup helper on , keeping the API_SERVER_KEY. Expected output: a message that the Gateway exposure was undone. Verify that Console on every phone still connects to the Dashboard before removing anything else. ``` ### Caveat Run the cleanup only after every phone uses Console 1.3, because the README warns that older versions still depend on the Gateway. Risk, remote script: This cleanup downloads and runs a script from the internet, so check the script first and run it only on the machine that hosts Hermes. Risk, credentials: Deleting the API_SERVER_KEY stops Hermes' API server from starting, which can break other tools that use that key. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xp3ta-hermes-console/close-old-gateway-network-exposure/ ## How to get back into Console after losing the Dashboard password with Hermes Console Repo: [xP3ta/hermes-console](https://github.com/xP3ta/hermes-console) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Generate a new Dashboard password, which also ends old sessions, and reconnect Console with it. **Who it is for:** A person who set up Console earlier and can no longer sign in to the Dashboard because the password is lost. **The problem:** Without the Dashboard password, Console cannot sign in, and the old password cannot be recovered from the phone. **The outcome:** You have a new Dashboard password, the old sessions are ended, and Console is connected again. ### Steps 1. On the computer where Hermes lives, run `curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-dashboard-setup.sh | sh -s -- --new-access` in Terminal, or the PowerShell form with `-NewAccess` from the README. 2. Note the new access details the command shows. 3. Open Console and find the new access under Get access back. 4. Sign in with the new details and confirm the chat loads. ### Prompt to paste into your agent ```text For the xP3ta/hermes-console setup, run the new-access option of the xP3ta/hermes-setup Dashboard helper on . Expected output: a new username and password for the Dashboard. Verify that the Dashboard sign-in page accepts the new password at http://:9119 before reporting success. ``` ### Caveat Running the new-access command ends the old sessions, so any other device signed in to the Dashboard will need the new password too. Risk, credentials: The new password is printed on screen, so keep it private and do not paste it into chats or shared notes. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xp3ta-hermes-console/recover-access-after-forgotten-password/