1.8.0: Enter’s behaviour is configurable
As of 2026-07-24. A snapshot; follow the links for what changed since.
If Shift+Enter submits instead of adding a line
Who needs to act: anyone for whom Shift+Enter submits in MulmoTerminal — equivalently, a bare Enter drops to a new line instead of sending.
Whether Enter submits or inserts a newline is decided by Claude Code, from the bytes the terminal sends it — not by MulmoTerminal. Some people rebind Claude Code the other way round, and there the behaviour is reversed.
How to set it
-
Add this to
~/.mulmoterminal/config.json:{ "terminalSubmit": "esc-cr" } - Reload the browser tab (the keyboard reads the value at page load).
- Restart the server (the phone remote view’s send reads it at startup).
- Check: a bare Enter submits, Shift+Enter adds a line.
Almost nobody needs this. The default "cr" is the standard binding, and an invalid value falls back to it, so a typo cannot leave Enter broken.
Claude sessions only — shell, codex and command cells always submit with a plain Enter. An IME candidate-confirm Enter is never intercepted.
→ Configuration → Enter: submit vs. newline
More default header buttons
The starter set gained 📁 browse files, 🖥 new terminal here, 🔗 this branch’s PR (git repos, only when a PR exists), and 🌐 open on GitHub. Nothing to configure — but note that setting buttons yourself replaces the whole default set.
→ Configuration → Customizing the header
Also
- File paths in terminal output became links (1.11.0 later made them open by extension).
- More scrollback survives a reconnect (64 KiB → 1 MiB, roughly 1000 lines).
- The zoomed view-toggle no longer covers a cell’s ✕ or the Settings button.
- A guide page for the cross-repo PR/Issue view → GitHub