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

How to deploy a private personal AI agent in one command with Talorys

Install Talorys into your own Cloudflare account and sign in from any device.

Credentials. The installer asks for your owner password and may use a Cloudflare API token, so keep both out of shared logs and chat transcripts.

Who it is forA solo user who wants a personal AI assistant that stores data in their own Cloudflare account, not a vendor's server.

The problemHosted assistants keep your chats, memories and tasks on someone else's servers, and setting up your own is usually a manual project.

The outcomeA working Talorys site at a pages.dev address that only you can sign into with your owner password.

What you need first

  • Node.js 22 or newer
  • A Cloudflare account, with browser login or an API token that has the listed permissions
  • A password you choose for the owner account
  • A terminal on your computer

Steps

  1. Confirm Node.js 22 or newer is installed.
  2. Run npx create-talorys@latest in the folder where you want the talorys/ directory created.
  3. Log in to Cloudflare in the browser page the installer opens, choose your account and an agent name.
  4. Enter an owner password when asked. The installer stores only a hash of it as a Cloudflare secret.
  5. Open the https://….pages.dev URL the installer prints, enter your password and start chatting.

Prompt for your agent

In the rociiu/talorys repo, run `npx create-talorys@latest` in <target-folder> and follow the prompts for the Cloudflare account and owner password. Report the pages.dev URL the installer prints. Verify by opening that URL and confirming the password screen loads.

Caveat. The installer creates the resources in your Cloudflare account, and Workers AI calls may use part of the free daily allocation, which Cloudflare can change.

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