How to Open Crosh: Chrome OS Shell Access Explained
If you've ever wanted to peek under the hood of a Chromebook, Crosh is your entry point. It's Chrome OS's built-in command-line interface — a lightweight shell that gives you access to system diagnostics, network tools, and developer-level controls that aren't available through the standard settings menu.
What Is Crosh?
Crosh stands for Chrome Shell. Think of it as Chrome OS's version of Terminal on macOS or Command Prompt on Windows — but intentionally more restricted. Google designed it to be accessible without enabling full developer mode, which means most users can open and use basic Crosh commands safely, without risking their system's security or voiding their warranty.
It runs directly inside the Chrome browser as a tab, not as a separate application window. That design choice reflects Chrome OS's browser-centric architecture — almost everything happens within or alongside Chrome.
How to Open Crosh 💻
Opening Crosh is straightforward and works on any Chromebook running Chrome OS:
- Press
Ctrl+Alt+Tsimultaneously
That's it. A new browser tab will open with the Crosh prompt, displaying:
Welcome to crosh, the Chrome OS developer shell. crosh> From here, you can type commands and press Enter to execute them.
Does It Work on All Chromebooks?
Yes — the Ctrl + Alt + T shortcut is universal across Chrome OS devices, regardless of manufacturer (Acer, Lenovo, HP, Samsung, ASUS, etc.) or the age of the device. As long as the device is running a functional version of Chrome OS, Crosh will open.
If the shortcut doesn't seem to work, check whether:
- You're pressing the keys simultaneously, not in sequence
- A keyboard shortcut hasn't been remapped through accessibility settings
- The Chromebook is in a managed/enterprise environment where the shell may be restricted by a system administrator
What Can You Do Inside Crosh?
Crosh supports a range of commands, though its scope is intentionally narrower than a full Linux shell. Here are some commonly used ones:
| Command | What It Does |
|---|---|
help | Lists all available Crosh commands |
ping [address] | Tests network connectivity to a host |
tracepath [address] | Shows the network path to a destination |
top | Displays running processes and resource usage |
battery_test | Runs a battery discharge test |
memory_test | Checks RAM for errors |
ssh | Opens a secure shell connection to another machine |
shell | Drops into a full bash shell (requires Developer Mode) |
The shell command is worth noting separately — it unlocks a much more powerful Linux environment, but it only works if Developer Mode is enabled. Without Developer Mode, typing shell returns an error. This is by design.
Crosh vs. Linux Terminal on Chrome OS
Newer Chromebooks support Linux (Beta) — also called the Crostini environment — which gives you a full Debian-based Linux terminal alongside Chrome OS. This is different from Crosh.
| Feature | Crosh | Linux Terminal (Crostini) |
|---|---|---|
| Requires Developer Mode | No | No (on supported devices) |
| Full Linux commands | No | Yes |
| Install Linux apps | No | Yes |
| System-level access | Limited | Broad |
| How to open | Ctrl + Alt + T | Settings → Advanced → Developers → Linux |
If you're trying to run Linux software or use tools like apt, git, or python, Crosh alone won't get you there — the Linux Terminal environment is the right path. If you just need quick diagnostics or network testing, Crosh handles that without any extra setup.
Developer Mode and the shell Command
Enabling Developer Mode on a Chromebook is a significant step. It allows the shell command inside Crosh to work, giving you root-level bash access. However, it also:
- Wipes all local data during the transition (a full powerwash occurs)
- Displays a warning screen on every boot
- May disable some enterprise-managed policies
- Can affect access to certain DRM-protected content
The process involves holding Esc + Refresh + Power to enter recovery mode, then pressing Ctrl + D to enable Developer Mode. Different Chromebook models can have minor variations in this process, so checking device-specific documentation is worthwhile before proceeding.
When Crosh Behaves Differently 🔧
A few variables affect what you'll see and what you can do:
Managed Chromebooks — Devices enrolled in a school or business domain may have Crosh disabled entirely, or have specific commands blocked by the administrator's policy. If the Ctrl + Alt + T shortcut does nothing, or if commands return policy-blocked errors, this is likely the reason.
ChromeOS version — Older versions of Chrome OS may have a slightly different command set available. Google updates the shell periodically, adding or deprecating commands. The help command always reflects what's currently available on your specific build.
Guest mode — Crosh is accessible in guest mode, but some commands that interact with user data or system state may behave differently or return limited results.
The Bigger Picture
Crosh sits at an interesting intersection — accessible enough for curious everyday users who want to run a quick ping test or check battery health, but shallow enough that it doesn't expose the full system to accidental damage. The shell command behind the Developer Mode gate is where things get genuinely powerful, and genuinely consequential.
Whether the basic Crosh toolset covers what you need, or whether the full Linux Terminal or Developer Mode access makes more sense, depends entirely on what you're trying to accomplish — and how comfortable you are with the tradeoffs each path brings.