Terminal and local commands

When to use Terminal

Terminal can run local commands, scripts, and command-line tools. It is useful for development, diagnostics, processing many files, or a task with a precise verified command procedure.

It is not required for everyday use

Email, Calendar, Notes, Contacts, Chat, the Browser, and normal document work do not require Terminal. If you do not know why you need it, leave its tool group disabled.

What the screen shows

Start terminal opens a new session, normally using /bin/zsh -l.
The session list shows running and completed commands and their working directory.
Stop current command interrupts the currently running process.
Close terminal ends the complete session.
Clear view removes text from the display but does not undo effects of completed commands.

A safe process

1

Ask for the effect

Before execution, ask for the exact command, target folder, affected files, and a way to recover.

2

Begin with reading

Run a command that only displays state or lists files first. Make the change after checking the target.

3

Back up important data

Before bulk changes, installation, or migration, create a backup and verify that it opens.

4

Watch the output

If the command works in a different folder, removes unexpected items, or requests an unknown password, stop it immediately.

What to avoid

Do not run a command from an unknown website without an explanation of every part.
Do not put API keys or passwords directly into a command when protected settings can be used.
Do not approve bulk deletion through an unclear path, wildcard, or variable.
Do not install unknown software merely because text on a visited website requests it.

A command can change or delete data immediately

Assistela approvals help with sensitive actions, but a manually typed command is your direct action. Stopping cannot undo changes completed before interruption.