Run env.
env
Mission 28
Environment variables
Inspect a simulated environment without exposing real browser or server secrets.
Terminal basicsenvechopwd
Lesson 28 of 360
0/360 lessons
0/17 missions
Terminal basics · 7 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
7 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run echo PATH is fake.
echo PATH is fake
Run pwd.
pwd
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Recognize common environment names and why they matter.
Run env and look for HOME, SHELL, and PATH.
Many CLI tools read configuration from the environment.
- Printing real secrets in a terminal.
- Assuming environment values are the same on every machine.
Reference
Commands in this lesson.
pwd
Print the current working directory.
env
Inspect a simulated environment.
echo <text>
Print text or write lab notes with >.