HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled
Jev Laya Verified
2026-09-22

GitHub · Runtime ports · Games and demos

mizorewww/laya-mlx

The fastest local run on an Apple laptop, benchmark caveats included.

The repository's GitHub card, read on 2026-09-24

What it does

Runs Laya's weights natively on Apple Silicon through MLX with the same three question types, the same formatting and the same calibration as upstream, and ships its own converted weights. A Snake demo calls the model for every move so the speed claim has something to watch.

The repository's own description: “Native MLX runtime for Laya typed decision models — 7–14 ms short decisions on M3 Max. No text generation, PyTorch, or cloud API.”

How it works

The encoder and the decision heads load through MLX and stay on the Metal GPU; the package exposes one predict call that takes the state and the questions together. The demo puts a visible safety layer between the model's proposal and the move, so the game measures the loop rather than the model alone.

The repository, by the numbers

Stars
6,109
Licence
Apache-2.0
Stack
Python · MLX · Apple Silicon
Last push
2026-09-22

Read from the GitHub API on 2026-09-24. Stars and the last push move daily — quote them with the date, the way we do.

What we checked

  • the README and its benchmark table, read 2026-09-24
  • the caption separating the one-question latency number from the Snake frame time
  • the licence file

What we did not check. The 7.4 ms and 13.4 ms medians. They are the author's, measured on an M3 Max, and no row in this column can be compared to another row's latency because nobody measured on the same machine.

Open the repository ↗All builds

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →