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

How to iterate on a plugin without restarting the host with Rutis

Edit a TypeScript plugin and see the running host reload it on every file change.

Who it is forA developer or coding agent building a connection to an API, model or tool, who needs quick feedback without restarting a long-running program.

The problemEach change to an integration usually means stopping and restarting the whole program, which slows iteration and risks leftover connections.

The outcomeA plugin project that runs under a host which reloads it whenever its files change, with configuration updates applied live.

What you need first

  • Node.js with npm, or Bun, for the TypeScript path
  • uv for the Python path
  • Go for the Go path
  • A Rust toolchain with cargo for the embedding path

Steps

  1. Run npx @arcships/rutis-host new weather --lang node to create the plugin project.
  2. Run cd weather && npm install to install dependencies.
  3. Run npx rutis-host dev and edit the plugin file; the host reloads it when files change.

Prompt for your agent

Using the repo arcships/rutis, create a TypeScript plugin named <target> with `npx @arcships/rutis-host new <target> --lang node`, install it, and start it with `npx rutis-host dev`. Expected output: the host running the plugin and logging a reload after you change a file. Verify that the reload happens without restarting the host process.

Caveat. The README shows this workflow for Node, Bun, Python and Go; check the language guide before relying on reload behavior for a specific runtime.

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