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

How to deploy an actor to Cloudflare Workers with Tardigrade

Test an actor locally with wrangler, then deploy it to Cloudflare.

Credentials. Model and Cloudflare credentials must be configured for deployment, so keep them in your secret store and out of the repo.

Who it is forA developer who wants a hosted agent that runs on Cloudflare with a directory of threads.

The problemTurning an agent prototype into a running hosted service requires routing, per-thread storage and deployment config.

The outcomeA deployed Worker where ActorDO routes requests and each ThreadDO keeps its own database.

What you need first

  • Bun installed, since the README uses bunx and bun add
  • Working knowledge of TypeScript
  • A model and credentials configured for the generated project
  • A Cloudflare account for Cloudflare hosting, or a Celld fleet with a storage bucket for self-hosting

Steps

  1. Generate the project with bunx tardie init meeseeks --template quickstart.
  2. Configure your model and credentials in the generated services file.
  3. Run bunx wrangler dev and follow the local setup guide to verify the actor responds.
  4. Run bunx wrangler deploy to publish the Worker to Cloudflare.

Prompt for your agent

Using the repo clavia-labs/tardigrade, generate a project with `bunx tardie init meeseeks --template quickstart`, add model credentials for <model-provider>, then run `bunx wrangler dev`. Expected output: a local Worker that serves the actor. Verify that both ActorObject and ThreadObject bindings are exported from the Worker entrypoint before deploying with `bunx wrangler deploy`.

Caveat. The README says to configure your model and credentials and points to the Cloudflare guide for details, so check that guide before deploying to production.

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