Local AI Cat module
MLXServe sidecar
Current shipping, testing, and product context for this part of Local AI Cat.
Status
Where it stands
- Platforms
- macOS
- Release channels
- Alpha · Beta · Main
- Distribution
- Outdoor
- AlphamacOS
- BetamacOS
- Outdoor · Direct downloadmacOS
Description
What it does
macOS Outdoor/Beta only. FeatureMLXServeSidecar owns configuration, settings reads, model/cache path resolution, subprocess launch/supervision, health polling, model discovery, log rotation, status state, and lazy startup/termination participants. The app injects only main-Bundle resolution for Contents/Resources/mlxserve/mlxserve-http and AppLog forwarding. The new focused package was chosen instead of folding the operationally independent subprocess into the embedded MLXServe module. FEATURE_MLXSERVE_SIDECAR still bundles mlxserve-http plus mlx.metallib only when MLXSERVE_BINARY_DIR is supplied; missing artifacts still report binary not bundled. The sidecar remains the same default-off second listener on port 11435, points at the same LLM and WhisperKit roots, and leaves legacy :11434 untouched. Its settings remain in exactly the same visible position inside the existing `.localAPI` UIContribution; no separate sidecar row or gate was introduced. The A/B phase deliberately permits double-loading because the sidecar process and app runtime pool are separate until serving unification.
Headless Local API
Drive it over the loopback API
Logging / observability: provisional grade L0 — structured=0 print=0 sentry=0.
- discover
- not applicable
- execute
- present
- observe
- not applicable
- configure
- not applicable
- cancel/stop
- not applicable
- reset
- not applicable
/v1/local/app/action/v1/local/app/artifacts/{id}/v1/local/app/navigate/v1/local/app/screenshot/v1/local/app/state/v1/local/app/surfaces/v1/local/app/transactions/{id}/v1/local/artifacts/v1/local/artifacts/{artifact_id}/v1/local/artifacts/{artifact_id}/content
Media
See it in action
Backlog / improvements
What comes next
No improvements are listed for this module yet.
History
How it got here
No change history has been published for this module yet.

