What you will learn The one-line install command, what it asks you, and what gets installed where.
Paste into a terminal (macOS/Linux) or PowerShell (Windows).
It arrives ready to run. There is no separate build or assembly step.
The address you will open in a browser. The default is:
Use the default unless you have a reason not to. If that port is already in use by another program, it will tell you to change it.
The password you enter when connecting.
It only opens on your own machine right now, but set a password anyway. Once you connect from outside, that password becomes the only door.
If you forget it, hyperteams setup lets you set it again.
| Location | |
|---|---|
| Program files | the install folder (shown during install) |
| The command | hyperteams — runnable from any folder |
| Database | inside the install folder. Conversations and usage records |
| Settings | .env.local |
| Logs | logs/server.log |
Nothing is created in your working directories. HyperTeams only remembers their paths; it does not put its own files inside them.
A version number means it is installed.
If you get
command not found, it is the same as in prerequisites — open a new terminal window and try again.
If the default port (27777) is taken, you can change it at run time.
You do not need to reinstall. Specify it each time you run, or change the
default with hyperteams setup.
This matters. When a new version comes out, do not rerun the install script.
upgrade replaces only the program files. Records, settings, and any
addresses you connected stay as they are. Reinstalling makes no guarantees about
what happens to them.
On Windows use the PowerShell command. The curl version is for macOS and Linux.
Possibly a proxy or firewall. Ask IT to allow access to hyperteams.net, or
download the install script, inspect it, and then run it.
The next chapter covers the first run step by step.
1. What two things does the install ask for?
The address (default http://localhost:27777) and a password. Set the
password even though it only opens locally for now — once you connect from
outside, it becomes the only door.
2. Why should you not rerun the install script when a new version arrives?
hyperteams upgrade replaces only the program files and preserves records,
settings, and connected addresses; a reinstall makes no guarantees about them.
3. Does HyperTeams create files in your working directories?
No. It only remembers their paths, and keeps its own files (database, settings, logs) in the install folder.
Now turn it on → First run and connecting
# macOS / Linuxcurl -fsSL https://hyperteams.net/install.sh | bash# Windows PowerShelliex (irm https://hyperteams.net/install.ps1)http://localhost:27777hyperteams --versionPORT=9000 hyperteamshyperteams upgrade