How to Open Crosh: The Complete Guide to Chrome OS's Built-In Terminal

If you've ever wanted to dig deeper into your Chromebook's system, run network diagnostics, or access developer-level tools, Crosh is your entry point. It's Chrome OS's built-in shell environment — and opening it takes just seconds once you know where to look.

What Is Crosh?

Crosh stands for Chrome Shell. It's a command-line interface built directly into Chrome OS, giving users access to a range of system tools, diagnostic commands, and network utilities without needing to enable full Linux or developer mode.

Think of it as a lightweight terminal — less powerful than a full Linux shell, but far more accessible. It runs entirely within the Chrome browser environment, which means no special setup is required for basic use.

Crosh is not the same as the Linux terminal available through Chrome OS's Linux development environment (Crostini). Crosh operates at a different layer and serves a different purpose, primarily system diagnostics and network testing.

How to Open Crosh on a Chromebook 💻

Opening Crosh is straightforward and works on virtually every Chromebook running Chrome OS.

Step 1: Make sure you're on your Chromebook and Chrome OS is active (not in a Linux environment or Android app).

Step 2: Press the keyboard shortcut:

Ctrl + Alt + T

Step 3: A browser tab will open with a dark terminal interface. You'll see a prompt that reads:

Welcome to crosh, the Chrome OS developer shell. 

That's it. You're in Crosh.

What If the Shortcut Doesn't Work?

In rare cases, keyboard remapping or accessibility settings can interfere with the shortcut. If Ctrl + Alt + T doesn't open Crosh, try these alternatives:

• Open the Chrome browser manually, then type chrome://crosh directly into the address bar and press Enter
• Check your keyboard settings to confirm the shortcut hasn't been reassigned
• Restart the Chromebook and try again — some session states can block terminal access

Basic Crosh Commands Worth Knowing

Once you're inside Crosh, typing help displays the available command list. A few commonly used commands include:

The shell command deserves a note: it only works if your Chromebook is in Developer Mode. Attempting it on a standard Chrome OS device will return a permissions error. This is intentional — Google restricts deeper shell access by default for security reasons.

Crosh vs. the Linux Terminal: Understanding the Difference

Many Chromebook users confuse Crosh with the Linux terminal available through the Settings > Advanced > Developers section. These are distinct environments:

Crosh is a restricted shell that runs within Chrome OS itself. It doesn't require enabling any additional features and is designed primarily for diagnostics. The command set is limited by design.

The Linux terminal (via Crostini) is a full Debian-based Linux environment that runs in a container alongside Chrome OS. It gives you access to apt, bash, and the full Linux ecosystem — but it must be explicitly enabled in settings and takes up additional storage.

If your goal is simply to run a ping test, check battery health, or SSH into another machine, Crosh handles that without any extra configuration. If you need to install Linux software, run Python scripts, or use developer tools like Git or npm, the Linux terminal is the appropriate environment.

Factors That Affect Your Crosh Experience

Not every Crosh session is identical. Several variables influence what you can do inside the shell:

Chrome OS version: Google updates Chrome OS on a regular release cycle. Some Crosh commands have been added, changed, or deprecated across versions. The command available in your session reflects your current OS build.

Managed vs. personal devices: Chromebooks managed by a school or enterprise organization through Google Admin Console may have Crosh access restricted or disabled entirely by the administrator. On managed devices, the Ctrl + Alt + T shortcut might be blocked at the policy level, not the OS level.

Developer Mode status: As noted, the shell command — which escalates Crosh to a full bash environment — only works when Developer Mode is active. Enabling Developer Mode involves a powerwash (factory reset) of the device and removes security features like verified boot. It's not a decision to take lightly.

Hardware generation: Older Chromebooks running legacy Chrome OS builds may have a slightly different Crosh command set or interface behavior compared to current models. The core shortcut and basic commands remain consistent, but edge cases exist.

What Crosh Can and Can't Do 🔧

It helps to go in with accurate expectations.

Crosh can:

• Run network diagnostics (ping, tracepath, connectivity checks)
• Monitor system processes in real time
• Test battery behavior
• Establish SSH connections
• Access basic hardware diagnostic tools

Crosh cannot (without Developer Mode):

• Install software
• Modify system files
• Access the full filesystem
• Run arbitrary scripts or executables

The shell is intentionally sandboxed. Chrome OS prioritizes security and simplicity, and Crosh reflects that philosophy — useful for diagnostics, not a replacement for a full development environment.

Why Your Use Case Changes Everything

Opening Crosh takes one keyboard shortcut. What you do inside it depends entirely on why you're there.

A student troubleshooting a slow school Wi-Fi connection has different needs than a developer testing SSH access to a remote server. A user on a personally-owned Chromebook has options that someone on a district-managed device simply doesn't. And someone comfortable enabling Developer Mode is working in a fundamentally different environment than someone who wants to stay on the default, secure Chrome OS setup.

The tool itself is consistent — how far it takes you depends on your device's configuration, management status, and how deep you need to go.