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

How to draft routing rules with a loopback-only model with Intent Route AI

Use a locally installed Ollama model so the intent stays on 127.0.0.1 instead of going to OpenAI.

Who it is forA privacy-minded Windows user who wants AI-assisted routing drafts but does not want the intent sent to a cloud provider.

The problemCloud drafting sends the typed intent and rule schema to OpenAI, which some users will not accept for their routing setup.

The outcomeA routing rule draft generated by a local model, validated the same way, and added disabled for your review.

What you need first

  • A Windows machine where the IntentRoute AI release can run
  • A sing-box v1.13+ installation that the app can start as its external TUN process
  • An OpenAI API key for cloud drafts, or Ollama installed with a local model for loopback-only drafts
  • Proxy details for any rule that routes traffic through a proxy

Steps

  1. Install Ollama and start its local service.
  2. Run ollama pull qwen3:8b to install the model separately.
  3. In IntentRoute AI, select Ollama (local) and choose the installed model from the list shown in the app.
  4. Enter your intent, request a draft, and review each field before accepting it as disabled rules.
  5. Open the Settings page and run the provider health check to confirm the model is reachable and installed.

Prompt for your agent

In the Vincent-Xi08/IntentRoute-AI repo, configure the Ollama provider with the model <model name> and generate a draft for the intent <intent text>. Expected output: a disabled rule draft and a health report showing loopback reachability and that the model is installed. Verify that the app only queries 127.0.0.1 or ::1.

Caveat. The README says the privacy and behavior of the installed model and runtime remain the user's responsibility, even though the app keeps requests on loopback.

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