Skip to content

The macOS App

MultiDocker ships with a native SwiftUI app for macOS 14+. It’s a graphical front-end over the same engine the CLI uses — not a re-implementation. Every action in the app shells out to the mdocker binary and decodes its --json output.

The MultiDocker main window: the sidebar shows the “Aktiv” block with acme-platform and its two live sessions plus the groups ACME CORP and INTERNAL; the detail pane shows the “Übersicht” tab of acme-platform with a red pulsing status aura, because one session is working, plus the tab badges and the expanded Health and Git cards.

The app also lives in the menu bar. The popover gives you every project’s state and a toggle to start or stop it, without bringing the main window forward:

The MultiDocker menu bar popover: three projects with status dots, hostnames and start/stop toggles.

The app wraps the CLI through Swift’s Process API. When you click “Start” on a project, it runs mdocker up <name>; when it renders the project list, it parses mdocker ls --json. This means:

  • The app and CLI can never drift in behaviour — there’s one implementation of every verb.
  • Anything the app does, you can reproduce (and script) on the command line.
  • The app adds presentation and orchestration on top: a sidebar with an “Aktiv” block and collapsible groups, a tabbed project detail, a Spedy tickets tab, a global AI-session overview with live status, a status aura that reacts to running work, embedded terminals, a profile editor, and a first-run wizard.

The app follows an MVVM + dependency-injection structure:

View ──► ViewModel ──► Service ──► ProcessRunner ──► mdocker
│
└──► Storage (preferences, logs, wizard state)
  • Views are dumb — they observe @Published state and send actions upward.
  • ViewModels own feature state and orchestrate service calls.
  • MdockerService is the umbrella service that wraps every CLI verb, decodes models, and tracks in-flight actions for progress UI.
  • ProcessRunner is the single place that creates Process instances, with PATH augmentation (so it finds brew-installed tools) and a SIGTERM→SIGKILL timeout.

All services and view models are @MainActor, so UI updates are always thread-safe.

Area What it shows
Sidebar A header “Projekte” with a counter and an “Hinzufügen” button, an “Alle AI-Sessions” row, an “Aktiv” block listing every project with a live session, and collapsible group sections. Hovering a project row turns its profile badge into a “+” that starts a new AI session. A footer entry opens the global profile editor.
Detail pane A sticky header (name, status, profile badge, URL, actions) over a status aura, plus a glass tab bar with four tabs: “Übersicht” (⌘1), “Services” (⌘2), “Tickets” (⌘3) and “Einstellungen” (⌘4).
Toolbar / menubar A Doctor button, refresh, settings, and an EDGE badge that turns red when the edge stack is down.
Console A collapsible bottom console showing every command the app ran, its output and exit code.

The app is optional. You can run everything from the terminal with mdocker. But the app adds real value for day-to-day use: at-a-glance health, one-click start/stop, embedded terminals that survive quitting the app, a live profile editor with validation, and Spedy tickets next to the project they belong to.

Under Einstellungen → Demo-Modus the app switches to fictional data: the Acme Corp projects, AI sessions in every state, Spedy tickets, Git status, database snapshots and configuration. Docker, tmux, Git and the Spedy API are not touched, and your real projects stay as they are. It is meant for screenshots, product videos and walkthroughs. A DEMO badge next to the EDGE badge shows that the mode is on. You can hide that badge for a screenshot.

To use demo mode for a single launch only, start the app with open -a MultiDocker --args --demo. In the terminal, MD_DEMO=1 mdocker … shows the same data.