Breaking

Fuga Fixes Scheduled Starts That Kept Running on Boot-Time Tool Detection

September 16, 2026 at 15:06 EDT

Software Dev & Coding
AI Agents

The most recent code change in Fuga's last day is four lines long and fixes a class of bug that every desktop agent application with a scheduler will eventually meet: a subscription registered at boot keeps calling the function it captured at boot, long after the application has learned things that function needed to know.

2026-09-17 · FUGA · LOCAL DEVELOPMENT

A subscription installed at boot kept starting sessions as if it were still boot

Scheduled session starts were running against the start function captured before command-line tool detection had resolved. A single indirection through a ref now hands each fire the current one.

The order of events that produced the bug

BOOT

The renderer registers one inter-process listener for scheduled starts

→

LATER

Command-line tool detection and catalog resolution finish, and the start function is rebuilt

→

SCHEDULED FIRE

The listener still calls the version it closed over at registration time

→

AFTER THE FIX

The listener reads a ref whose value is kept pointed at the current start function

BEFORE

Captured once, used forever

Every scheduled run inherited the boot-time view of which agent tools existed and what the catalog contained.

AFTER

Captured once, resolved late

The listener stays registered once, but the function it calls is looked up at the moment the schedule fires.

WHY AGENT APPLICATIONS HIT THIS

The cheap thing registers first; the expensive facts arrive later.

Detecting installed command-line agents and resolving a model catalog are asynchronous start-up work
A message listener is cheap, so it is installed early and intentionally never replaced
The failure is silent: the scheduled run launches, it just behaves as though the app had only just started

THE RIGHT CONTAINER

A pointer to the newest function belongs in a mutable ref: nothing about it is rendered, and updating it must not schedule a re-render.

THE HONEST CAVEAT

The assignment happens in the component body on every render, which the framework guidance advises against; the supported alternative has its own constraints for long-lived subscriptions.

Continue reading

The rest of this article is for AI News Blitz readers. Choose an option below to keep reading.