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

How to run a local OpenAI-style LLM server on AMD with Kyojin

Serve a 95 GB Qwen model on one 128 GB AMD mini PC through an OpenAI-compatible API on port 8000.

Authorization notice. Kyojin is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer or small team that wants to point existing OpenAI API client code at a model hosted on their own AMD Strix Halo machine instead of a cloud service.

The problemCloud model APIs send data off the machine and bill per request, and most large models do not fit on a single consumer box.

The outcomeA local server on port 8000 that answers OpenAI API requests using a 300B-class MoE model class on one machine.

What you need first

  • AMD Ryzen AI Max+ 395 mini PC with 128 GB of memory (Strix Halo, gfx1151)
  • ROCm build of torch, installed per doc/install.md
  • Python and the hf command-line tool to download model packs
  • Roughly 100 GB of free disk space for a model pack (Qwen pack is 95 GB)

Steps

  1. Install ROCm torch and build Kyojin once by following doc/install.md.
  2. git clone https://github.com/Yamz-Labs/kyojin && cd kyojin
  3. hf download yamz-labs/Qwen3.8-Flash-Next-EXL3-Yamz --local-dir ./qwen-pack
  4. python tools/qwen/serve.py --model ./qwen-pack --port 8000 -c 131072
  5. Point your OpenAI API client at port 8000 on the machine and send a test chat request.

Prompt for your agent

In the Yamz-Labs/kyojin repo, follow doc/install.md, then download the Qwen3.8-Flash-Next pack and start tools/qwen/serve.py on port 8000 on <target host>. Expected output: the server starts and answers one OpenAI API chat request with text. Verify that the response JSON includes a choices array before reporting success.

Caveat. The README says the software targets AMD Strix Halo with ROCm (gfx1151), so it will not run on other hardware as documented.

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