Skip to content

v1.9.0 — Connection Settings Polish

Choose a tag to compare

View all tags
@acari-git acari-git released this 15 Jun 10:08
· 11 commits to main since this release
v1.9.0
6c4e00d

v1.9.0

Summary

v1.9.0 improves the Connection Settings UI and copy workflow.

This release adds a Current Target summary so users can clearly understand which server target they are configuring across Managed Server, External Server Detected, Adopted External Server, and Not Running states.

Added

  • Added Current Target summary to Connection Settings
  • Added Target Type display
  • Added ownership note display
  • Added readiness/status summary
  • Added Copy Base URL
  • Added Copy Model ID
  • Added Copy API Key Placeholder
  • Added Copy All Connection Settings
  • Added Copy Hermes Agent Config
  • Added Copy curl Readiness Check
  • Added ConnectionTargetSummary
  • Updated README and docs for the v1.9.0 Connection Settings polish

Target Types

Connection Settings now distinguishes:

  • Managed Server
  • External Server Detected
  • Adopted External Server
  • Not Running / Not Connected

For Not Running / Not Connected, the UI shows a preview-style state so users can see the selected configuration without confusing it for an active connection target.

Copy Actions

The Connection Settings UI now provides clearer copy actions for common client setup workflows:

  • Base URL
  • Model ID
  • API key placeholder
  • JSON config
  • Hermes Agent config
  • All connection settings
  • curl readiness check
  • OpenAI-compatible chat example

These are copy-only helpers. MLX Server Manager does not send inference requests.

Hermes Agent Config

The Hermes Agent config copy text includes:

  • Base URL
  • Model
  • API key placeholder
  • Direct Mode note
  • local server note
  • ownership note
  • Qwen thinking note where relevant

Readiness Check

The readiness copy action uses /v1/models.

MLX Server Manager does not use /v1/chat/completions for readiness or detection.

Direct Mode Boundary

Direct Mode remains unchanged:

OpenAI-compatible client -> mlx_lm.server or adopted external server -> MLX model

MLX Server Manager still does not proxy inference requests, act as a chat UI, or become a multi-backend wrapper.

Ownership Boundary

The existing ownership boundary remains unchanged.

External Server Detected and Adopted External Server are not app-managed processes.

MLX Server Manager does not:

  • take PID ownership of external servers
  • stop external servers
  • restart external servers
  • kill external servers
  • monitor external server memory
  • collect external server logs

Managed server lifecycle controls remain limited to processes started by MLX Server Manager.

Verification

  • Debug build succeeded
  • Release zip created
  • Connection Settings target summary added
  • Copy actions verified at build level
  • Stop / Restart safety unchanged
  • /v1/models remains the readiness endpoint
  • No inference proxy added
  • No chat UI added
  • No external process ownership added

Asset

MLXServerManager-v1.9.0-unsigned.zip

SHA-256:

8bf679d1252d444def26a95a1c1bcb31c42cc9c4fe2401afe79ec3e68d6b5696

Size: 351K

Assets 3
Loading