Quad-pane file managers compared: when 4 panes beats 2 (or 1)

Two-pane file managers come from 1986 — Norton Commander, Total Commander, Far. The workload was: copy from left to right. The shape fit the work. The work was sequential, file-system-centric, single-task.

Modern AI-adjacent dev work is none of those things. It's parallel, mixed (source plus artifacts), and you're holding three projects open at once. The pane count needs to follow.

Three workloads, three pane counts

Workload A: copy/move/sync

"I need to move 200 files from Downloads to project/assets, then rename them."

Right pane count: 2. Source pane, destination pane. This is what dual-pane was built for and it's still the best shape. mq-dir's 2H and 2V layouts cover this; so do Forklift, Marta, Commander One.

A third pane adds nothing: you're not pulling from a third location. Two panes, focused on each other.

Workload B: research / synthesis

"I'm reading 12 papers, taking notes, writing a summary."

Right pane count: 4. Sources + references + scratch + output. Each pane is a phase of the work and you flip between them rapidly. We covered this in detail in the 4-pane research workflow.

Two panes here means you're constantly re-pinning one of them as you switch between phases. The friction adds up to about 15 seconds every time you swap, hundreds of times an hour.

Workload C: parallel projects / AI sessions

"I'm running three Claude sessions, each on a different repo, plus watching their output folders."

Right pane count: 4. One pane per project + one for whatever's currently producing artifacts. The thesis: each session's working tree should always be visible, never hunted-for.

This is the workload mq-dir was specifically built for. The win isn't display real estate; it's that you stop alt-tabbing to find which folder is which.

What actually breaks at higher pane counts

Tested honestly — what fails at each step:

1 pane

• Breaks at: needing to compare two folders, copy between them, watch an artifact stream while editing.
• Mitigation: Cmd+T tabs. Works for sequential work; fails when work is parallel.

2 panes

• Breaks at: a third project entering the picture, or a workflow that has more than two phases.
• Mitigation: Cmd+T per pane (each pane has its own tabs). This buys a lot of headroom — Forklift users live here for years.

4 panes

• Breaks at: very small displays (<13"), sessions that don't actually have four contexts.
• Mitigation: dynamic layout — drop to 2 panes when you don't need 4. mq-dir's ⌥⌘1–4 switches layout in one keystroke, preserving the off-screen pane state for later.

6+ panes

• Breaks at: human attention. Each pane below 320px wide stops being scannable.
• Mitigation: there isn't a great one. Better to use four panes plus tabs than six panes.

How quad-pane apps differ

Even within the "4 panes" category there are real choices:

The "shared sidebar" point is underrated. With four Finder windows you have four sidebars; with mq-dir you have one. Click a Favorites entry, it opens in the focused pane. The sidebar becomes a router.

When not to use four panes

Be honest about your workload:

• You only have one project open at a time → 1 or 2 panes is enough.
• You're a heavy SFTP/server user → Forklift's 2-pane is more polished here than mq-dir's 4-pane (which is local-first).
• You hate keyboard navigation → quad-pane apps lean on Cmd+1–4. If you'd rather click, the value drops sharply.

The "default to 2, escalate to 4" pattern

This is what most mq-dir users land on after a month:

1. Cold-launch in 2H (two panes side by side) for everyday work.
2. Hit ⌥⌘4 when a session goes wide — three projects, research, AI agents.
3. Hit ⌥⌘1 for focused single-pane writing.

The layout follows the work, not the other way around. The off-screen pane state is preserved when you shrink, so going 4 → 1 → 4 returns the panes to where they were.

Try the cheapest test

If you've never used four panes, the way to know if it fits: open mq-dir, set ⌥⌘4, pin four directories you actually use. Work in it for two days. If you find yourself manually shrinking back to one, two-pane is your shape — and that's a real answer, not a smaller answer.

Most people who run AI sessions in parallel don't shrink back. Free, MIT-licensed, no telemetry.