Read the prompt before the command
A terminal session carries a location and an identity. In the local Ghost OS shell, pwd tells you where you are, whoami tells you which user is acting, and cd changes the working directory. Relative filenames are interpreted from that directory. ~ is a shortcut to your home directory.
A successful simulated SSH login changes the prompt to the target device. That device may present a Linux-style shell, a router or switch CLI, or a supported Windows CMD or PowerShell-style command set. The prompt and available commands follow the device profile. These are educational command environments, with their own limits. Use exit to leave a remote session and return to the previous shell.
Turn output into the next input
A pipe, |, passes the text from one command to the next. Think of it as a sequence of questions: show me the file, keep the relevant lines, then show the first few matches. Supported text tools include grep, head, tail, sort, uniq, and wc.
Output redirection saves text into a virtual file. > creates or replaces the destination; >> appends. tee saves a copy while also passing the text onward, and tee -a appends. A failed write is still a failed operation: check the message and the file rather than assuming that a pipeline undoes earlier steps.
Explore without losing your place
Use command history to revisit earlier input and Tab completion for supported command names, arguments, and paths. Completion depends on the current shell and what is available in that context. help and man explain the supported forms. less and more let you review a file or piped text in a pager.
For supported background workloads, the prompt can return while the task continues. jobs shows job state; fg, bg, and guarded kill operate on eligible jobs. Job control is bounded and cooperative, rather than a complete Unix signal and scheduling model.
Practice scripting at the right scale
The embedded Bash-compatible subset supports learning exercises with variables, conditions, loops, and pipelines. Embedded Python supports interactive work and scripts with virtual-file and simulated-socket integration. Treat the in-app help as the guide to supported behavior: full Bash compatibility and compatibility with every Python package or host tool are not promised.
A useful exercise is to compare a command run locally with one run after a remote login. Record the prompt, user, current directory, and output. The same command name can describe different supported behavior in a different session.