A chapter to look things up in. Find your symptom.
Most problems have their answer in the log.
Just the end:
If it died on the previous run:
hyperteams: command not foundThe most common problem.
Check the log. Usually a prerequisite problem.
If either does not, fix prerequisites first.
To change the default, hyperteams setup.
http://PORT=9000 hyperteamshyperteams restart is required after connecting a
tunnelThe first is the most common. When the Claude Code login expires, HyperTeams stops with it.
Your working directory is probably drawn too wide. Redraw it narrowly.
And state the scope in your instruction — writing it as what not to do is effective.
The cause differs by symptom.
| Symptom | Cause | Response |
|---|---|---|
| Only generic answers | missing context | add the situation to the folder description and the instruction |
| It forgets earlier instructions | context pushed out | split into a new task |
| It does what you said not to | scope unspecified | state what not to do |
| Unclear whether it finished | no done condition | add a pass criterion |
The task is too big. Split it smaller — one task fitting in a single sentence is about the right size.
Clean up terminals you are not using.
See the cost section of the scheduled runs chapter.
hyperteams upgrade does not touch data. If you reinstalled, data may have been
removed.
If you use git, undoing there is the most reliable route. That is why committing before starting is recommended.
Without git you depend on your editor's undo or a backup.
Get in touch, with the log.
Contact: hyperteamsnet@gmail.com
Walk the recovery order once, for yourself. Thirty minutes → Recover a stalled job
Including these speeds things up:
cat logs/server.logtail -50 logs/server.logcat logs/server.log.prevclaude --version # does it print?node --version # does it print?PORT=9000 hyperteamshyperteams setup□ Is the Claude Code login still valid? → run claude in a terminal□ Is the working directory path valid? → does the folder actually exist□ Are there errors in the log? → tail -50 logs/server.log□ have you left several terminals open and forgotten them□ are too many tasks running at once□ how many scheduled runs are going□ are there schedules left over whose purpose is gone□ are you using a heavy model for simple worktail -100 logs/server.log□ OS and version□ hyperteams --version□ claude --version / node --version□ what you were trying to do and what did not work□ the end of the log