You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Configurable defaults for a new workspace: terminal pane count and browser start URL #212
I use wmux for multiple projects, and two startup behaviors force manual work every time I start a session:
New workspaces open with a hard-coded number of terminal panes. When I create a workspace, it opens exactly 3 terminal panes (T-shaped: 2 top + 1 bottom). Even when I want fewer or more, or a different arrangement, I have to re-split and re-arrange manually every time. wmux new-workspace via the CLI is inconsistent too — it opens a single pane instead.
The built-in browser panel opens blank. When I toggle the browser panel (Ctrl+Shift+I), it has no default page, and I have to type/click my usual starting URL each time.
I looked for settings for both and could not find them.
What would you like wmux to do?
Add two configurable defaults, ideally in ~/.wmux/config.toml following the existing [terminal] / [remote] / [keys] pattern:
Default terminal pane count / layout for a new workspace. A simple option to control how many terminal panes a fresh workspace starts with (and, if possible, how they are arranged), e.g.:
[workspace]
panes = 3 # default terminal panes in a new workspace
layout = "grid" # single | grid | left | down (optional)
This should apply consistently to the sidebar "+" button and wmux new-workspace (which currently opens a single pane), so the count is no longer hard-coded.
Default browser start URL. A page the built-in browser panel opens to when it is first shown for a new workspace, e.g.:
[browser]
default-url = "http://localhost:3000"
Empty / unset should keep the current behavior (blank page). This is the start page, distinct from the existing default search engine.
What do you do today instead?
I press Ctrl+D / Ctrl+Shift+D and drag dividers to rebuild my layout after every new workspace.
I navigate the browser panel to the URL I want each time.
I can partially work around the pane-count gap with the Saved Layouts → set as Default feature, but that is a heavier flow and the CLI still opens a single pane regardless; there is no simple config value for "how many panes should a new workspace start with".
Both shipped in 2.8.0. You'd found a real inconsistency, and half of the second one turned out to be a bug rather than a missing feature.
Pane count and layout
[workspace] in ~/.wmux/config.toml, close to what you proposed:
[workspace]
panes = 3# 1-8layout = "grid"# grid | columns | rows | left | down | single
layout
grid
balanced rows — at 3 panes this is exactly the T you have today. Default.
columns
all side by side
rows
all stacked
left
one full-height pane on the left, the rest stacked to its right
down
one full-width pane on top, the rest side by side below
single
shorthand for panes = 1
Also in Settings → Workspace → New Workspace, so it isn't config-file-only.
You were right that the hard-coding was the problem, and it was worse than it looked from outside: the shape was decided in two places that disagreed, because the resolver took it as a parameter that each caller filled in differently. There is now one resolution, ranked — a saved layout marked Default first (it also carries each pane's shell, cwd and startup commands, so it answers the same question more completely), then this setting.
wmux new-workspace now follows it too, which is the consistency you asked for and does mean the CLI changes from one pane to three. wmux new-workspace --panes 1 (or --layout single) pins the old shape for a script that depends on it, and --panes/--layout win over the config either way.
panes is capped at 8 — not a technical limit, just that the value comes from a hand-edited file and over the pipe, and every pane it makes spawns a shell. Out-of-range is clamped and reported by wmux config show, rather than silently doing something else.
Browser start page
[browser]
default-url = "http://localhost:3000"
Also in Settings → Browser → Start page. A scheme is required: a bare localhost:3000 is refused with an explanation, because a webview handed one loads nothing and says nothing at all.
One correction to the issue, and it's in your favour. You wrote that empty/unset should keep the current blank-page behaviour — but blank was never the intended behaviour, it was a bug. A workspace that has never opened its browser is saved with browserUrl: '', and '' is a value: it defeated the default parameter the panel already had. So a new workspace showed wmux's page and a restored one showed nothing, which is what you were hitting. Empty now means "wmux's own page" for both, consistently. If you actually want a blank panel, default-url = "about:blank" says so explicitly.
Thanks for a precise, well-scoped report — the "I looked for settings for both and could not find them" line is the part that made it obvious this was one issue and not two.
Activity
feat(workspace): pane count, arrangement and browser start page are s…
amirlehmam commentedon Sep 1, 2026
Both shipped in 2.8.0. You'd found a real inconsistency, and half of the second one turned out to be a bug rather than a missing feature.
Pane count and layout
[workspace]in~/.wmux/config.toml, close to what you proposed:layoutgridcolumnsrowsleftdownsinglepanes = 1Also in Settings → Workspace → New Workspace, so it isn't config-file-only.
You were right that the hard-coding was the problem, and it was worse than it looked from outside: the shape was decided in two places that disagreed, because the resolver took it as a parameter that each caller filled in differently. There is now one resolution, ranked — a saved layout marked Default first (it also carries each pane's shell, cwd and startup commands, so it answers the same question more completely), then this setting.
wmux new-workspacenow follows it too, which is the consistency you asked for and does mean the CLI changes from one pane to three.wmux new-workspace --panes 1(or--layout single) pins the old shape for a script that depends on it, and--panes/--layoutwin over the config either way.panesis capped at 8 — not a technical limit, just that the value comes from a hand-edited file and over the pipe, and every pane it makes spawns a shell. Out-of-range is clamped and reported bywmux config show, rather than silently doing something else.Browser start page
Also in Settings → Browser → Start page. A scheme is required: a bare
localhost:3000is refused with an explanation, because a webview handed one loads nothing and says nothing at all.One correction to the issue, and it's in your favour. You wrote that empty/unset should keep the current blank-page behaviour — but blank was never the intended behaviour, it was a bug. A workspace that has never opened its browser is saved with
browserUrl: '', and''is a value: it defeated the default parameter the panel already had. So a new workspace showed wmux's page and a restored one showed nothing, which is what you were hitting. Empty now means "wmux's own page" for both, consistently. If you actually want a blank panel,default-url = "about:blank"says so explicitly.Thanks for a precise, well-scoped report — the "I looked for settings for both and could not find them" line is the part that made it obvious this was one issue and not two.
amirlehmam commentedon Sep 1, 2026
Released in v2.8.0.
feat(browser): make dev-server auto-open a persisted pref, default off (
fix(worktree): branch from the caller's repository and validate refs