# A Browser With a Built-in Terminal for Web Developers

> Why a browser with a built-in terminal helps web developers: your own shell in a pane next to the page, links from its output that open in tabs, and safety.

Canonical: https://monok.io/blog/browser-with-built-in-terminal.md

[Design](https://monok.io/blog/category/design)

Nemo · October 20, 2026 · 3 min read

Web development is a loop between two windows: a terminal running the dev server and a browser showing the result. A browser with a built-in terminal folds that loop into one window. In Monok, a terminal is a pane: press Ctrl+` and one splits in below the page, running your own login shell. Cmd+click a localhost link in its output and it opens in a tab. It is in the [current release](https://monok.io/download), version 0.1.0.

## What does the terminal do?

| Feature | What it means |
|---|---|
| Terminal panes | Ctrl+` splits a terminal in below the page and moves the keyboard to it; press it again to go back to the page |
| Your own shell | Your login shell with your .zshrc, so your prompt, aliases and version managers load as they do in Terminal; Settings › Terminal can pick another shell from the system’s list |
| Panes like tmux | Cmd+D splits right, Shift+Cmd+D splits down, Option+Cmd+arrows move the focus, Shift+Cmd+Return zooms a pane |
| `>command` in the Magic Bar | In an empty pane, type `>npm test` in the [Magic Bar](https://monok.io/blog/minimalist-browser-no-address-bar) and press Return: that pane becomes a terminal and runs it |
| Links | Cmd+click on `http://localhost:5173` in the output opens it in a browser tab |
| Find | Cmd+F searches the terminal’s scrollback |
| Open a folder | File › Open Folder in Terminal (Shift+Cmd+O) starts a terminal pane in the folder you pick |

Pane layouts come back with the session. A terminal comes back as an empty pane, because a shell only starts when you ask for one.

## Why put a terminal in a browser?

Because switching windows is the most common thing a web developer does, and every switch breaks a little concentration. With the dev server in a pane under the page you start it, watch it compile, open the URL and look at the result in the same tab. It fits the rest of the design: chrome that stays out of the way and a [keyboard-first flow](https://monok.io/blog/keyboard-shortcuts-mac-browser).

It is a real terminal, not a toy console: input methods and dead keys work, Cmd+C and Cmd+V copy and paste, Cmd+K clears, and each terminal has its own font size.

## Is a terminal in a browser safe?

This is the question that matters, so the boundary is simple: **the terminal is native browser chrome, and web pages can never reach it.** No JavaScript API opens it, reads its output or types into it, and neither do the browser’s own `browser://` pages. Typing or pasting `>command` never runs anything; only your own Return key does. A terminal starts on four actions only: Ctrl+`, the Magic Bar, the menu command and Open Folder in Terminal, and the browser’s tests check that nothing else in the code can start one.

Cmd+click on a link in the terminal opens a normal tab, the same as typing the address yourself.

## Who is it for?

Mostly people who build for the web: front-end developers running Vite, Next.js or Angular dev servers, and anyone who keeps a terminal open next to the browser all day. If you never open a terminal, you never see it: there is no button for it in the interface, only the shortcut and the menu.

## FAQ

### Is the terminal available now?

Yes, in version 0.1.0. The [download](https://monok.io/download) is for macOS 14 or later.

### Can a website run commands in my terminal?

No. The terminal is part of the browser’s own interface and is never exposed to web pages or JavaScript.

### Does it cost much memory?

Measured on an M5 Pro, the app process uses 46 to 47 MB with a page, a terminal pane and an empty pane open, and 49 MB with one terminal filling the window. WebKit’s processes for the page are separate. The [lightweight browser guide](https://monok.io/blog/lightweight-browser-for-mac) explains how to measure.

Early preview · macOS

Monok is a small Mac browser with a native terminal and a file manager.

Magic Bar, tmux-style panes, your own shell and ad blocking built in. Free while in preview.

 [Go to the download](https://monok.io/download)

**About this article.** Written by Nemo, who is building Monok. Performance numbers here are v1 targets unless a post says they were measured, and on what. Spotted something wrong or out of date? [Tell us](mailto:support@monok.io).

More in Design

[Design](https://monok.io/blog/category/design) Oct 22, 2026 · 4 min

## [A Minimalist Browser With No Address Bar](https://monok.io/blog/minimalist-browser-no-address-bar)

Why a minimalist browser can drop the address bar: how the Magic Bar on Cmd+L replaces it, what you lose, what you gain, and how tabs and panes fit in.

[Files](https://monok.io/blog/category/files) Oct 28, 2026 · 4 min

## [How to Show Hidden Files on Mac: Finder and Terminal](https://monok.io/blog/show-hidden-files-mac)

How to show hidden files on a Mac: the Finder shortcut Cmd+Shift+Period, the Terminal command that keeps them visible, and how to reach the Library folder.

[Web Platform](https://monok.io/blog/category/web-platform) Oct 27, 2026 · 3 min

## [The Web APIs React and Angular Apps Need From a Browser](https://monok.io/blog/web-apis-react-angular-need)

Which Web APIs React and Angular apps need from a browser: the DOM, events, microtasks, timers, fetch, history and observers, the bar a new engine must clear.