mq-dir vs Finder: when the default isn't enough

Finder shipped in 1984. It's the file manager 95% of macOS users need, and the one Apple keeps adding modest improvements to. It's also the one that quietly bottlenecks specific workflows — without ever quite breaking enough to feel "wrong."

This post is for the user who has hit those bottlenecks and wants to know if mq-dir actually fixes them before installing.

Where Finder is genuinely fine

Be honest first: Finder works for most things.

• Single-folder navigation: ⌘O, type a path, navigate. Excellent.
• AirDrop: not replaceable. Finder owns this.
• Drag from other apps to file system: deeply integrated. Other file managers can't fully replace this.
• macOS Tags / Smart Folders / Stacks: native features, work everywhere.
• iCloud Drive integration: smoother than any third party.
• Default for system dialogs: Save panels, attachments, Open dialogs — Finder is the model.

If your workflow is mostly the above, mq-dir doesn't do much for you. Stay with Finder.

Where Finder bottlenecks specific workflows

If you're considering an alternative, you've probably hit at least 2-3 of these:

State doesn't survive relaunches

Open Finder, navigate to ~/Downloads, sort by date descending, scroll to a specific file. Quit Finder. Reopen. Default sort, scroll reset, wrong folder.

You can pin a folder, set its default view, and survive some of this. But scroll position, selection, and complex multi-window state genuinely don't persist reliably.

For a developer running 5 sessions with 5 working directories, this is daily friction.

No quad-pane

Cmd+T gives tabs in a single window. Tabs share a focused state — only one is active. There's no native way to have 4 functional folder views side-by-side with ⌘1–4 to focus each.

You can simulate it with 4 Finder windows tiled with Magnet/Rectangle, but they're independent — no shared sidebar, no focus routing, no state coupling.

Preview is window-scoped

Finder's preview pane (right-click → Show Preview) is one per window. If you want to compare 4 different files visually, you need 4 windows, each with preview enabled. Manageable but cumbersome.

Per-tab tree view absent

Finder has list, icon, column, gallery views. None is a per-tab toggleable file tree (VS Code-style). For developers, this is a big absence — code navigation often wants the tree pattern.

Tabs don't have first-class state

Finder tabs are window-level conveniences, not durable state containers. You can reorder them, but they don't reliably restore exact view + scroll on relaunch.

What mq-dir specifically adds

Up to 4 panes per window

⌥⌘1 / ⌥⌘2 / ⌥⌘3 (split horizontal) / ⌥⌘4 switch layout instantly. The off-screen panes preserve state when you shrink layout — go 4 → 1 → 4 and the panes return as they were.

Per-pane tabs

Each pane has its own tab strip. ⌘T makes a tab in the focused pane. Tabs stay with their pane.

Religious state persistence

Folder, sort order, scroll position, focus, hidden file toggle, column widths, preview visibility, expanded tree nodes — all persisted, all survive force-quit. Every Codable struct hand-rolls init(from:) with decodeIfPresent defaults; every schema bump has a migration test (CONTRIBUTING.md enforces this).

Result: you can close mq-dir mid-task, reopen tomorrow morning, you're at the exact pixel position you left.

Per-tab preview + tree view

Each tab independently controls whether preview is on (and what file is selected) and whether tree view is shown. Two tabs in one pane can have entirely different layouts.

Projects (named workspaces)

Save your current quad-pane setup as "Linear bug bash" or "agent dev." Switch projects in one click — the outgoing project auto-saves, the incoming one restores exactly. Finder has no equivalent.

cmux integration

If you use cmux (multi-session terminal multiplexer), mq-dir's sidebar mirrors your sessions. Click a session row to open its working directory in the focused pane. Niche but powerful for AI multi-tasking.

Markdown preview with full GFM

Open a .md file in mq-dir's preview pane and you get full GitHub-Flavored Markdown rendering — tables, code blocks, task lists, fenced code with syntax highlighting. Finder's preview is QuickLook plain.

What Finder still wins

Don't oversell. After daily-driving mq-dir, these still belong to Finder:

• AirDrop.
• Drag-from-Mail-message-to-Desktop and similar deep app integrations.
• iCloud Drive sync indicators and the "Optimize Mac Storage" UI.
• Tags-as-color-on-icon display in some contexts.
• macOS Open/Save dialogs (those are essentially mini-Finder; mq-dir can't intercept them).

Most users keep Finder accessible for these and run mq-dir as the daily navigator.

When to switch (and when not to)

Switch to mq-dir if any of these is a daily friction:

• 3+ projects open in parallel and you alt-tab between Finder windows.
• AI agent fleet (Claude Code, Cursor sessions) producing artifacts in 4+ folders.
• You miss your scroll position every time you relaunch.
• Markdown files you preview daily and want to actually render, not just plain-text.
• Cmux user.

Stay with Finder if:

• One project at a time, occasional file management.
• Heavy AirDrop user.
• Family Mac, casual use.
• You haven't actually felt the friction.

The right answer for many readers is "stay with Finder until you feel the bottleneck." Don't preemptively switch; the cost of moving for a workflow you don't have is real.

Coexistence

The realistic pattern:

• Set mq-dir as your default for Cmd+Click → "Show in [file manager]" via Finder Preferences for power users (or just Cmd+Tab to it).
• Keep Finder accessible for AirDrop and system dialogs.
• Two apps, complementary roles.

Verdict

Finder is excellent for the median macOS user. mq-dir is the answer when specific workflows — parallel projects, AI agent fleets, religious persistence — push past Finder's design limits. Neither replaces the other entirely.

mq-dir is free, MIT, zero telemetry. Try it for a week alongside Finder; you'll know within days whether it earns a permanent spot in your dock.