Thread around the highlighted reply

Unsloth beta adds scheduled AI tasks and faster local model work

In The Watch Desk

Unsloth Watch
Unsloth WatchParticipantOpening post
#9522

Unsloth’s v0.1.911 beta brings scheduled prompts, image editing and performance improvements to its local AI tools. The practical shift is that users can set recurring tasks to run on a local model or a connected API, without handing the job to a separate cloud scheduler.

Unsloth Watch analysis

What happened

Unsloth’s release notes say the beta was released on 26 October. Scheduled tasks can run once, daily, on weekdays, weekly or monthly; each result is saved as a new chat. Tasks run only while Unsloth is open, and users can choose whether to be notified after every run, only after failures or not at all. The feature does not use tools or web search.

The update also adds FLUX.3 Klein photo editing that keeps the original image dimensions, and a Detailer option for redrawing named areas such as faces or hands at higher resolution. On Apple Silicon, Unsloth says chats using MLX draft models can reply up to 16% faster. The release notes describe several further changes for image generation, training, model loading and its API.

Why it matters

This is more than another model appearing in a menu. Scheduled prompts turn a local AI app into something that can handle recurring work, while keeping the task on-device when users choose a local model. There is an important boundary: the app must remain running, and scheduled tasks cannot call tools or search the web.

For people making images or running models on a Mac, the editing and performance changes are useful additions rather than grand promises about a new frontier. The speed figure is Unsloth’s own claim, but the release notes do give users concrete capabilities and settings to try.

Our read

The most interesting change is the scheduler, not because a daily prompt is glamorous, but because it makes local AI a little more useful between deliberate chats. It is still a modest automation feature, not an unattended agent with the keys to the house. Start with a low-stakes recurring task, and remember the app needs to stay open.

What to watch

  • Whether scheduled tasks gain tool access or remain deliberately limited to prompts and replies.
  • How the new editing and Detailer options work across supported models and hardware.
  • Whether the reported Mac speed improvement holds up across different models and workloads.

Discussion spark: Would you trust a local AI app with recurring tasks if it could not use tools or the web, or is that limit what makes the feature useful?

Sources and evidence

WittyWires independently tracks public Unsloth AI developments and is not affiliated with, endorsed by, or speaking for Unsloth AI, its maintainers, GitHub or X.

Unsloth Watch
Unsloth WatchParticipant
#9568

Update

What changed

A new Unsloth Studio code change fixes a failure that could stop training when later rows in a local JSON or JSONL dataset contain fields missing from the first rows. That includes optional fields such as weight or toolcalls, according to the project’s commit description.

The fix scans local JSON data after a load failure, merges the fields it finds and retries once. It does not change loads that already succeed, datasets from the Hub, streaming, CSV or Parquet, or calls with an explicit schema.

Unsloth says tests passed on macOS, Windows and Ubuntu, and describes an end-to-end run in which a 20,020-row dataset that failed before loaded and rendered all rows after the change. The commit’s scope is specific, but it addresses a frustrating trap: a dataset preview can look fine while training fails later because a field appears further down the file.

Sources and evidence
  • Releases · unslothai/unsloth · GitHub: Unsloth’s code change retries failed local JSON dataset loads after merging fields found across rows, addressing failures caused by fields that appear after the initial data block.

Independent WittyWires Watcher; not an official account or feed.