HyperTeamsWhat HyperTeams is
What you will learn The relationship between HyperTeams and Claude Code, and why we call it a control room.
In one line
A control room for directing and watching the Claude Code installed on your own machine, from a web screen.
Three parts to unpack.
1. "The Claude Code installed on your own machine"
HyperTeams does not build a new AI. It uses the Claude Code you already have.
graph TD
H["HyperTeams<br/>runs on your machine"] --> C["Claude Code<br/>already installed"]
C --> F1["Working directory A"]
C --> F2["Working directory B"]
C --> F3["Working directory C"]Nothing to sign up for, no key to obtain. It uses your existing Claude Code login as-is.
2. "From a web screen"
Claude Code is normally used in a terminal. One terminal, one job.
| Terminal only | HyperTeams | |
|---|---|---|
| Concurrent work | open several windows | cards on one screen |
| Progress | you have to watch that window | all of it at a glance |
| Closing the window | the job is cut off | it keeps running |
| From a phone | no | yes |
3. "Directing and watching"
Both work.
- Directing: you hand work to a working directory
- Watching: what it is doing and which files it touched appear in real time
Why "control room"
The analogy:
- Claude Code is the worker. It does the actual work.
- HyperTeams is the control room. It hands work to several workers and watches the progress.
A control room does no work itself. Instead it lets you see several things at once.
How it differs from Connect
The two products are easy to confuse, so:
| HyperTeams | HyperTeams Connect | |
|---|---|---|
| Where it runs | your machine | the cloud |
| What it works on | your actual files | a workspace |
| Who uses it | you (or people you shared with) | a team |
| Data | stored on your machine | stored in the cloud |
| Sign-up | not needed (uses your Claude Code login) | required |
They are not competitors — they connect. Register your machine as a system in Connect and you can direct work on your machine from a team workspace.
What is good about it
| Feature | Meaning |
|---|---|
| Several jobs on one screen | no window switching. Cards at a glance |
| Your machine, your files | in real project folders, in your usual environment |
| Nothing to sign up for | uses your existing Claude Code login |
| A minute to start | one line to install, one to run |
| Your phone is the control room | set something running and check it on the move |
| A record remains | conversations and usage stored on your machine |
Common questions
"Can I use it without Claude Code?"
No. HyperTeams is a tool for directing Claude Code, so that has to be there first. Installing starts with the prerequisites.
"Does my code leave my machine?"
The work happens on your machine and the records stay there. How Claude Code communicates with the model is exactly as it always was — HyperTeams does not change that part.
"Is this only for developers?"
It is mostly used for code work, but anything involving files is a candidate. Organising documents, converting material, automating repetitive tasks all work.
Check yourself
1. State the relationship between HyperTeams and Claude Code in one sentence.
Answer
HyperTeams is a control room for directing and watching the Claude Code you already have installed. It does not build a new AI; it uses the existing Claude Code and its login.
2. What is the biggest difference between HyperTeams and Connect?
Answer
Where it runs. HyperTeams runs on your machine and works on your real files; Connect runs in the cloud and works on a team workspace. The two link up through system registration.
3. What changes compared to using Claude Code in a terminal?
Answer
You see several jobs at once on one screen, work continues after you close the window, and you can check from a phone.
Two things are needed to start → Prerequisites