DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to sync SSH hosts and keys across devices, encrypted with Hatoba

Deploy a sync Worker and D1 database in your own Cloudflare account so every device shares one encrypted vault.

Authorization notice. Hatoba is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

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.

Who it is forAn 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 problemKeeping 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 outcomeYour hosts, keys, and conversations sync between your devices, with only ciphertext stored in your Cloudflare account.

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

  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 for your agent

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.

Share: 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