Skip to content

Orchard Release Notes

Andrew Waters · A native Swift macOS interface for Apple container, with container and image management, Compose projects, local Kubernetes, Linux machines and local AI tools.

CaskVirtualization & Containers 1.8K
Install command
brew install --cask orchard
30-day installs
315
#533 in App
1-year installs
2.4K
Last 365 days
Latest version
2.7.1
Download size
33MB
dmg
Release cadence
Weekly
2 releases in 30 days
  1. 2.7.1

    LatestPatch

    GitHub Release Added to Homebrew

    CompatibilitymacOS 26 or later

    Orchard v2.7.1

    Thank you for using Orchard, and for the bug reports, ideas and pull requests that keep making it better. If it's useful to you, please consider starring Orchard on GitHub. It takes a second and helps other people find it.

    Changes

    Added
    • On Apple container 1.7.1, Create Cluster has a Use local images option, on by default, which lets the nodes pull from the Mac's own image store (container cluster create --shared-image-store) (#173). An image built or pulled in Orchard then runs in the cluster without a registry or a copy. A cluster's detail says whether it can see the Mac's images; one that can't points to Recreate, since only a create can turn it on. Recreate keeps the choice.

    • Containers Orchard creates follow the [container.dns] defaults in container's config.toml (nameservers, search domains, options and domain), as container run does from container 1.7.1 (#173). A field set in Orchard wins, then [container.dns], then Orchard's chosen default domain, then container's [dns].domain. This covers the Run form, compose, sandboxes and model servers. Settings > General shows the defaults read-only next to the DNS Domain picker, and the Run form's empty domain choice names the domain it falls back to.

    • On Apple container 1.7.1, Create Cluster can size the workers apart from the control plane (#174). With workers, the resource fields say they size the control plane, and Size the workers under Advanced sets the CPUs and memory each worker gets (--workers count=<n>,cpus=<n>,memory=<size>). Left off, a worker gets container's single-node defaults: a quarter of the Mac's CPUs and memory, at least 2 CPUs and 2 GB. Recreate reads the sizes off the live workers, keeps a cluster made in a terminal with workers of several sizes as it is, and otherwise uses the sizes the cluster was created with. Below 1.7 only a plain count is sent, as before.

    • On Apple container 1.7.1, the Clusters tab reads what container stored for each cluster when it was created (container cluster ls --format json) (#174). The list and detail show the cluster's Kubernetes version, and the detail its creation date. Recreate takes the CNI and Kubernetes version from that record, so a cluster created outside Orchard recreates with its real settings, and falls back to what Orchard remembers for clusters made before 1.7. Those show a short note that container cluster ls doesn't list them; they can still be deleted. A cluster container has a record of but whose nodes are gone is listed with no nodes, so it can be recreated or deleted. If cluster ls fails, the tab works from the containers as before.

    • Settings > System shows the kernel against the one the installed container version recommends (#174). When an older version's kernel is still installed it shows both and offers Use Recommended Kernel. A custom kernel is shown as custom and isn't flagged.

    • Settings > System shows whether container's image snapshots and container file systems are backed up by Time Machine, and offers Leave Out of Backups when they are (#174). Both can be rebuilt by pulling the image or recreating the container, and container 1.7.1 leaves them out on new installs only. It sets the same exclusion as tmutil addexclusion, only when you choose it, and never touches named volumes. Nothing prompts for it, so putting the folders back in your backups is respected.

    Changed
    • Orchard now builds against Apple container 1.7.1 (containerization 0.54.0), up from 1.6.1 (containerization 0.53.0), and Install container installs 1.7.1 (#173).
    • Load Image is gone on Apple container 1.7.1, which removed container cluster load-image (#173); Use local images replaces it. On 1.6.x it works as before.
    • Orchard no longer stops, force stops or deletes a single cluster node, on any container version (#173). Acting on one node breaks the cluster's Kubernetes state, and container 1.7.1's CLI refuses it too. The detail header, context menus, multi-select cards, menu bar and Cmd+K leave those actions out for a node or turn them off with a note pointing to Clusters, and Stop All and the bulk stop and remove skip nodes and leave them out of their counts. Logs, terminals, stats and export still work on a node, and a cluster is still stopped or deleted from Clusters, including one made before container 1.6.1.
    • Orchard now uses compose 0.9.0, and takes the rules for a failed post_start or pre_stop hook from it rather than keeping its own copy (#130): whether the run stops or carries on, what a failure reports and how much of a hook's output is kept. Hooks behave and read exactly as before. The Compose tab offers the matching 0.9.0 plugin update.
    • The foot of the Compose tab shows the installed container compose version on its own, and links to its release on GitHub. A development build shows as the release it came after, marked (dev), and links to the commit it was built from.
    Fixed
    • Orchard no longer calls any vmlinux-* kernel the recommended one (#174). Someone still on the kernel container 1.6.1 installed was told they had the recommended kernel on 1.7.1.
    • In full screen the list and detail headers (search, filters, sort and the add buttons) are no longer hidden behind the toolbar (#167). They sit just below it while the window is full screen, and the windowed layout is unchanged.
    • Containers in a Compose project can reach each other by name (#130). Compose containers were created with a bare hostname, which container's DNS never matches, so a service could not find another as <container>.<domain>. They are now created under Orchard's default DNS domain (Settings > General > DNS Domain, else container's own default), as containers from the Run form are, with the same nameservers as before. The foot of the Compose tab shows it as Default domain, which opens Settings to change it, and says when container compose in a terminal would use another, since that reads only container's default from config.toml. Containers already running pick it up when they are next recreated.
    Security
    • Orchard now builds with swift-nio 2.105.0, swift-nio-extras 1.35.2 and swift-nio-http2 1.46.0, up from 2.97.1, 1.33.0 and 1.42.0, to pick up the SwiftNIO security fixes for unbounded HTTP/1 headers, a ByteBuffer overflow, CRLF injection in request URIs, a decompression ratio bypass and HTTP/2 request smuggling (#170). These libraries come in through Apple container and its dependencies; nothing Orchard calls changed.

    Installation

    Homebrew

    brew install orchard
    

    Already installed with Homebrew? Update with:

    brew upgrade orchard
    

    Download

    1. Download Orchard-2.7.1.dmg
    2. Open it and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Orchard also updates itself: when a new release is out, it offers the update in the app.

    Checksums

    System Requirements

  2. 2.6.1

    Patch

    OpenNavo editorial Added to Homebrew

    CompatibilitymacOS 26 or later

    Orchard 2.6.1 adds volume management for compose projects and a Volumes tab, plus fixes for container recreation, networking and container install.

    Orchard 2.6.1 was released on 2026-11-02. This update adds volume management for compose projects and a Volumes tab, plus fixes for container recreation, networking and container install.

    • Compose projects create and mount their named and anonymous volumes, with compose 0.8.0; a volume declared under volumes: is created as <project>_<key> or under its name:, and an external: true volume has to exist already.
    • Add a Volumes tab that shows each volume's size on disk, format, age, labels and the containers that mount it, with create and delete; delete is turned off while a volume is mounted.
    • Add Free Up Space to remove data nothing uses: images no container is made from, stopped containers and volumes no container mounts; Orchard checks again just before removing anything.
    • Run and Edit can mount a named volume or a tmpfs, and a volume's detail has Run Container.
    • Show Show in Finder and Copy Path for a compose project's compose file beside Up and Down.
    • Give containers DNS aliases on their network with Apple container 1.6.0 or later; with the DNS domain test, api makes the container answer to api.test and .gateway to every name below gateway.test.
    • Treat a sandbox as an isolated workload with or without a model, showing its network mode, mounts, CPUs and memory, and asking before stopping, force stopping, removing or editing a sandbox that another app owns.
    • Offer to update the container compose plugin when it is behind, and show the installed version at the bottom of the Compose tab.
    • Run containers on a platform other than the Mac's own, including linux/amd64 images under Rosetta, and keep the chosen platform when a container is edited, recovered or recreated.
    • Notice when Apple container is not installed and offer to install 1.6.1 with one administrator prompt.
    • Read a compose project's file again before Up, so an edit made since the Compose tab was opened is what runs.
    • Keep named volumes, tmpfs mounts and block mounts when Orchard recreates a container, with the same volume and options.
    • Show the runtime's error in the Run, Create Sandbox and Edit sheets and keep them open to try again.
    • Keep each published port's host address when a container is recovered or recreated.
    • No longer offer Remove for a running container in the Containers list; a mixed selection offers to remove just its stopped containers.
    • Keep a container's network, DNS domain and DNS aliases when it is edited, including on Save & Recreate.
    • Stop a Compose hook process Orchard loses track of instead of leaving it running.
    • Work with Apple container 1.6.1, which renamed its Kubernetes plugin from k8s to cluster; the sidebar's k8s Clusters is now Clusters.
    • Limit a failed command's alert to the last progress line and at most the last 10 lines of the rest, and say how many lines it left out.
    • Replace Hide Dock icon with a Show Dock Icon choice: Always, While a Window Is Open or Never; the menu bar panel gains Settings and Quit buttons.
    • Show a prominent "Start Container System" button on the stopped-system screen, with Starting... feedback while startup is in progress.
  3. 2.6.0

    OpenNavo editorial Added to Homebrew

    CompatibilitymacOS 26 or later

    With Apple container 1.6.0 or later, adds worker nodes and a no-CNI option when creating clusters, container-to-image commits, and custom machine accounts. Multi-node clusters expand to show node roles and status. Machine creation now warns that a read/write home mount lets processes inside the machine change Mac files. Workers and machine accounts are creation-time settings.

    With Apple container 1.6.0 or later, adds worker nodes and a no-CNI option when creating clusters, container-to-image commits, and custom machine accounts. Multi-node clusters expand to show node roles and status. Machine creation now warns that a read/write home mount lets processes inside the machine change Mac files. Workers and machine accounts are creation-time settings.

    Source: https://github.com/andrew-waters/orchard/releases/tag/v2.6.0

  4. 2.5.2

    Expand

    OpenNavo editorial Added to Homebrew

    CompatibilitymacOS 26 or later

    Compose lifecycle hooks, label migration and DNS fixes.

    Orchard 2.5.2 — Release notes

    The Compose tab runs post_start and pre_stop hooks and displays the active hook and latest output. A failed post_start aborts the up operation and leaves its container in place; a failed pre_stop is reported but stopping proceeds. Hooks do not run for starts or stops from the Containers tab or menu bar.

    Updates to compose 0.5.0: container labels change from com.container-compose.* to com.compose.*. Older projects are no longer recognized in the Compose tab. Take them down with the version that created them, or remove their containers, then bring them up again.

    Fixes the compressed row for a newly added project that sorts first. Restores service dns, dns_search and dns_opt settings and resolver configuration for containers created through Run. Requires macOS 26 and Apple container 1.5.0.

    Official sources

  5. 2.5.1

    Expand

    OpenNavo editorial Added to Homebrew

    Fixes window activation, default DNS configuration, disappearing Compose projects, overlapping container refreshes and SwiftUI error-alert warnings.

    Changes
    Reuses and restores the existing Orchard window from the menu bar.Fixes default DNS settings on container 1.4.1 and later.Preserves Compose projects when saved-list reads fail.Prevents older overlapping refreshes from overwriting newer results.Fixes SwiftUI warnings when dismissing an error alert.

    Orchard v2.5.1

    Thank you for using Orchard, and for the bug reports, ideas and pull requests that keep making it better. If it's useful to you, please consider starring Orchard on GitHub. It takes a second and helps other people find it.

    Changes

    Fixed
    • Open Orchard in the menu bar brings the Orchard window to the front instead of opening a second one (#118). A minimised window is restored, and a new window opens only if none is open.
    • Making a DNS domain the default works again on container 1.4.1 and later (#116). Orchard set it with container system property set dns.domain, which those releases no longer have, so Make Default and the DNS Domain picker in Settings failed with "3 unexpected arguments". The default is now an Orchard setting, used for containers you create in Orchard, so changing it needs no administrator password and no restart of the container system. If you haven't chosen one, Orchard uses the [dns] domain from your ~/.config/container/config.toml, and Settings > General shows that value as the container default.
    • Compose projects no longer disappear from the Compose tab when Orchard briefly can't read its saved project list. A failed read was treated as an empty list. Orchard now keeps the projects it already has, and won't save over the list until it has read it.
    • The container list no longer jumps back to an older, sometimes empty, list when several refreshes overlap. A slow refresh that finished after a newer one could overwrite the newer result.
    • Dismissing an error alert no longer logs a SwiftUI warning about publishing changes during a view update.

    Installation

    Homebrew

    brew install orchard
    

    Already installed with Homebrew? Update with:

    brew upgrade orchard
    

    Download

    1. Download Orchard-2.5.1.dmg
    2. Open it and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Orchard also updates itself: when a new release is out, it offers the update in the app.

    Checksums

    System Requirements

    Source: https://github.com/andrew-waters/orchard/releases/tag/v2.5.1 Homebrew version evidence: https://github.com/Homebrew/homebrew-cask/commit/8d1c758b256225baf6339909cb5a6f84de9843c9

  6. 2.5.0

    Expand

    OpenNavo editorial Added to Homebrew

    Adds Kubernetes version selection, custom CNI and host-localhost DNS redirects; updates Apple container integration and fixes Compose plugin installation and empty entrypoints.

    Changes
    Adds Kubernetes version selection and custom CNI manifests.Adds DNS redirects to services on the host Mac.Builds against Apple container 1.5.0; replaces cluster Start with Recreate.Fixes missing plugin detection, Compose reinstall and empty entrypoints.

    Orchard v2.5.0

    Thank you for using Orchard, and for the bug reports, ideas and pull requests that keep making it better. If it's useful to you, please consider starring Orchard on GitHub. It takes a second and helps other people find it.

    Changes

    Added
    • Choose the Kubernetes version when creating a cluster. The Create Cluster sheet's free-text node image field is now a menu headed by the node image Apple container's k8s plugin ships with (marked Recommended, and read from the installed plugin rather than a copy in Orchard), followed by the newest kindest/node release of each Kubernetes version from 1.31, fetched from Docker Hub when the sheet opens and pinned by digest. "Custom Image" takes any other reference. Choosing a version only became meaningful with container 1.5.0: until then the plugin configured the control plane for its default version whatever image you passed, so a different image ran mismatched components. For the same reason 1.5.0 rejects a node image with no tag, and Orchard now says so before creating anything. Offline, the menu offers the recommended image and a custom one.
    • Use your own CNI with a new cluster. The Create Cluster sheet's Advanced section takes a CNI manifest to apply instead of the default kindnet (container 1.5.0's --cni). Orchard can't check that a manifest suits the cluster, so the sheet points out that it must fit the pod subnet and links to Apple container's Custom CNI guide.
    • Redirect a DNS domain to your Mac's localhost. The Add DNS Domain sheet takes an optional IPv4 address; the domain resolves to it and Apple container redirects that address to the host's 127.0.0.1, so containers can reach a service running on the Mac by name. Domains set up this way are marked LOCALHOST in the list and show their address in the detail header. Before container 1.5.0, adding or removing one of these redirects reloaded the Mac's whole packet filter configuration and cut outbound networking for every running container; 1.5.0 reloads only its own rules.
    Changed
    • Orchard now builds against Apple container 1.5.0 (containerization 0.47.0), up from 1.4.1 (containerization 0.45.0). Nothing Orchard calls has changed shape. The release also fixes GHSA-44v5-vx46-ghv6 in the k8s plugin (kubeconfig values from the guest are now sanitised before being merged into your kubeconfig), which Orchard picks up through the CLI.
    • Orchard no longer warns that cluster creation will fail on a guest kernel built without nftables. Container 1.5.0 prepares nodes with the node image's own iptables backend instead of hard-coding iptables-nft, so the older kernel that an upgraded install keeps now works (apple/container#2120). A node-preparation failure still gets Orchard's own message rather than the CLI's, which names a step that succeeded, but it no longer blames the kernel.
    Removed
    • Starting a stopped cluster, which is replaced by Recreate. Container 1.5.0 removed container k8s start, so a stopped cluster can only be deleted and created again; Recreate does both in one step. It opens the Create Cluster sheet filled in from the cluster (its name, CPUs and memory, the Kubernetes version and, for clusters Orchard created, the CNI manifest) and deletes and creates when you confirm. A node doesn't record its image tag, so Orchard recovers the version from the image digest, and asks when it can't. Stopped cluster nodes in the Containers list, the menu bar and the command palette no longer offer Start either: a plain start skips the boot, readiness wait and kubeconfig write the old command did, so the node's detail offers Recreate Cluster instead.
    Fixed
    • Orchard notices a missing Kubernetes plugin again on container 1.5.0, which reports it as an unknown command rather than a missing plugin. Without this, the Clusters tab showed a Create Cluster button that stayed disabled with no explanation.
    • A stopped container's resource charts are hidden, as they are for a container that hasn't run. A container that ran earlier in the session kept its charts after it stopped, and a time window with too few samples then showed a "Collecting" spinner for samples that were never coming. The same applies to machines and clusters.
    • Orchard offers to reinstall the compose plugin after a Homebrew upgrade of container removes it (#113). Orchard decided whether the plugin was installed by looking in /usr/local, but a Homebrew container looks for plugins inside its own versioned install, so after a brew upgrade a copy in /usr/local still counted as installed although the CLI could not see it, and an install from Orchard went where that CLI never looks. Orchard now asks the CLI itself whether container compose works, and installs into the directory the CLI names in its error. That directory belongs to you under Homebrew, so the install no longer asks for an administrator password there.
    • Images that clear their inherited entrypoint with ENTRYPOINT [""] now run. Orchard used the empty string as the program to launch, so the container failed to start; the command now runs on its own, as the CLI does from 1.5.0.

    Installation

    Homebrew

    brew install orchard
    

    Already installed with Homebrew? Update with:

    brew upgrade orchard
    

    Download

    1. Download Orchard-2.5.0.dmg
    2. Open it and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Orchard also updates itself: when a new release is out, it offers the update in the app.

    Checksums

    System Requirements

    Source: https://github.com/andrew-waters/orchard/releases/tag/v2.5.0 Homebrew version evidence: https://github.com/Homebrew/homebrew-cask/commit/b7ab9771c57802fcbf5a6cf7efc278676425ef45

  7. 2.4.3

    Expand

    OpenNavo editorial Added to Homebrew

    Adds configurable AI endpoint addresses and disabling; clarifies API-key saving outcomes and backs off probes for servers requiring authentication.

    Changes
    Allows editing and disabling detected model-server endpoints.Reports API-key save, rejection and Keychain failure outcomes.Backs off probes unless a usable model server is detected.

    Orchard v2.4.3

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • The AI Models panel's detected endpoints can now be re-pointed and switched off (#110). The four addresses discovery probes (Ollama on 11434, LM Studio on 1234, an MLX server on 8080 or 8000) were a hardcoded list. A server listening anywhere else was undiscoverable, and there was no way to exclude one you would rather Orchard left alone. Each one is now a configuration you own: the detail pane carries the host and port it probes, with Save and, for an address you have moved, "Restore default". Switching one off stops Orchard contacting it at all rather than merely hiding it, and it moves to a "Not probed" section in the list, so there is a way back on. An endpoint you have moved keeps its row under "Not answering" while nothing responds there, so a mistyped address can be corrected rather than taking the endpoint out of the panel; a built-in sitting on its shipped address stays quiet, since "you aren't running Ollama" is not news. Both choices persist, and a built-in added in a later release joins your list rather than replacing it. An endpoint pointed at another machine is bridged into containers by its own address, since only a server on this Mac needs the network gateway indirection.

    Fixed

    • Saving an API key for a locked model server now tells you what happened (#110). The field cleared itself on Save and said nothing further, which looked the same whether the key had been stored and rejected, stored and accepted, or never stored at all. Keychain writes also discarded their status entirely, so a refusal from the keychain was invisible by construction. The panel now reports each outcome in its own words, including the one that previously had no voice: a key saved successfully that the server still rejects, which is a wrong key rather than a broken Save. A stored key is shown as stored, with a Remove button, instead of an empty field that could mean either nothing saved or something hidden.
    • A model server that wants an API key is no longer probed every 5 seconds for as long as Orchard runs (#110). The background tick backed off to 30s only while nothing was detected, and a server answering 401 counts as detected, so an endpoint Orchard could never get into held the fast cadence indefinitely and filled that server's own log with rejected requests. The tick now backs off unless something usable is detected. Saving a key still re-probes immediately, so nothing that depends on a fresh answer waits on the slower cadence, and an endpoint switched off is not contacted at all.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

    Source: https://github.com/andrew-waters/orchard/releases/tag/v2.4.3 Homebrew version evidence: https://github.com/Homebrew/homebrew-cask/commit/9a24d8468fdc7e2c4af4247a5a5705937d226150

  8. 2.4.2

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.4.2

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Hi everyone, this release is a huge one personally, and one that's long overdue.

    Since Apple launched container, everyone's been looking for Compose support so Docker Compose files can be brought across. The maintainers themselves have turned this down in several issues, pushing it onto the community. I've closed a lot of feature requests because I hoped this would be a core feature, but the maintainers made it very clear they are not going to work on it.

    In the early days, many people, including myself, attempted to build something to solve that. However, they were all independent binaries, and still are — requiring their own commands and not portable.

    A few releases ago, container added support for plugins, the first of which is an official k8s one — it's the same plugin Orchard itself calls to bring k8s to your box.

    So in order to bring these worlds together, I've created a new project, compose, which is a plugin for apple/container that can be installed without Orchard (although it's offered to you with minimal work involved via the UI).

    The syntax for compose looks exactly how you would want it:

    container compose up --help
    

    I'm opening that up in the hope that other developers can contribute to it and make it the standard way to use Compose with containers. There is no Orchard logic in it — it's a plugin and can be bundled as a Swift library in 3rd party tools such as other UI's or applications, instead of being proprietary.

    With this being so new, if you have any feedback or want to contribute, please do!

    Check out the project and give this new Orchard release a go — navigate to the Compose view where it will be installed for you, if you wish.


    Added

    • The shell a container terminal opens with is now a setting, taken as written and passed through with its flags, so bash -l gets a login shell that reads your rc files (#107). Which shells an image has and which flags they accept is a property of the image, so there is nothing here for Orchard to enumerate and nothing worth validating beyond refusing to send an empty command. sh remains the default because it is the one shell a minimal image is likely to have, which makes it a safe default rather than a good one.

    • A Compose tab, for bringing a set of services up and down from a compose file. Projects are found by the labels on their containers rather than by any file Orchard keeps, so a project brought up from the terminal appears here without Orchard having been told anything, and a project Orchard has been shown a file for can be brought up, taken down and reconciled from the window. Running up a second time compares each service against a hash stamped on the container it produced, then creates, starts, leaves alone, recreates or removes each one accordingly, and every step is listed as it happens.

    • Compose keys that cannot be honoured are never quietly dropped. Adding a project shows what will be ignored, how much ignoring it costs, and the line each key sits on, and the project goes on showing that afterwards: three weeks later nobody remembers what they accepted, and the containers cannot tell them. A file that grows a new unhandled key is put back in front of you before the next up rather than waved through on an older answer. A service that builds is built through the same path as the Images tab, so its BuildKit log shows up under Builds like any other build.

      The planning behind the tab is andrew-waters/compose, a Swift package Orchard links and which also backs the container compose plugin, so the terminal and the window cannot drift apart. Two limitations are worth stating up front: without health reporting in the runtime, up starts dependencies before dependents but does not wait for them to become ready, and hostnames have to be unique across every container on the machine, so a service answers to <project>-<service> rather than to its service name.

    • The Compose tab offers to install the container compose CLI plugin when it is not there. Orchard itself never needs it, because the window links the planner and runs plans over XPC, so this is an offer rather than a fault and the banner is coloured accordingly: every project in the list works with nothing installed. It is worth offering because container's own installer clears the plugin directory on every upgrade (apple/container#1617), so a plugin someone installed by hand goes missing again through no fault of theirs. Installing fetches the latest release, unpacks it, and puts the two files where the CLI looks, with the work shown step by step in a sheet: this downloads 15MB and then asks for an administrator password, and someone about to be asked for their password should be able to see what asked and why. Everything up to the copy happens unprivileged in a temporary directory, so a failure before that point never prompts at all, and a download in flight can be cancelled.

    Fixed

    • Ghostty no longer gets a new window, and a second copy of itself, every time you open a container terminal (#107). Orchard launched it with open -na, and -n starts a separate instance: a window in one instance can never join a window in another, so a new window was not a design choice so much as an inevitability, and every container opened left another Ghostty running. Ghostty 1.3 ships a scripting dictionary, so it is now driven the way Terminal.app and iTerm2 already were rather than through open, and all three stop being special cases. Whether the terminal arrives as a tab or a window follows the system-wide "Prefer tabs when opening documents" setting rather than a preference of Orchard's own: you have answered that question once, for every app. macOS defaults that to fullscreen rather than always, so the default is still a window; the difference is that it is now the system's answer rather than Orchard overriding it.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  9. 2.4.1

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.4.1

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • The k8s Clusters tab now warns when the guest kernel cannot bootstrap a cluster, and offers to fix it. container k8s create prepares its node with iptables-nft, which needs a kernel built with nftables; the kernel Apple container recommended before 1.3.0 was not, and container system start skips the kernel download whenever a kernel already exists (apple/container#905), so an install carried forward from an earlier release keeps the old kernel and fails every cluster creation however new the CLI is. Orchard reads the default kernel the CLI records, and when it predates nftables the tab says so and offers "Install Recommended Kernel" in place of the empty state. Creation is still available from there, because the check is a version floor rather than a capability probe and a deliberately chosen custom kernel is nobody's business but yours.

    Changed

    • Sheets have one Cancel button rather than two. Create Cluster, Create Machine, Edit Machine, Add Network and Add DNS Domain each had one in the header and another in the footer, and several bound the Escape key twice over. The footer keeps its Cancel, beside the action it cancels.
    • The log viewer's target picker now shares a row with the filter field instead of sitting on a row of its own above a divider, which gives every pane back a band of vertical space; a window split four ways spent four of them on it. The picker also sits flush with the pane's leading edge: a menu picker centres itself in a flexible frame, which was insetting it from everything above and below.

    Fixed

    • Opening Containers or Images no longer highlights a row from the middle of the list. Both lists sort and filter in the view (by name, running first, the search field, the in-use toggle), while the selection was made from the first element of the service's array, which is the order the daemon returned. On this machine that meant Images opened on a digest-pinned Kubernetes node image nine rows down. Each of those lists now claims the first row it is actually showing.
    • A single-node Kubernetes cluster is no longer treated as though it had no control plane. Container 1.4.1 labels the one node of a default container k8s create cluster control-plane,worker, because it is both, and Orchard compared that label to control-plane exactly. The node therefore classified as a worker, the cluster read as stopped while it was running, and everything gated on a running control plane was hidden: the detail header offered Start instead of Terminal (kubectl), Write Kubeconfig, Copy Kubeconfig Path and Load Image, and every resource panel showed "Not running" over live charts. Roles are now read as the list the label can be, so a node that is both counts as the control plane.
    • A cluster that fails while its node is being prepared now explains why. The plugin runs node preparation as one set -e script whose last two commands are the iptables-nft calls, so an abort there surfaces the accumulated output of the steps that already succeeded: the error names net.ipv4.ip_forward = 1, a sysctl that worked, and never shows the command that failed (apple/container#2120, open with no fix in 1.4.1). Orchard recognises that failure and names the real cause, including the kernel responsible when it can tell.
    • "Install Recommended Kernel" no longer reports success without installing anything. An "already exists" refusal from the CLI was treated as an idempotent success, which is wrong in the one case that matters most: someone on an outdated kernel would be told the recommended one was installed and would still fail every cluster creation. The refusal is now retried with --force, which replaces only a kernel of the same name.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  10. 2.4.0

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.4.0

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Quick none-changelog related note from me - I hope you're finding Orchard useful to you. The last month has seen stargazers on the project double, so it's great to have you here. Please let me know if you're finding this useful and feel free to add any feature requests / bug reports on Github.

    The last release had over 3,100 downloads, so please consider giving it a star on Github if you're using it and spreading the word.

    And a special thanks to everyone who's contributed to the project so far!

    Added

    • Reclaim disk space on a running container, from the container detail header ("Reclaim Space") or the containers list context menu. Deleting files inside a container doesn't shrink its host-side disk images on its own, so the space stays claimed until the free blocks are trimmed; this hands them back and refreshes the system disk usage tiles once the daemon reports the trim done. Apple container exposes the operation for running containers only, so the action is offered only while a container runs, and a mixed multi-selection reclaims just the running members. Note that container 1.4.1 cannot yet complete the trim on a container's root filesystem: the guest's FITRIM ioctl returns "not supported" even though the block device backing the rootfs advertises discard, and the daemon trims "/" for every container that isn't read-only, so the operation fails there. Orchard reports that as a plain sentence rather than the daemon's three-deep nested error, and the action will start working against a container release that fixes the trim.

    Changed

    • Orchard now builds against Apple container 1.4.1 (containerization 0.45.0), up from 1.3.1 (containerization 0.42.0). The client-facing surface is additive between the two releases (a new XPC route and its client method), so nothing Orchard already called has changed shape. The bump also removes the two containerization advisories fixed in 1.4.1 (GHSA-4587-w9mm-xxvh, an OCI layout load that followed symlinks out of the extraction directory, and GHSA-rgqp-277h-gcwj, a socket path length limit longer than the buffer it copied into) from the shipped bundle. Neither was reachable from Orchard: the app has no OCI layout import path and doesn't open unix sockets, but there is no reason to ship the code.
    • The container system version Orchard displays is now the bare release number. Apple container 1.4.1 changed what its health check reports, from container-apiserver 1.4.1 to 1.4.1.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  11. 2.3.4

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.3.4

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Fixed

    • Scrolling a container's detail pane no longer hangs the app (#103). The six configuration wells sat in a LazyVGrid, and placing a row whose wells hold selectable text re-entered the grid's own placement: the main thread spun in over a thousand nested sizeThatFits frames at 100% CPU with memory climbing about 13 MB a second, and the window never recovered. The same two-column layout is now built eagerly from stacked rows, which six wells cost nothing to lay out up front. The wells also pair up only while the pane is wide enough to carry two and stack below that: at a 1024-point window two columns left a key/value row so little width that its value and Show/Copy controls fell out of the row entirely. Long environment-variable and OCI-label keys additionally cap their column rather than sizing to the longest key without limit, so a namespaced key wraps instead of crowding out its own value.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  12. 2.3.3

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.3.3

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Fixed

    • Local-model detection no longer probes every 5 seconds when nothing is listening. Each probe of the four conventional ports (11434, 1234, 8080, 8000) with no server behind them produced a connection-refused URLSession task, and CFNetwork logs every one - dozens of NSURLErrorDomain -1004 console lines per minute on an idle machine. The background tick now backs off to 30s while no provider is detected; while one is detected, the 5s cadence stays so a stopped server disappears promptly, and opening the Models tab or the run form's model bridge still probes immediately.
    • Editing a container no longer silently strips its labels. The edit sheet's prefill omitted labels entirely, so the recreation that applies an edit dropped every label on the container, including Orchard's own sandbox markers (a sandbox stopped being recognised as one after any edit). Labels now carry through: internal ones untouched, the rest editable in the new labels editor.
    • Running a locally built image no longer fails with a 401 from Docker Hub. The Run Container sheet canonicalised every image reference before running, so a local tag like mono2 was rewritten to docker.io/library/mono2 and the backend tried to pull a repository that doesn't exist on the registry (Hub answers 401 for unknown repositories). The reference now resolves against the local image store first - a match runs under the exact reference the store knows (including the implied :latest), and only unmatched references canonicalise into pullable registry form. The "Local image available" hint and the actual run decision now agree.

    Added

    • Labels can be set when running a container: the Run/Edit form's Advanced tab gains a key/value labels editor (matching the environment-variables editor), and the containers list can group by any of those keys. Internal com.apple.container.* and com.orchard.* labels are managed by the runtime/Orchard and don't appear as editable rows.
    • A Builds sidebar tab (Resources section, orchard://builds) tracks every image build Orchard has started, and the records survive relaunches (stored as versioned JSON in Application Support, with each log's last 1000 lines). The list shows status, start time, and duration per build, searchable by image name; the detail pane shows the build's request (Dockerfile, platform) and its log - complete while the app runs, trimmed to the last 1000 lines for records restored after a relaunch - live while building and reviewable after, with Cancel Build for in-flight builds and a context-menu Remove Record for finished ones. Once a build's image exists, the detail also mirrors the image view's affordances: a "Launch image" button opening the run-container sheet pre-filled with the built reference, a "Containers using this image" list that jumps to each container, and a confirmed Delete that removes both the build record and the built image (disabled while containers use the image; if the image delete fails, the record is kept). Builds and images cross-reference: the build detail's "View Image" jumps to the built image, and an image produced by an Orchard build gains a "View Build" button jumping to the newest successful build of that reference. Builds run concurrently and survive closing the Build Image sheet; a build still running when the app quits is marked "interrupted" on the next launch, since the CLI process was orphaned and its outcome never observed (the image may still have been built). The registry only lists builds Orchard itself started: apple/container's builder shim exposes just info() and a build stream over its gRPC surface, so BuildKit's own history is not reachable from the host.
    • Deep links: Orchard registers the orchard:// URL scheme. orchard://<tab> opens any sidebar tab (e.g. orchard://dashboard), and orchard://container/<id>, orchard://image/<reference>, orchard://mount/<id>, orchard://machine/<id>, orchard://dns/<domain>, and orchard://network/<id> jump straight to a resource, reusing the same navigation path as the command palette and menu bar (so a target in a still-loading list is selected once it appears). A resource noun without an identifier falls back to its tab, and image references keep their interior slashes.
    • Containers can be grouped by label: the containers sort menu gains a "Group by Label" submenu listing every label key present on current containers (internal com.apple.container.* bookkeeping labels excluded). With a key selected, the list renders one collapsible section per label value - click a header to fold it - with a count badge, a "No label" bucket for containers missing the key, and a per-group actions menu to start or stop everything in the group. The choice persists, and search/running filters apply within the groups.
    • Containers can be exported as tar archives (container 1.2+ API). An "Export…" button in the container detail header and an "Export Filesystem…" context-menu item in the containers list prompt for a destination, stream the filesystem through the API client (written to a scratch directory first, so a failed export never leaves a partial file at the chosen path), show an "Exporting…" state while in flight, and reveal the archive in Finder when done.
    • Image pulls now show real progress: a determinate bar with downloaded/total bytes and blob counts (e.g. "256 MB / 512 MB · 3/8 blobs") instead of an indeterminate spinner, updating live from the registry client's progress events (throttled to ~10 Hz so per-chunk byte updates don't churn the UI). The bar stays indeterminate until the total size is known, and the phase label ("Fetching image") replaces the static "Pulling image..." message.
    • Build images from a Dockerfile. The Images tab gains a hammer button (and the command palette a "Build an Image..." action) opening a Build Image sheet: pick the Dockerfile through a file panel so non-default names like Dockerfile.dev are discoverable (the build context auto-fills to the Dockerfile's folder), name the image, choose the target platform (Apple silicon linux/arm64 or Intel linux/amd64, defaulting to the host), and optionally build without cache. The build shells out to container build, which starts the BuildKit builder on demand, and the build log streams live into the sheet through the ANSI console; closing the sheet leaves the build running, and a Cancel Build button terminates it. Successful builds refresh the image list automatically.
    • Log views now render ANSI colours and support selection across lines. Container and machine logs were previously drawn as one SwiftUI Text per line, which printed colour escape codes as literal garbage and scoped text selection to a single line. Both the detail Logs tab and the log viewer window now share a single NSTextView-backed console: SGR styles (16-colour, bright, 256-colour, truecolour, bold/italic/underline) are rendered, other escape sequences are stripped, carriage-return progress lines show their final state, and click-drag or Cmd+A/Cmd+C works across the whole log. Filtering now matches the escape-stripped text, so a filter term can no longer hit or miss because of bytes inside a colour code, and the console follows the tail only while scrolled to the bottom (scrolling up to read no longer fights the 2s refresh, which previously only auto-scrolled on first load).

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  13. 2.3.2

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.3.2

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Fixed

    • The GUI now tracks the container system when it is stopped and started from the CLI (#100). The 5-second status poll was torn down by the main interface's onDisappear, which also fires when the system stops and the "not running" screen swaps in. After that, nothing polled, so a container system start run in a terminal was never noticed and Orchard stayed on "Container is not currently running" until the power button was clicked. The same dead end was reachable by launching Orchard while the system was stopped. The poll's lifetime now matches the window rather than one branch of the state view, so external stops appear within a poll tick (a stop can still lag while container system stop drains running containers, since the API server answers until it deregisters) and an external start restores the full interface automatically.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  14. 2.3.1

    Expand

    GitHub Release

    Orchard v2.3.1

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Fixed

    • Image sizes now match container image ls -v (#98). Orchard was showing the size of each variant's manifest descriptor - a couple of kilobytes of JSON - instead of the image content, so every image listed as "1 KB"–"3 KB". Variant sizes are now computed the same way the CLI computes FULL SIZE: manifest descriptor plus config blob plus the sum of the compressed layers. The container detail's Image section and the multi-select image cards previously showed the raw index descriptor size as "Size"; both now use the same resolved size as the images list, and the image Technical Details row is relabeled "Index Size (bytes)" since that value genuinely is the index descriptor size.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  15. 2.3.0

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.3.0

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Changed

    • Orchard now links the Apple container 1.3.1 client libraries (previously 1.2.2), restoring compatibility with current container installs. 1.3.1 also patches six security advisories in the containerization package that Orchard's image operations link directly, including path traversal in the local content store and a RegistryClient that followed WWW-Authenticate realms without validating the host.
    • Image pulls now default to https for all registries, matching container 1.3.0's removal of the auto registry scheme. Pulls from localhost or private-IP registries no longer silently downgrade to plain http; a local http registry needs registry.scheme = "http" in the container configuration, same as the container CLI.

    Fixed

    • Local-model detection no longer follows HTTP redirects when probing for providers. The probe targets conventional ports (11434, 1234, 8080, 8000), which are often owned by something else entirely; a dev server on 8080 that redirects to its TLS port would take the probe with it, so Orchard opened a connection to an unrelated endpoint every five seconds and abandoned it when the 1.5s probe deadline expired. Against a Rails app running with force_ssl this leaked a socket per probe until the server's accept loop stopped and it served nothing at all. A real provider answers 200 directly, so a redirect is now simply classified as "not a provider" - which also stops a redirecting server from being misreported as a model server.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  16. 2.2.2

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.2.2

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • The menu bar popup now exposes a Stop control for the container system alongside the existing Start control, so the system can be shut down without opening the main window or going through the command palette. The button is gated on a running system and disabled while a transition is in flight; calling stopSystem() while a transition is already in flight is a no-op at the service layer.

    Fixed

    • Menu-bar System analytics no longer stays stuck on "Collecting…" when container stats fail. The menu-bar hover popover now distinguishes four explicit states: collecting during the initial two-tick baseline, available with real CPU/memory history, "No running containers" when the system has none to sample, and "Stats unavailable" with a short reason when the XPC service is unreachable or every stats call failed. Per-container stats failures are now logged via Log.xpc so diagnostics aren't blind, and the existing dashboard, container, and machine stats paths are unchanged. No new macOS permission is required.
    • Container service-unavailable failures in the menu-bar sampling tick are now logged only once per tick via Log.xpc; subsequent outcomes in the same tick fold in silently while the first error is retained, so a single tick with several unreachable containers no longer produces one log line per outcome.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  17. 2.2.1

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.2.1

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • Command palette: press Cmd+K (or View > Command Palette...) to fuzzy-search everything Orchard manages - containers, images, mounts, machines, k8s clusters, AI models, sandboxes, DNS domains and networks - and jump straight to any of them, or run actions from the keyboard: run a container, pull an image, create networks/machines/clusters, start/stop/restart the container system, and per-resource verbs like "stop db", "logs api" or "console web". Results rank with real fuzzy matching (exact prefix beats word-boundary beats scattered match); destructive operations are deliberately not palette-reachable.
    • The Dock icon can now be hidden (Settings > General > "Hide Dock icon"): Orchard switches to a menu-bar accessory, staying reachable from the menu bar, and the preference applies immediately and persists across launches. Note that macOS also removes accessory apps from the Cmd-Tab switcher.

    Fixed

    • The AI Models and Sandboxes middle columns no longer render lighter than every other list: they used the sidebar list style, which paints its own source-list background, instead of the plain style the rest of the middle columns use.
    • Searching in the DNS and Networks tabs now actually filters the list; previously the search field rendered, but typing did nothing.
    • The search query is cleared when switching tabs, so a query typed in one tab no longer silently filters the next.
    • The containers list now supports Command+A select-all like the other multi-select lists.

    Removed

    • Dead internal code: the never-shipped item navigator popover, its orphaned header component and an unused detail column wrapper.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  18. 2.2.0

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.2.0

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • Containers owned by a container plugin (such as k8s cluster nodes) are badged in the containers list and detail header with the owning plugin and their role, e.g. "k8s · control-plane", so kindest/node containers aren't mystery rows.
    • Clusters: a new sidebar section for local Kubernetes clusters created with the container k8s plugin (container 1.2.2+). Node containers are grouped into clusters with per-node role, status, IP, CPUs, memory, and published ports; clusters can be created, started, and deleted from the UI, local images can be loaded into a cluster's containerd, and the kubeconfig can be written or its path copied, with a one-click terminal preconfigured for kubectl. Installs without the plugin get an explanatory state with upgrade guidance.

    Fixed

    • With the sidebar hidden, the Dashboard (and other full-width pages) no longer render underneath the macOS window controls (#88).

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  19. 2.1.7

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.1.7

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Changed

    • Orchard now links the Apple container 1.2.2 client libraries (previously 1.1.0), restoring compatibility with current container installs (#54).
    • When the installed container release doesn't match the client Orchard links, the app now shows the version-incompatibility screen with upgrade guidance instead of reporting the system as stopped with a raw health-check decode error (#37, #39).

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  20. 2.1.6

    Expand

    GitHub Release

    Orchard v2.1.6

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • Pull images by reference from non-Docker-Hub registries: the image search gains a pull-by-reference input, and references are canonicalized so by-reference and search-result pulls share progress tracking.
    • Docker Hub search now searches as you type (300ms debounce, Enter bypasses it) and paginates as you scroll.

    Changed

    • Image sizes display consistently and pull progress is clearer, with failed pulls dismissible and retryable.
    • Multi-selection across containers, images, mounts, DNS domains, and networks: shift-click range selection, Command+A select-all, batch deletion, and a summary detail view for the selection (#53).

    Fixed

    • The Run Container sheet now stays open when the run fails, so the configuration can be adjusted and retried; previously it dismissed regardless, leaving only the error alert.
    • When the container system is stopped or XPC is unreachable, Orchard no longer storms error dialogs from background refresh. Failed XPC connections surface as a clear "container service is unavailable" message, and after starting the system Orchard waits until the service is actually reachable before loading data.
    • Running containers' stop buttons in the menu-bar panel now respond on first click.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  21. 2.1.5

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.1.5

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • 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).

    Fixed

    • 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).

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  22. 2.1.4

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.1.4

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • Error message displayed when trying to start container now includes a download link if the binary could not be found.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  23. 2.1.3

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.1.3

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • Local AI models (MLX): a new AI Models section discovers model servers running on your Mac (Ollama, LM Studio, and MLX servers), and can start and stop your own mlx_lm.server instances - pick a model and port, choose whether to bind 0.0.0.0 so containers can reach it, with child-process supervision, crash surfacing and log access.
    • The container↔model bridge: wire a container to a host model in one step. Orchard computes the container-reachable endpoint from the network gateway and injects OPENAI_BASE_URL at create time - so a containerised app or agent talks to a local model with no hand-configured host networking. Inference runs on the Apple GPU on the host (Virtualization.framework guests have no GPU access).
    • Sandboxes: a first-class view of containers wired to a local model, recognised by a label Orchard stamps or by a model-endpoint environment variable. Each sandbox shows its model endpoint, an isolation badge (host-only/no-egress vs internet-open), and agent-runner controls - chat, terminal, and a stop kill-switch. Create one from the New Sandbox button or from a model's detail.
    • In-app chat tester: hold a short conversation with any model server from the AI Models view - no terminal or container needed - to check it's working.
    • Sandbox containers are flagged with a shield badge (and an explanatory popover) in the Containers list and detail, since a sandbox appears in both places.
    • A new Local AI guide on the site covering MLX, the bridge, isolation, and a runnable quick start.

    Changed

    • Reorganised the sidebar so Sandboxes joins Containers and Machines under Compute, and AI Models sits under Resources alongside Images and Mounts.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements

  24. 2.1.2

    Expand

    GitHub Release Added to Homebrew

    Orchard v2.1.2

    Installation

    1. Download the DMG file below
    2. Open the DMG and drag Orchard.app to your Applications folder
    3. Launch Orchard from Applications

    Changes

    Added

    • Container machines: create, configure, run and monitor Apple container machines (persistent Linux VMs) directly in Orchard, over the native XPC API rather than shelling out to the CLI. A new Machines section in the sidebar lists your machines with state, IP address and a default badge, and the detail view shows the full configuration plus live CPU, memory, network and disk usage.
    • Create machines from an image with configurable CPUs, memory (defaulting to about half your host RAM), home-directory mount mode (read/write, read-only, or none), nested virtualization, and an optional custom kernel.
    • Machine lifecycle controls - start, stop, set-default, and delete - each with clear in-progress feedback.
    • Edit a machine's configuration with a one-click stop, apply and restart, since Apple's runtime only applies CPU/memory/home-mount/kernel changes on the next boot.
    • Machine output and boot logs stream in the same multi-pane log viewer as containers, and running machines appear in a Machine Utilisation table on the Dashboard.
    • Init-system guardrails for the most common machine pitfall: a warning before creating from an image that has no init system, and a clear "the image has no init system" explanation when a machine boots and immediately stops because it lacks /sbin/init.

    Changed

    • Reorganised the sidebar into Compute (Containers, Machines), Resources (Images, Mounts) and Networking (DNS, Networks), with Machines a first-class peer of Containers.

    Fixed

    • Container machines' backing containers no longer appear as unexplained entries in the container list - they're now filtered out, matching the container CLI.

    Checksums

    • SHA256: See the .sha256 file for verification

    System Requirements