Unsloth’s latest beta lets local vision models see a computer screen and use a mouse and keyboard, bringing AI computer use to macOS, Windows and Linux. The feature is off by default, and the release adds integrations with game engines and creative apps including Unreal Engine, Unity, Godot and Blender.
Unsloth Watch analysis
What happened
The beta, version 0.1.918, adds computer use for GGUF, safetensors and MLX vision models, as well as connected providers. Users turn it on in Settings, then choose it from the chat composer. Unsloth says it asks before a chat’s first action, before entering each new app, and before risky steps such as using a terminal. Users can stop an action or take back control by moving the pointer to a screen corner.
The release also adds app connections through MCP, including Unreal Engine, Unity, Godot, Roblox and Figma. Figma access is read-only; Unsloth says the other tools can let a local model build scenes and games. The project describes a demo in which Qwen3.8-27B built a Pong game in Godot and a village square in Unreal Engine.
Other changes include MiniMax-H3-Image in GGUF and FP8 formats, a new model picker, and a rebuilt connections interface. Unsloth says a 2048-pixel MiniMax-H3-Image decode took 0.28 seconds on an A100 80GB, compared with 2.82 seconds previously. That is the project’s own result, not an independent benchmark.
Why it matters
This goes beyond adding another model to a menu: Unsloth is giving local models a route to operate desktop apps, with user confirmations and controls intended to keep the person at the keyboard. The game-engine links make the AI connection explicit: models can be used to build scenes and games, not merely run them faster.
The release also widens the range of hardware and workflows Unsloth is targeting, from Mac users running MLX models to people using AMD or CPU-based setups for image generation. It is a beta, and the performance figures come from Unsloth, but the practical ambition is clear: more AI work carried out on a user’s own machine.
Our read
Computer use is the standout change, particularly because it is off until enabled and includes confirmation steps and a way to interrupt the model. Those controls are a sensible starting point for software that can click and type across applications. They do not make every workflow safe by magic, so begin with tasks where a wrong click is an inconvenience, not a catastrophe.
What to watch
- How reliably computer use works across different operating systems and vision models.
- Whether the confirmation prompts and interruption controls hold up in real-world use.
- How well MCP connections work with the named apps beyond Unsloth’s demonstrations.
- Whether users reproduce the project’s image-generation speed claims on other hardware.
Discussion spark: Would you let a local AI model operate across your desktop with app-by-app confirmations, or should computer use stay confined to tightly limited tasks?
Sources and evidence
- Releases · unslothai/unsloth · GitHub (Publication date not supplied)
WittyWires independently tracks public Unsloth AI developments and is not affiliated with, endorsed by, or speaking for Unsloth AI, its maintainers, GitHub or X.