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

How to create a routing rule from a running process with Intent Route AI

Pick a live process in the app and turn it into a routing rule in one step.

Who it is forA Windows user who sees an application already running and wants its traffic routed without looking up its executable path.

The problemFinding the exact executable path and PID for an application and writing the rule by hand takes time and invites mistakes.

The outcomeA new rule for the selected process, created through the normal configuration transaction and still subject to the usual enable step.

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 process-to-rule view in IntentRoute AI.
  2. Search by name or PID to find the running application.
  3. Select the process and create a rule from it with one click.
  4. Open the rule constraints editor to add any host, IP-CIDR, port, protocol, or note limits.
  5. Run Policy Intelligence to check the new rule for conflicts, then enable it if it is correct.

Prompt for your agent

Using the Vincent-Xi08/IntentRoute-AI repo, find the running process named <process name> and create a rule for it. Expected output: one new rule that shows the real executable path. Verify that the rule was added disabled and that the configuration was saved through the normal transaction.

Caveat. The README says the rule is created through the normal configuration transaction, but enabling it and starting the sing-box runtime remain separate steps that you control.

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