Skip to content

fix(ai): starting the AI stacklet tells you what it is doing - #76

Merged
arthware-dev merged 3 commits into
mainfrom
fix/ai-stacklet-startup
Sep 10, 2026
Merged

arthware-dev merged 3 commits into
mainfrom
fix/ai-stacklet-startup

Conversation

@arthware-dev

Copy link
Copy Markdown
Contributor

Two ways stack up ai misled you.

Starting without voice waited out a full timeout for the TTS container and
another for Whisper, then reported both as broken, when they were never
started because that is what was asked for. A manifest can now mark a check
as belonging to an optional part.

And if oMLX disappeared after setup (a Python upgrade breaking its
virtualenv, a brew cleanup, a new Mac), nothing noticed: containers started,
the command reported success, and the only sign was a health check failing
with no cause. Starting now stops and says what is missing.

Starting the AI stacklet without voice waited out a full timeout for the
TTS container and another for Whisper, then reported both as broken. They
were never started, because that is what was asked for. Four minutes of
the startup spent on a question nobody posed.

A manifest can now mark a check as belonging to an optional part.
Setup installs oMLX once and records that it is done, so the install step
never runs again. If the engine later disappears -- a Python upgrade that
breaks its virtualenv, a brew cleanup, a new Mac -- nothing noticed.
Containers started, the command reported success, and the only sign was a
failing health check that named no cause.

Starting now stops with what is missing and how to reinstall it.
They cover the compose profile, but the new guard means on_start now
also refuses a managed provider with no oMLX installed. That made them
pass on a machine with the engine and fail on one without, which is
exactly the difference between a developer Mac and CI.
@arthware-dev
arthware-dev merged commit 9dbba4a into main Sep 10, 2026
1 check passed
@arthware-dev
arthware-dev deleted the fix/ai-stacklet-startup branch September 22, 2026 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant