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

How to run Talorys locally to test changes without Cloudflare with Talorys

Start the agent, Pages proxy and UI on your machine with a mock AI provider.

Credentials. The local dev password defaults to talorys-dev-password, so set TALORYS_DEV_PASSWORD before exposing the dev server on any network.

Who it is forA developer who wants to modify Talorys or test a feature before deploying to Cloudflare.

The problemTesting a change against a live deployment is slow, and it spends real Cloudflare resources on every try.

The outcomeA local Talorys UI at http://localhost:5173 that you can edit and test with a deterministic mock AI provider.

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. Install Node.js 22 or newer.
  2. Run git clone https://github.com/rociiu/talorys.git and then cd talorys.
  3. Run npm install.
  4. Run npm run dev and open http://localhost:5173 in your browser.
  5. Sign in with talorys-dev-password, or the value of TALORYS_DEV_PASSWORD if you set it, and run npm test before you change anything.

Prompt for your agent

In the rociiu/talorys repo, run `npm install` and `npm run dev`, then open http://localhost:5173. Report whether the sign-in page loads and whether `npm test` passes. Verify that the app is running without a Cloudflare login.

Caveat. Local development uses the mock AI provider, so model replies are deterministic and do not reflect the live Workers AI model.

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