# AI use cases for Hatoba (scarletkc/Hatoba) Repo: [scarletkc/Hatoba](https://github.com/scarletkc/Hatoba) | Use cases: 4 | Page: https://dedupedai.com/use-cases/scarletkc-hatoba/ Hatoba is an open-source desktop SSH client with an AI assistant and end-to-end encrypted sync stored in your own Cloudflare account. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Build the Hatoba desktop app from source: https://dedupedai.com/use-cases/scarletkc-hatoba/build-hatoba-desktop-from-source/ - Sync SSH hosts and keys across devices, encrypted: https://dedupedai.com/use-cases/scarletkc-hatoba/sync-ssh-hosts-across-devices-encrypted/ - Watch every saved server's health on one page: https://dedupedai.com/use-cases/scarletkc-hatoba/monitor-all-servers-on-one-dashboard/ - Have an AI assistant diagnose a live SSH session: https://dedupedai.com/use-cases/scarletkc-hatoba/let-ai-assistant-diagnose-live-ssh-session/ ## How to build the Hatoba desktop app from source with Hatoba Repo: [scarletkc/Hatoba](https://github.com/scarletkc/Hatoba) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Compile and run the open-source SSH client on your own machine instead of using a release build. **Who it is for:** A developer who wants to audit, modify, or run the SSH client from its source code. **The problem:** Release binaries are not always what you want to run, and you may need to inspect or change the code before trusting it with your SSH keys. **The outcome:** A working development build of Hatoba on your machine, plus an installer or package you built yourself. ### Steps 1. Install Rust stable, Node.js 22 or later, and pnpm, plus the WebView2, Xcode Command Line Tools, or Tauri Linux dependencies for your system. 2. Clone https://github.com/scarletkc/Hatoba and open the folder in a terminal. 3. Run `pnpm install`. 4. Run `pnpm tauri dev` to start the app in development mode. 5. Run `pnpm tauri build --no-sign` to produce an installer without update signatures (on macOS, use the build command in the README that turns off update artifacts instead). ### Prompt to paste into your agent ```text Clone the scarletkc/Hatoba repo, run `pnpm install` and then `pnpm tauri dev` in the cloned folder, and report whether the app window opens. Verify that the Rust and Node.js versions meet the README requirements before starting. ``` ### Caveat The README says the Linux and macOS builds get little testing on real machines, so expect rough edges outside Windows. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. 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/scarletkc-hatoba/build-hatoba-desktop-from-source/ ## How to sync SSH hosts and keys across devices, encrypted with Hatoba Repo: [scarletkc/Hatoba](https://github.com/scarletkc/Hatoba) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Deploy a sync Worker and D1 database in your own Cloudflare account so every device shares one encrypted vault. **Who it is for:** An engineer with a laptop and a desktop who keeps the same servers and keys on both and does not want a third-party server holding the data. **The problem:** Keeping hosts, keys, and terminal sessions in step across devices by hand is error-prone, and most sync services hold readable copies of your data. **The outcome:** Your hosts, keys, and conversations sync between your devices, with only ciphertext stored in your Cloudflare account. ### Steps 1. Open the README section Set up sync and read the Deploy the sync Worker guide at workers/sync/README.md. 2. Choose a deployment path: deploy with one click from the browser, deploy with wrangler, or let Hatoba deploy with a Cloudflare API token. 3. On the first device, connect Hatoba using the Worker URL and the setup token you generated during deployment. 4. On each other device, connect using only the Worker URL and your master password. 5. Store the master password and recovery code safely, since lost data cannot be recovered without them. ### Prompt to paste into your agent ```text Read workers/sync/README.md in the scarletkc/Hatoba repo and list the deployment options and the exact connection steps for a first device and a second device. Verify that the output names the Worker URL, the setup token, and the master password, and that it does not invent any command not in the guide. ``` ### Caveat If you forget the master password and lose the recovery code, the README states your data cannot be recovered. Risk, credentials: The setup token and the master password unlock your vault, so store them in a password manager and never paste them into an AI agent prompt or a shared chat. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. 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/scarletkc-hatoba/sync-ssh-hosts-across-devices-encrypted/ ## How to watch every saved server's health on one page with Hatoba Repo: [scarletkc/Hatoba](https://github.com/scarletkc/Hatoba) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README See online status, CPU, memory, disks, and load for all saved hosts without installing anything on them. **Who it is for:** A sysadmin or solo operator with several Linux servers who wants a quick health view before starting work. **The problem:** Checking each server one by one over SSH takes time, and installing monitoring agents on every machine is not always allowed. **The outcome:** A dashboard of cards or a table showing the status of each saved host, read over SSH. ### Steps 1. Import your existing hosts from ~/.ssh/config, or add them in the Hosts view with groups and tags. 2. Confirm each host's authentication method, such as a key in the Key vault or ssh-agent. 3. Open the Dashboard and switch between the card and table views. 4. Click a host to open a terminal session if a metric looks wrong. ### Prompt to paste into your agent ```text In the scarletkc/Hatoba app, open the Dashboard after importing hosts from ~/.ssh/config, then list each saved host with its online status and CPU and memory readings. Verify that every saved host appears once and that no software was installed on the servers. ``` ### Caveat The README says the terminal status bar shows CPU, memory, and network for Linux servers, so the dashboard's full detail is most reliable on Linux hosts. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. 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/scarletkc-hatoba/monitor-all-servers-on-one-dashboard/ ## How to have an AI assistant diagnose a live SSH session with Hatoba Repo: [scarletkc/Hatoba](https://github.com/scarletkc/Hatoba) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Let a model read your terminal and run approved commands on a server, with control over each action. **Who it is for:** An engineer debugging a failing server who wants help reading logs and running checks without typing each command by hand. **The problem:** Tracing a fault across logs, processes, and config files takes many small steps, and copying output into a chat tool is slow and loses context. **The outcome:** The assistant reads the terminal, proposes or runs commands with your approval, and reports the likely cause. ### Steps 1. Add your OpenAI-compatible or Anthropic API key in Settings. 2. Open an SSH connection to the failing host and open the AI assistant panel beside the terminal. 3. Describe the problem, and choose Approve each action, Auto mode, or bypass mode based on how much control you want to keep. 4. Review every command the assistant proposes before it runs, and stop it if the output looks wrong. 5. Ask for a summary of the findings and the changes it made. ### Prompt to paste into your agent ```text In the scarletkc/Hatoba app, open an SSH session to , ask the AI assistant to find why is failing, and keep approval on for every action. Verify that the assistant lists each command it ran and that you approved each one before execution. ``` ### Caveat The README says the assistant sends the terminal screen with each message unless you turn that off, so clear sensitive output or disable that setting before debugging on a host with secrets visible. Risk, credentials: The assistant sends the screen, attachments, and tool results to the model provider, so host addresses, passwords, and keys on screen reach that provider. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. 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/scarletkc-hatoba/let-ai-assistant-diagnose-live-ssh-session/