DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to share a running local model with your tailnet with Omarchy Local AI

Expose a running model to other devices on your Tailscale tailnet, still behind the gateway key.

Credentials. Anyone on your tailnet who has the gateway key can use the shared model, so give the key only to people you trust.

Who it is forA small team or a person with several devices on one tailnet who wants one machine to serve a local model to the others.

The problemA model running on one machine is only useful on that machine unless it can be reached from your other devices, and exposing it carelessly is risky.

The outcomeA running model is reachable on your tailnet through tailscale serve, still requiring the gateway key, and you can stop sharing from its page.

What you need first

  • Omarchy with the Quattro shell and its bar
  • Docker, jq, curl, flock, sha256sum and sha1sum installed
  • A supported GPU, or an x86-64 CPU with AVX2 and enough RAM for the recipe
  • Enough free RAM and disk for the model you pick, as the panel lists them
  • Your Omarchy password for setup, since setup runs Omarchy's Sudoless Docker command, which is root-equivalent

Steps

  1. Make sure Tailscale is running and logged in, and that your account is Tailscale's operator (Omarchy's Tailscale install sets this).
  2. Start a model from the models tab so it is running.
  3. On the running model's page, click share to share it on your tailnet.
  4. To remove the share, click **Stop sharing** on the model's page.

Prompt for your agent

Using the repo 0xSero/omarchy-local-ai, share the running model <model-name> on the tailnet and confirm the share is active. Expected output: the model's page shows it as shared and another device on the tailnet can reach it with the gateway key. Verify by checking that the share is listed on the model's page, then stop sharing and confirm it is removed.

Caveat. Sharing needs Tailscale running and logged in with the right operator, and if another account is the operator you must ask that account to manage sharing.

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