v2.1.0

MossInfer 2.1.0 adds features on top of 2.0 and keeps its interfaces: ABI 1, server protocol 2. Builds and applications written for 2.0 run unchanged.

New

• Edit adapters (reference images). Edit adapters such as chinoll/Moss-Image-Edit load with --lora and edit up to four reference images (--reference). On a bf16 DiT the adapter is merged on the GPU at load, about 1 s. On INT8, INT4 and NVFP4 it runs as a side branch. moss-infer quantize --lora bakes it into an INT8 file. Runs at an 8 GiB VRAM budget.
• GGUF DiT files. Community GGUF DiTs (Q8_0, Q6_K, Q5_K, Q5_1, Q5_0, Q4_K, Q4_1, Q4_0, BF16, F16, F32) load as dit_file. They are converted once into INT8 ConvRot, or into bf16 for tier reference, and kept in cache_dir. Their speed and VRAM are those of the format they run as.
• Component API. Run the pipeline step by step from your own sampler loop: text encoding, run setup, single denoise steps with host or engine guidance, latent batches, VAE encode/decode. It is in the C library and in moss-server (over shared memory). With the same inputs the steps reproduce mi_generate bit for bit. See docs/c-api.md and docs/server-protocol.md.
• Check before running. mi_check(), the server's check method and moss-infer check plan a request without loading weights. They report whether it fits, the plan and an estimate of the time.
• Runtime LoRA placement. --lora-placement default|merge|side_branch. bf16 merges now run on the GPU.

Faster

• INT8 high: 3.2 % less time per step at 1024² and 4.8 % less at 2048² on an RTX 5090, with bit-identical images. INT8 + 8-bit attention now takes 0.186 s per step at 1024², 2.5× the bf16 reference. It is 1.13× faster per step than ComfyUI's INT8 at 1024² and 1.08× faster at 2048².
• LoRA side branch on INT8: a rank-16 LoRA costs about 5 % per step, down from 8.7 %.

Hardened

• Windows file handling. User paths, cache entries and output files go through handles that refuse pipes, devices and links leading outside their folder. Files are published by rename.
• Model files replaced while the engine runs load anew at the next generate, or fail cleanly with the file named.

Compatibility

• mi_generate output is bit-identical to 2.0.0, and its speed is unchanged or faster. Measured on an RTX 5090 over 16 paired processes per configuration.
• New capability bits: MI_CAP_COMPONENTS, MI_CAP_REFERENCE_IMAGES, MI_CAP_CHECK. New server capability: components.