What you will learn This part is for readers without a technical background. From here on the manual uses these words without explaining them. This first chapter is the floor — what is actually happening inside the machine.
The earlier parts covered what and why. From here it is how, and that is where unexplained words start arriving.
After this part those four lines read plainly. Not so you can write software, but so you can read the rest of the manual without stopping and talk to your IT people in the same words.
| Part | What it does | Analogy |
|---|---|---|
| Storage (disk, SSD) | survives power off | filing cabinet |
| Memory (RAM) | what is open right now | the desk |
| CPU | does the actual work | the person working |
HyperTeamsgraph TD
A["Storage — survives power off<br/>files, programs"] -->|"opening spreads it out"| B["Memory — cleared on power off<br/>what is open now"]
B -->|"hands over the maths"| C["CPU — does the work"]
C -->|"result back"| B
B -->|"only if you save"| AThe bottom arrow is the point. What sits in memory has to pass through save to survive. Pull the power and the desk is swept; only the cabinet remains.
They look alike, and mixing them up makes the rest of the manual confusing.
| Program | Process | |
|---|---|---|
| What | what is installed | what is running |
| Where | storage | memory |
| How many | one | possibly several |
Install Chrome once, open three windows: one program, several processes.
When the hyperteams command says it is already running, it means the process.
It sounds like a brush-off, but there is a reason. A restart wipes memory entirely. Tangled state, half-open connections, files held by mistake — all gone at once.
If two restarts change nothing, memory is not the cause. From the third attempt, look at configuration. That one distinction saves a lot of flailing.
Start a program in a terminal and it usually hangs off that window. Close the window and it dies with it. Programs that need to outlive the window offer a separate way to start.
That is what --background in the command reference means, and
the same structure is why the terminal stays alive after
you close the browser tab.
The computer itself still has to be on. Background detaches from the window, not from the machine. Close a laptop lid and the CPU stops, so scheduled runs stop with it.
| State | Memory | Running programs |
|---|---|---|
| On | kept | running |
| Sleep | kept | stopped |
| Shut down | cleared | gone |
Sleep keeps everything in place, so on waking it looks like nothing happened. But nothing ran while it slept. If a machine is meant to work overnight, turn sleep off.
Different things. Disk is the cabinet, memory is the desk. Emptying the cabinet does not clear the desk. Close programs, or restart.
Closing a window and ending a process are different. Anything started in the
background survives the window and needs an explicit stop
(hyperteams stop).
1. What is the difference between storage and memory?
Whether it survives power off. Storage (the cabinet) does; memory (the desk) is cleared. That is why saving matters.
2. What kind of problem does a restart fix?
State accumulated in memory — tangled state, half-open connections. If two restarts change nothing, look at settings on disk instead.
3. Does a background process keep working when you close the laptop lid?
No. Background detaches from the terminal window, not the machine. Sleep stops the CPU, so scheduled work stops too.
Next, inside that cabinet → Files, folders, paths
"Install Node.js LTS""Open localhost:27777""Attach it with a read-only account""Issue an API key and put it in the header"✓ Fixed by a restart → state accumulated in memory ("it was fine yesterday")✗ Survives a restart → settings written to storage, a bad filehyperteams # tied to this terminal — closing it stops the programhyperteams start --background # detached — keeps running