Locked-device guide

How to Code on a School Chromebook When Linux Is Locked and You Can’t Install Anything

Your school greys out the Linux toggle and blocks the Play Store. Here’s how to actually learn to code on the machine you have — no installs, no admin rights, no waiting for permission.

A student typing Python into a browser code editor on a small school Chromebook, seen over the shoulder in a classroom.
A browser tab is the whole setup. No Linux, no admin password. Photo: Coodeverse.

You found the tutorial. You followed it. You went to Settings → About ChromeOS → Developers, and the Linux toggle is grey. Maybe it isn’t even there. Maybe you got as far as “open a terminal” before discovering there is no terminal to open.

Then the article you’re reading tells you to sudo apt install python3, as though that settles it.

It doesn’t settle it. Most Chromebook coding guides are written by people on personal machines, for people on personal machines. Roughly a third of the way down, one of them admits the problem in a footnote — if you use this at school, you might not be able to use Linux — and then keeps going. The advice never changes.

So here is the version written for the machine you actually have: school-managed, locked, no admin rights, and no way to ask the IT department for anything before Friday.

At a glance

Who this is forStudents on a school-issued Chromebook with an admin-locked device
What you needA browser tab and about 90 seconds
What you don’t needLinux, developer mode, admin rights, an account, money, a different laptop
Languages that genuinely workAll eleven worth learning, with honest caveats per language
Time to first working programUnder two minutes
Advertisement

First, find out how locked you are

There are three tiers. Find yours before reading further — the advice differs, and one tier makes most of this unnecessary.

ChromeOS settings screen showing the Linux development environment option greyed out, with a policy notice reading that the device is managed by a school.
The greyed toggle. On a managed device this is not a bug and not something you can click through. Screenshot: Coodeverse.
Tier 1

Nobody manages this machine

You bought it, or your family did. Linux works. Install a real toolchain. Skip ahead.

Tier 2

Managed, Linux disabled

This is the common case on school devices. Open chrome://management in a tab. If it says the device is managed, you’re here. Everything below applies.

Tier 3

Managed, Play Store restricted, filter active

Same as Tier 2, plus a filtering proxy that blocks domains. Everything below applies, and you’ll also want the school filter section.

Diagram of the three lockdown tiers: unmanaged device, managed with Linux disabled, and managed with an active web filter.
Find your tier in sixty seconds, then read only the part that applies. Diagram: Coodeverse.

Sixty seconds of checking:

  1. Go to Settings → About ChromeOS → Developers. Is “Linux development environment” present? Greyed? Missing?
  2. Open chrome://management. Does it report the device as managed?
  3. Try to open the Play Store. Does it load, or show a policy notice?
  4. Press Ctrl + Alt + T. Does a terminal open, or does it say “no Crostini”?

If you got a terminal, stop reading and install things. Everyone else: the whole article below assumes you can install nothing, and that’s fine.

The one-tab setup

Browser-based compilers exist, they’ve existed for years, and they need nothing from your device except a tab. No Linux container, no policy exception, no admin password. Your school can grey out the toggle but it cannot grey out JavaScript running in a renderer.

That isn’t a workaround with sharp edges — it’s how a meaningful share of the world’s beginner code already runs. Snippets in tutorials, coding-interview screens, classroom exercises: browser sandbox, no install.

A Chromebook with the screen split into two halves: a free Python course on the left and a browser code editor on the right.
Course left, compiler right. Two tabs, split with Alt + [ and Alt + ], and that is your entire IDE. Screenshot: Coodeverse.

Open one now. Python compiler. Paste this:

name = "you"
for i in range(3):
    print(f"Still here, {name}? Good.")

Run it. Three lines of output. That’s the entire setup section, and you’ve already finished it.

Then pin the tab — Ctrl + Shift + T reopens it if you lose it, or right-click → Pin — and keep a second tab open with the matching free course. Two tabs is your whole IDE.

What actually runs, language by language

Most “you can’t code on a Chromebook” advice is roughly true for professional work and wildly overstated for learning. Here’s the honest split.

LanguageOn a locked ChromebookThe limit
HTML / CSSFully learnableNone. This is what the browser is for.
JavaScriptFully learnableNone for learning.
SQLFully learnableSample tables only; no real database server
DSAFully learnableLanguage-agnostic; the compiler is enough
PythonLearnable to a solid levelNo pip install, no packages, no local files
TypeScriptLearnableNo tsc --watch; one file at a time
CLearnable for syntax and algorithmsNo real toolchain, no gdb
C++Same as C, and more painfulNo debugger, no build system
C#Syntax and LINQ learnableNo Unity, no desktop apps
KotlinSyntax, coroutines, OOP learnableNo Android build, no Gradle
Advertisement

The pattern: the languages that live in a browser tab are the ones whose tooling is a browser tab. Everything else you can learn, and you’ll hit a wall later — a real one, but a later one, and hitting it in six months beats not starting because the toggle is grey.

If you want to be strategic about it, start with HTML → CSS → JavaScript. Nothing about that path requires a single install, ever, and it’s the one with the most entry-level jobs attached. Add Python alongside it if you want the data side.

Surviving an 11-inch screen

A school Chromebook is small, low-resolution, and has a keyboard with no function row. These are real obstacles, not vanity ones. Fix them.

Split the screen properly. Alt + [ puts the current window on the left half, Alt + ] on the right. Course on the left, compiler on the right. Learn this in the first minute.

Reclaim vertical space. Alt + Shift + B toggles the shelf to auto-hide. F4 goes full-screen. On an 11-inch panel, those two together are worth more than any productivity app.

Kill the tab bar when you’re working. Open the compiler in its own window — Shift-click the tab, or drag it out. Fewer pixels lost.

Learn three editor shortcuts. Ctrl + Z undo, Ctrl + / comment, Ctrl + Enter run (or whatever your compiler binds). You will use these thousands of times.

Tab moves focus, not spaces. In a browser editor, Tab inside the code area should insert spaces; if it jumps out of the editor, click back into the code first. If your compiler supports it, set tab width to 2 — four-space indents eat a third of your visible line width on a small screen.

External keyboard, if you can. Any USB or Bluetooth keyboard is a genuine upgrade, and a £15 one from a charity shop is enough. This is the single highest-value thing you can add to a locked device, and it needs no permissions.

Zoom out one notch. Ctrl + − twice. Slightly small text is better than four lines of visible code.

Advertisement

Saving work when you can’t install Git

No Linux means no git, no local repo, and — this is the part nobody warns you about — the compiler tab loses your code when you close it.

Save outside the tab, every session:

  • Google Drive, if your school allows it: a folder called code, one file per exercise. Drive keeps versions; you can roll back.
  • The compiler’s download button, if it has one: exports to your Downloads folder, which survives.
  • A plain .txt file in the Files app. Ugly, works, and Files is not blocked by policy.
  • Email it to yourself at the end of every session. Zero elegance, zero data loss.

Name files 2026-11-10-fizzbuzz.py, not untitled. Dates sort.

Once you have a stable connection to Drive, and if the domain isn’t blocked, look at GitHub in the browser — you can create repos and commit through the web UI without a shell. Slow, but it’s a real portfolio, and it starts existing today rather than after you buy a laptop.

The rule: your work lives in at least two places before you close the lid. A lost first project is the most common reason people quit in week two.

The school filter problem, and the email that fixes it

Managed devices often run a filtering proxy — Securly, GoGuardian, Lightspeed, or a district appliance. Two things can go wrong with a browser-based compiler site:

  1. The domain is blocked outright. New and uncategorised domains get swept up by aggressive category rules. A site the filter has never heard of looks like an unknown, and unknown gets blocked.
  2. The page loads but the worker doesn’t. Some compilers run code in a web worker or a separate origin. The shell is whitelisted, the worker isn’t, and you get a spinner that never resolves.
Chromebook screen showing a school filter block notice in place of a coding website, with a Run button frozen behind it.
Two different failures: a block notice, or a page that loads and does nothing. Only the first one needs an email. Screenshot: Coodeverse.

If the page loads and the Run button does nothing, that’s the second one — it’s not you, and no amount of refreshing fixes it. Try a different compiler for that language, or work offline.

If it’s blocked outright, ask. Teachers say yes to this far more often than students expect, because “let me write Python in a browser tab” is a request they can approve without a ticket. Send this:

Subject: Request to unblock coodeverse.com (browser coding, no install)

Hi [name],

I'm learning to code in [subject] and the Linux environment on my
Chromebook is disabled, so I can't install Python or a code editor.

coodeverse.com runs Python, JavaScript and SQL in the browser tab
with nothing installed. It's free, has no sign-up and no ads.

Could the domain be allowed? If it helps, the compilers are at
coodeverse.com/compilers - I only need that path, not the whole site.

Thanks,
[name], [class]

Two things make that email work: it names the specific subpath so IT doesn’t have to open the whole domain, and it pre-empts the two objections (cost, sign-up). Send it once. If it’s refused, don’t argue — carry on with whatever isn’t blocked, and use a phone as a second screen.

When a Chromebook genuinely isn’t enough

This is the section most guides skip, and the reason people burn months on the wrong device. A browser tab gets you to a real, employable beginner level. It does not get you all the way. Here’s where the wall is:

  • No local server. Can’t run Flask, Django, Express, or anything listening on a port. Fine until you’re building APIs.
  • No Docker. No containers, no Postgres, no Redis.
  • No Android or iOS builds. Kotlin and Swift syntax yes; a signed APK, no.
  • No Unity, no game engine. C# syntax yes; a shipped game, no.
  • No debugger. Breakpoints and stack traces are where real debugging is learned. Browser devtools give you some of this for JavaScript and none of it for anything else.
  • 4 GB of RAM, usually. A dozen tabs and the machine starts swapping.
A phone propped against a keyboard next to a Chromebook, showing reference documentation while the laptop holds a code editor.
When a second window isn’t available, a phone becomes one. Photo: Coodeverse.

None of that is a reason to wait. All of it is a reason to be clear-eyed about what the device is for: the first six months. After that you need a real machine, and you should start quietly planning for one — a second-hand ThinkPad is £120, and old laptops run ChromeOS Flex if you ever get one to repurpose.

One more thing worth saying plainly: a school Chromebook is not a lesser start. It’s the standard start for a lot of people, including plenty who are now employed. Nobody will ask what you wrote your first loop on.

Your first week

Seven days, roughly 40 minutes each. Nothing here needs an install.

  1. HTML basics. Build a page with a heading, two paragraphs and a link. Run it in the web compiler. Save it to Drive.
  2. CSS. Colour the page, change the font, add a border. Ugly is fine.
  3. JavaScript lesson 1. console.log your name and a calculation. Open devtools with Ctrl + Shift + J and read the output there too.
  4. Variables and a loop. Print the numbers 1 to 10.
  5. FizzBuzz. Don’t look it up for twenty minutes first.
  6. Break it deliberately — delete a bracket, misspell a keyword, misindent a line. Read every error message out loud. This is the most useful day.
  7. Rebuild day 1’s page from memory. Then add one thing you haven’t been taught.

Day 6 matters more than days 1 through 5. Beginners who can read errors outlast beginners who can’t, by a wide margin, and errors are free.

Frequently asked

Can I install Python on a school Chromebook?
Not without Linux or developer mode, and on a managed device both are usually locked. You can still write and run Python in a browser tab in under a minute, which is enough to learn the language.
The Linux toggle is greyed out. Can I force it?
Only by switching the device to developer mode (Esc + Refresh + Power), which wipes local storage and may be blocked by policy. On a school device, assume you can’t, and use the browser.
Is coding on a Chromebook good enough to get a job?
Good enough to reach an employable beginner level in web development, which is where the entry-level jobs are. Not good enough to skip ever owning a real machine. The two facts aren’t in conflict.
Will my school see what I’m typing?
On a managed device, assume the admin can see browsing history and screen activity. That’s true of every site, not just this one.
Why does the Run button do nothing?
Almost always the web-worker problem above — the page loaded but the execution origin is blocked. Try another compiler for that language, or a different network.
Do I need an account anywhere?
No. The compilers, the courses and the practice questions are free and open with no sign-up. Nothing to verify, nothing to forget.

If you own the machine (Tier 1)

Enable Linux in Settings → About ChromeOS → Developers, install a real toolchain, and use the browser compilers only for quick tests. You get the best of both — and you should still read the saving section, because developer mode wipes local storage.

The honest summary

The greyed-out toggle is not a verdict on whether you get to learn this. It’s a constraint, and constraints have shapes — this one is narrower than the guides make it look. A tab, a keyboard shortcut or two, a save habit, and a politely worded email to IT will carry you a lot further than the people who gave up and started shopping for MacBooks.

Start on day 1. It’s one tab.