Key points
- Kimi K3.1 Pro weights — Beyond model announcements, the supplied material, which has not yet been verified against primary sources, reports that Moonshot AI uploaded Kimi K3.1 Pro's weights to its moonshotai account on Hugging Face.
- trnrt inference — RunAnywhere's open-source inference engine, trnrt, runs GLM-5.3-Flash MoE on a single AWS trn2.48xlarge and provides an OpenAI-compatible API.
- Looped Transformers — The author used Nsight Compute to analyze a Huginn-style looped Transformer and check whether successive iterations could actually reuse the cache.
Your Daily AI Stew from Robin, on Salty Talk.
Today we start with new model capabilities, then look a layer deeper inside the machine: once weights are available, how do you get them running, and where does the time actually go?
Hunyuan Hy4
The relationship between the source digest’s date and this edition’s date has not been verified. Evidence of publication times, time zones, and collection times is still missing, so we do not use it to establish when these events occurred. The following summarizes an AIHOT daily report that has not yet been verified against primary sources: Tencent Hunyuan released the production version of Hy4, scaling up pretraining and post-training and adding visual understanding and computer use for the first time. For developers, the significance is that the model’s scope extends from text to images and interface interaction: it now has to handle more than a passage typed into a text box. Source: AIHOT daily report
The release and benchmark information in this item has not yet been verified against primary sources. The digest reports improvements of 19.1% on GameDev and 9.8% on GameLogic. The versions also need to be kept distinct: 770B total parameters, 49B active parameters, and a 1M context window refer to the Hy4 preview released earlier, on August 28. They should not be presented as new specifications for the production release.
The same digest reports that OpenAI introduced Images 2.6. Source: OpenAI official announcement OpenAI says generation is 50% faster, with the low-quality Flare tier taking as little as 6 seconds, and that this image capability is available across all tiers in ChatGPT and Codex. From interface interaction to image generation, these releases expand the capabilities developers can call on. The “as little as 6 seconds” figure applies to a specific quality tier; it cannot be generalized to the wait time for every image task. Source: AIHOT daily report
Kimi K3.1 Pro weights
Beyond model announcements, the supplied material, which has not yet been verified against primary sources, reports that Moonshot AI uploaded Kimi K3.1 Pro’s weights to its moonshotai account on Hugging Face. The following statements about the availability of the weights and the Pro version have not yet been verified against primary sources. According to that material, developers and businesses can now download and test the model and evaluate local deployment. The practical value of open weights is that they provide another way to inspect a model firsthand. Source: Hugging Face
The material describes it as the first open-weight, natively multimodal agent model in the K3.1 series, built from Kimi K3 through large-scale joint reinforcement learning during post-training across hundreds of downstream domains. It relays an official claim that this is currently the most capable model in the 3T class. That capability assessment remains an official claim. The material does not provide a complete model card or specify terms for commercial use and redistribution, so we keep the news to the availability of weights for testing, without adding deployment assurances.
trnrt inference
Once you have the weights, the next question is how to make them run more smoothly. The following summarizes the supplied engineering record; the source date is not used to establish when the events occurred. RunAnywhere’s open-source inference engine, trnrt, runs GLM-5.3-Flash MoE on a single AWS trn2.48xlarge and provides an OpenAI-compatible API. The model has 320 billion total parameters, activates 18 billion per step, and supports a context of 1 million tokens. Source: r/MachineLearning
What makes this engineering record interesting is its breakdown of inference time. In an early batch-1 KDA linear-attention half-layer, the recurrence itself accounted for only 2% of elapsed time, while mHC pre-projection accounted for 36% and XLA glue for 33%. Sparse models compute only a small number of experts at each step, but many small calls, layout conversions, memory round trips, and communication between chips can still consume the time.
The team rewrote each half-layer as an NKI megakernel and fused the entire sparse-attention layer. With the same layout, batch-8 decoding time per step fell from 32.2 milliseconds in the October 17 build to 24.2 milliseconds in the November 1 build. This shows that optimization can also focus on moving less data and crossing fewer kernel boundaries. These figures, however, reflect improvements within this Trainium2 implementation. The material provides no GPU comparison using the same trace; some choices in sparse-attention prefill also remain approximate, with no task-level evaluation yet. Source: r/MachineLearning
Looped Transformers
Following that thread of data movement, there is also a measurement on an NVIDIA B200. The author used Nsight Compute to analyze a Huginn-style looped Transformer and check whether successive iterations could actually reuse the cache. A looped architecture can share weights and increase effective depth, but sharing weights does not automatically mean each iteration can fetch them from on-chip memory. Source: r/MachineLearning
The experiment found a clear boundary: sharing one 72 MiB set of weights across eight matrix multiplications was 24% faster than storing eight identical copies, with almost no HBM reads. Once the weights grew to 288 MiB and exceeded L2 capacity, the performance difference disappeared. In an educational Huginn Core implementation with random weights, eight iterations also took roughly eight times as long and read roughly eight times as much HBM data as a single iteration.
This test separates two easily confused issues: storing fewer copies of model parameters and moving those parameters fewer times during execution are different things. Bandwidth savings depend on working-set size, cache capacity, and kernel scheduling. Reuse in the architecture must ultimately translate into reuse on the chip.
MaixStation
Moving from inside the chip back to the desktop, Sipeed has disclosed more specifications for MaixStation, its pocket-sized Linux AI workstation for local AI inference and development. It uses the Axera AX8860P, integrating a 16-core Arm CPU and an NPU rated at 256 TOPS in FP4, with up to 128GB of LPDDR5X memory. Source: r/LocalLLaMA
In light of the inference optimizations above, other details worth examining include its 273GB/s memory bandwidth, 10G SFP+ networking, and PCIe 5.0 expansion. For local development, compute, memory, and interfaces together determine the hardware available to run a model. A TOPS figure alone is not enough: FP4 here means a four-bit floating-point format, and the rated operation count cannot be converted directly into throughput or accuracy for a particular model.
Sipeed says it is working to open-source the AX8860 SDK and upstream the code. According to the supplied report, the announced target price is about $3,999, with crowdfunding planned for late 2026. Neither the target price nor the crowdfunding plan is a final retail price or launch date. What we can see for now is the machine’s specifications and the direction of its software work; the material provides no benchmarks. Source: r/LocalLLaMA
Taken together, today’s stories connect model capabilities, open weights, inference kernels, and local hardware into a chain from release to execution. According to the unverified material discussed above, Hy4 expands input and interaction capabilities, while Kimi provides access to downloadable weights. The trnrt and B200 tests draw attention to memory and execution details. By the time we reach local devices such as MaixStation, the questions become concrete: what can the model do, how can its weights be used, how does the data move, and how well can the machine actually run it?
🎧 This episode is also available as a podcast: listen to Daily AI Stew · 2026-11-04.