Release v2.1.5 · andrew-waters/orchard

Orchard v2.1.5

Containers can now be created with a chosen CPU and memory allocation, and both can be changed later from Edit Configuration (via the usual stop/recreate flow). Previously every container silently got the runtime defaults of 4 CPUs and 1 GB with no way to change them in the GUI (#73).
The AI Models section now recognises oMLX servers. oMLX serves the same OpenAI-style API on the same conventional port (8000) as mlx_lm.server, so it previously appeared as a generic "MLX Server"; it's now identified by the owned_by: omlx stamp in its models listing (#72).
Local model servers that require an API key (oMLX generates one at setup) are no longer invisible: they appear as a locked provider with a field to paste the key, which is then used for detection, model listing, the chat tester, and the container bridge (OPENAI_API_KEY).

Edit Configuration no longer drops the executable from the Command Override field: the form now shows the full command (sleep 3600, not just 3600), so saving doesn't corrupt the container's process configuration. Quoted arguments (sh -c "echo hi") now also survive the round-trip (#42).
Unchecking "Run in detached mode (background)" now does what it says: after the container starts, Orchard opens your preferred terminal attached to it. The toggle no longer appears in the Edit Configuration sheet, where recreation always happens in the background (#43).
Opening a container terminal in Terminal.app or iTerm2 no longer fails with "Not authorized to send Apple events" on notarized builds: the app now carries the com.apple.security.automation.apple-events entitlement and a usage description, so macOS shows the Automation consent prompt. If permission is denied, the error now points to System Settings → Privacy & Security → Automation instead of dumping the raw AppleScript error (#64).