Authorization notice. Hatoba is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA sysadmin or solo operator with several Linux servers who wants a quick health view before starting work.
The problemChecking each server one by one over SSH takes time, and installing monitoring agents on every machine is not always allowed.
The outcomeA dashboard of cards or a table showing the status of each saved host, read over SSH.
What you need first
- A computer running Windows, Linux, or macOS (Windows is the maintainer's main platform)
- Rust stable, Node.js 22 or later, and pnpm for building from source
- WebView2 on Windows, Xcode Command Line Tools on macOS, or the Tauri system dependencies such as libwebkit2gtk-4.1-dev on Linux
- SSH access to at least one host, with a password or key
- A Cloudflare account for optional sync (the free plan usually covers personal use)
- An API key from an OpenAI-compatible or Anthropic provider for the AI assistant
Steps
- Import your existing hosts from ~/.ssh/config, or add them in the Hosts view with groups and tags.
- Confirm each host's authentication method, such as a key in the Key vault or ssh-agent.
- Open the Dashboard and switch between the card and table views.
- Click a host to open a terminal session if a metric looks wrong.
Prompt for your agent
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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page