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

How to predict which rule handles one app and destination with Intent Route AI

Enter one process, destination, port, and protocol to see the rule that would match it.

Who it is forA user who has several overlapping rules and wants to confirm what happens to one specific application's connection before enabling a change.

The problemRule priority, order, and fallback make it hard to tell by inspection which action a given connection would get.

The outcomeA three-valued answer (proven match, proven global fallback, or indeterminate) with an evaluation trace showing the rules considered.

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. Open the AI Route Simulator page in IntentRoute AI.
  2. Enter one exact process name, one concrete domain or literal IP address, one port, and TCP or UDP.
  3. Run the simulation and wait for the bounded background evaluation to finish.
  4. Read the result and the local evaluation trace, and open the proven matched rule if one is shown.
  5. Change the query or the configuration to test another case, noting that the old result is hidden after either changes.

Prompt for your agent

In the Vincent-Xi08/IntentRoute-AI repo, run the Route Decision Simulator for the process <process name>, destination <domain or IP>, port <port>, and protocol <TCP or UDP>. Expected output: a proven match, a proven fallback, or an indeterminate result with a trace. Verify that the simulator performed no DNS lookup, proxy probe, or configuration change.

Caveat. The README calls the simulator a static what-if tool that does not observe traffic, so its result describes configuration semantics, not what a live connection would actually do.

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