Not every topic runs code in the browser. The track overview and lesson header show an execution profile.
Common profiles
iframe_html— HTML/CSS preview in an iframe.client_javascript— JS in the browser; use DevTools console too.server_script/server_compiled— needs the dev runner (npm run runnerlocally).none— read + local practice (Git, Excel, AWS console, …).
When Run is disabled
Follow the Install on your device section on the first lesson of each track and practice in your own terminal or app.
Self-check
- Why can’t Git commands run inside a web iframe safely?
- What two terminals do you need for PHP playground on localhost?
Interview prep
- Why might a topic have no “Run” button?
Some tracks are conceptual or shell-oriented; running arbitrary code in the browser would be unsafe or misleading. You practice in your own environment instead.
- What should you never paste into a public code sandbox?
Secrets (tokens, passwords), private URLs with session cookies, or customer data—treat sandboxes as observable.