First run and connecting

What you will learn The basic start, connect, and stop flow. And how to run it without tying up a terminal.

If localhost:27777 means nothing to you, start with Networks and communication.

Starting

One word, from any folder.

On start it prints the address.

Connecting

Open that address in a browser. Enter the password you set during install and you are in.

It is empty the first time, because you have not registered a working directory yet. That is the next chapter.

The screen after registering a few folders. The far left is the working directory list (on a wide screen it starts folded into a narrow strip of letter badges — open it with »), with per-engine usage and CPU, memory and disk at the bottom. Next to it is the selected folder's sidebar — four sections: Tasks · Terminals · Explorer · Browser — and the wide area on the right is the workbench, which lays them out side by side as tabs and panes.

Tools, usage and settings live under ⋯

Press ⋯ (More) in the sidebar header for Tools · Usage · Folder settings · Global settings. The first three open as workbench tabs; Global settings slides in from the right. Language, run accounts, remote access (tunnel) and updates are in Global settings.

The ⋯ menu in the sidebar header.

The command palette (Ctrl+K, ⌘K on macOS) goes to the same places — type a name like "New task", "Tools" or "Global settings". Ctrl+B (⌘B) folds the sidebar away and back.

Stopping

Ctrl-C once in the terminal you started it from cleans everything up.

If tying up a terminal is inconvenient

Starting with plain hyperteams means you have to keep that terminal. Close the window and it stops with it.

To keep it running after closing the window:

It prints the address and returns your prompt. You can use that terminal for other things, or close it.

When running in the background

Starting automatically at boot

Register hyperteams start --background as a system startup item.

These are each OS's standard mechanism, so there is plenty of material online.

The three ways to run it

graph TD
  A["hyperteams"] --> A1["attached to this terminal<br/>Ctrl-C to stop<br/>closing the window stops it"]
  B["hyperteams start --background"] --> B1["terminal is free<br/>hyperteams stop to stop<br/>survives closing the window"]
  C["Registered at startup"] --> C1["automatic at boot<br/>nothing to think about"]

Start with plain hyperteams at first. Watching the output lets you confirm it is working. Move to background once you are comfortable.

Where people get stuck

"The address prints but the browser won't open it"

• Check you typed it exactly (including http://)
• Another program may be using that port → try PORT=9000 hyperteams

"I don't remember the password"

Lets you set it again.

"It starts and immediately stops"

Check the log.

Usually Claude Code or Node.js is not ready. Recheck prerequisites.

Check yourself

1. What is the difference between hyperteams and hyperteams start --background?

2. Where do you see the output when running in the background?

3. Why start with plain hyperteams at first?

Build the knowledge of where to look before you need it. Thirty minutes → Check your first connection