Who it is forA developer who already uses Claude Code and wants its requests answered by a model running on their own Strix Halo machine.
The problemClaude Code needs a Messages API endpoint, and the developer wants that endpoint served from local hardware.
The outcomeClaude Code sends its Messages API calls to the halogen server and receives answers from the local model.
What you need first
- An AMD Strix Halo machine (the README measures on a Ryzen AI Max+ 395 with 128 GB)
- Podman installed, with access to /dev/kfd and /dev/dri
- Access to the BIOS to set the UMA frame buffer carve-out to its minimum
- Disk space for the model weights, which the container downloads on first run
- Network access to ghcr.io and the model download source
Steps
- Set the BIOS carve-out (UMA frame buffer) to its minimum, as described in docs/host-setup.md.
- Run
mkdir -p ~/halogen-models - Run
podman run --rm -p 8731:8731 --device /dev/kfd --device /dev/dri --group-add keep-groups --ipc=host --ulimit memlock=-1:-1 -e HALOGEN_DOWNLOAD=peonist-ai/halogen-qwen3.8-flash-next -v ~/halogen-models:/models ghcr.io/peonist-ai/halogen-flash-server:0.18.12(inferred, check the README) - Follow docs/claude-code.md to direct Claude Code to the Messages API on the server.
- Send one small request as a test and confirm the reply, using docs/api.md for the expected responses.
Prompt for your agent
Using the repo peonist-ai/halogen-flash-server, configure Claude Code on <target machine> to use the local halogen server on port 8731, following docs/claude-code.md. Expected output: a short Claude Code prompt returns a reply from the local model. Verify the server is listening on port 8731 before you test.
Caveat. The README describes Claude Code support through the Messages API, but the exact client setup lives in docs/claude-code.md, which this summary does not reproduce.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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