Sidebar & Project Detail
The main window is a classic split view: a sidebar of your projects on the left, and a tabbed detail pane for the selected project on the right.

The sidebar
Section titled “The sidebar”From top to bottom the sidebar holds:
- A header “Projekte” with a counter and an “Hinzufügen” button that registers an existing compose project (scan or manual).
- A row “Alle AI-Sessions” (sparkles icon) with a counter of live sessions and a red pulsing dot while any session is working. It opens the global session overview.
- The block “Aktiv”.
- The group sections.
- A footer entry “Profile” that opens the global profile editor, with a live counter of how many profiles exist.
The “Aktiv” block
Section titled “The “Aktiv” block”Every project that currently has at least one live session (alive and not exited) is lifted into the “Aktiv” block at the top: the project row plus its live sessions, indented underneath. The block is not collapsible, it never grows past 42 % of the sidebar height and scrolls on its own beyond that, and its header carries the same red pulsing dot when a session is working.
Groups
Section titled “Groups”Below “Aktiv” the projects are grouped. Group sections are sorted alphabetically, with ungrouped projects collected last under “Weitere”. If no project has a group at all, the sidebar falls back to a flat list without any headers.
A group header has a 3 pt gradient bar and toggles between “Gruppe ausklappen” and
“Gruppe einklappen” as its tooltip. The collapsed state is persisted in
~/.multidocker/preferences/preferences.json under collapsedGroups, so the sidebar looks
the same after a restart.
Groups are assigned per project — from the context menu below, from the “Gruppe” card in the
Einstellungen tab, or from the CLI with mdocker group set. See
Project Groups.
The project row
Section titled “The project row”Each row shows a status dot, the project name, its primary hostname in a monospaced font, and a profile badge — “Shopware”, “API + Web”, “Generic”, or the profile name for anything else.
When you hover the row, the badge is replaced by a “+” in the brand gradient with the tooltip “Neue AI-Session erstellen”. It opens the new-session sheet directly, without a detour via the detail pane.
Context menu
Section titled “Context menu”Right-clicking a project row offers, in this order:
- “Stoppen” and “Neustart” for a running project, “Starten” for a stopped one
- “Im Browser öffnen”
- “Pfad im Finder zeigen”
- the submenu “Gruppe” — every existing group as a checkmark entry, then “Keine Gruppe”, then “Neue Gruppe …”, which opens a sheet titled “Neue Gruppe” with a “Gruppenname” field and the buttons “Abbrechen” and “Anlegen”
- “Auswählen, um umzubenennen”
- “Aus Liste entfernen …”

The detail pane
Section titled “The detail pane”Selecting a project shows a sticky header — name, status, profile badge, URL and the lifecycle actions (⌘R starts the project) — above a glass tab bar.
Status aura
Section titled “Status aura”Behind the header sits a status aura that tells you what the project is doing without reading a single label:
| Aura | Meaning |
|---|---|
| off | the project is stopped |
| green, static | the project is running |
| red, pulsing (1.6 s) | a session in this project is working — this beats green |
The pulse respects the system’s Reduce Motion setting.
The four tabs
Section titled “The four tabs”| Tab | Shortcut | Badge |
|---|---|---|
| “Übersicht” | ⌘1 | red pulsing dot while a session is working |
| “Services” | ⌘2 | the number of services |
| “Tickets” | ⌘3 | the number of open tickets |
| “Einstellungen” (short title “Optionen”) | ⌘4 | — |
Switching tabs slides the content horizontally.
“Übersicht” tab
Section titled ““Übersicht” tab”Health, git, Shopware and AI sessions. The cards flow into two columns from 840 pt of content width (capped at 1200 pt); the git and Shopware cards hide themselves when they aren’t relevant, and the layout closes the gap.
Health card
Section titled “Health card”An at-a-glance summary from mdocker health <name> --json: edge stack status, per-service
container state, and an HTTP probe for each hostname. This is the fastest way to see whether
a project is actually reachable, not just “running”.
Git card
Section titled “Git card”A summary from mdocker git info <name> --json — branch, dirty counts, ahead/behind, stash,
and (expanded) the last commit, remote URL and worktrees.
Shopware card
Section titled “Shopware card”For Shopware projects (shopware-dockware profile), shows the shop version, warns about
APP_URL drift, and offers buttons for cache clear, build, and the sales-channel domain
sync wizard. See Shopware Workflows.
AI-Sessions card
Section titled “AI-Sessions card”The project’s sessions with their live status, a button to start a new one and a reload button. Opening a session attaches an embedded terminal — see Attached Terminals.
“Services” tab
Section titled ““Services” tab”One accordion per compose service showing state, ports, environment variables (with secret masking) and a ready-to-copy connection string for databases — see Accessing Databases from the Host — followed by a database card with snapshots and dump/restore actions. While the project is stopped the database card says “Projekt ist gestoppt - keine Container vorhanden.”
“Tickets” tab
Section titled ““Tickets” tab”A master-detail view over the Spedy board assigned to the project: a 320 pt list on the left with the header “Tickets”, a counter and a “Tickets neu laden” button, and the ticket detail on the right.

- Nothing selected yet: “Ticket auswählen”.
- Board assigned but nothing open: “Keine offenen Tickets”.
- No board yet: the “Spedy-Board” card plus the hint “Sobald ein Board zugewiesen ist, erscheinen die offenen Tickets hier.”
Tickets are re-polled every 120 s, but only while the “Tickets” tab is visible. A
.ticket deep link opens the project, switches to this tab and selects the ticket.
“Einstellungen” tab
Section titled ““Einstellungen” tab”The per-project settings cards, in this order:
| Card | What it does |
|---|---|
| “Hostnames” | Add, remove and open the project’s hostnames. Changes re-render the override and may regenerate the certificate and restart the router. |
| “Routing” | Web routing per service (port, scheme) and the project’s profile. The header button „Override neu generieren“ rebuilds the override from the current compose file, for example after you removed a service; the same action sits in the „…“ menu of the project header. |
| “Pfade” | The “AI-Pfad” a session starts in and the “Editor-Pfad” the editor opens. |
| “Spedy-Board” | Assign or remove the Spedy board whose tickets fill the “Tickets” tab. |
| “Demo-Link (öffentlich)” | Start, copy, open and stop a public cloudflared demo tunnel. |
| “Gruppe” | The sidebar group of this project. Empty means no group. |
| “Details” | Registry facts about the project. |
| “Projekt” | Rename the project or remove it from the list. |

Toolbar, menubar and console
Section titled “Toolbar, menubar and console”- The toolbar carries a Doctor button, refresh, settings, and the EDGE badge — a constant “EDGE” label that’s green when the edge stack is up and red when it’s down. Clicking it toggles the edge stack (remember: taking it down stops all projects).
- The app also lives in the menubar as a compact popover with the project list and quick toggles.
- A collapsible console at the bottom records every command the app ran, its output,
exit code and duration — handy for seeing exactly which
mdockercall a click triggered. Drag its top edge to resize it (double-click resets), search it, filter by errors or project, and copy or re-run an entry via hover buttons or the context menu.