v2.7.0 — Export Profiles
v2.7.0
This is an app release.
Summary
v2.7.0 adds Export Profiles for model profile metadata.
Users can now export their MLX Server Manager model profiles to a JSON file for backup or migration preparation.
This release implements export only. Import Profiles remains future work.
Added
- Added
Export Profiles...action in the Models sidebar - Added JSON export for model profile metadata
- Added export privacy summary
- Added export success / cancel / failure messages
- Added export logging
- Added
ModelProfileExportService - Updated README and docs for Export Profiles status
Exported JSON
The exported JSON includes:
schemaVersionappexportedAtprofiles- profile
name - profile
modelID - profile
host - profile
port - non-empty Advanced Launch Options
Not Exported
Exported profiles do not include:
- API keys
- tokens
- secrets
- executable paths
- local model paths
- model weights
- model caches
- logs
- PID
- memory metrics
- readiness results
- runtime process state
- selected current target state
- adopted external server state
Safety Boundary
Export Profiles is side-effect-free.
It does not:
- start servers
- stop servers
- restart servers
- adopt external servers
- forget external servers
- call
/v1/models - make external HTTP requests
- change process ownership
- proxy inference requests
Direct Mode Boundary
Direct Mode remains unchanged:
OpenAI-compatible client -> mlx_lm.server or adopted external server -> MLX model
MLX Server Manager does not proxy inference requests, act as a chat UI, download models, delete models, or become a multi-backend wrapper.
Import Status
Import Profiles is not implemented in this release.
Future import work should include:
- import preview
- schema validation
- profile validation
- conflict handling
- skip / rename / replace options
- no automatic server start
Build
Unsigned macOS app build:
MLXServerManager-v2.7.0-unsigned.zip
SHA-256:
8877aa7912585e733b9b26cc642a3a7a8e09abddae0ca402f0a7d868cef777f6