HyperTeamsHyperTeams vs Paseo
Paseo is an open-source app that runs a daemon on your computer to drive agents like Claude Code, Codex and OpenCode, and lets you connect from phone, web and desktop with end-to-end encryption. HyperTeams heads the same way, keeping execution on your computer, but it also starts work on its own at set times, takes non-code work, and adds the approvals, audit and cost attribution you need once colleagues assign work.
Why HyperTeams over Paseo
Paseo and HyperTeams start in the same place: agents run on your computer, you watch and instruct from your phone, and your code goes nowhere. They split after that. The HyperTeams control room starts work every day at the time you pick on screen and takes work in folders that aren't repositories as cards. Paseo has cron and interval schedules too, and Paseo Hub also starts work from GitHub, Slack and Discord activity. Once several people are involved, Paseo Hub lists allowed users per trigger and collects run records. HyperTeams Connect adds roles and policy per folder and command, per-item pre-approval with its audit trail, and cost and caps per person and team. HyperTeams does not drive Paseo, so you can use them side by side.
It starts on its own at a set time
Starts agents on cron or interval schedules, and with Hub also from things that happen in GitHub, Slack and Discord.
Pick a time on screen and it runs then, every day. A failure notifies you.
It takes non-code work
An app for driving coding agents remotely, so the screen centers on agent chats and diffs.
Work becomes cards per folder, so reports, documents and data cleanup show up with their result files in one list.
A person allows it before it runs
Add allowed users to a Hub trigger and their activity starts an agent right away. Roles and per-item approval are not documented.
Set roles and policy per folder and command, and send risky work through per-item pre-approval. An audit trail records who approved what.
Cost belongs to a person
Usage is mixed into each agent account. What each person's job cost isn't tracked separately.
Every job records its cost, Connect attributes it to people and teams, and caps apply per person and team.
HyperTeams vs Paseo
- PaseoA daemon on your computer (or home server or VPS) runs the agents; desktop, phone, web and CLI clients connect to it.
- HyperTeams SystemExecution stays on that machine — the control room sits on top rather than taking it over.
- HyperTeams ConnectIt does not touch execution; it receives what the control room reports.
- PaseoSeveral agents in parallel, optionally each in its own git worktree and branch.
- HyperTeams SystemOne card per job — hand it five and five run side by side, in five folders.
- HyperTeams ConnectThe control room does this
- PaseoLive agent output and diff review in the app.
- HyperTeams SystemStatus, a summary of the answer, and an unread marker, all in one list.
- HyperTeams ConnectThe control room does this
- PaseoThe daemon stays up when you close the window; an end-to-end encrypted relay reaches it from your phone.
- HyperTeams SystemResident, and it records progress: it continues after you close the window, and a tunnel shows it on your phone.
- HyperTeams ConnectThe control room does this
- PaseoStarts agents on cron or interval schedules. Hub also starts work from GitHub, Slack and Discord activity.
- HyperTeams SystemYou pick a time on screen, and a failure notifies you.
- HyperTeams ConnectThe control room does this
- PaseoConnects to several daemons, and Hub collects incoming work and runs in one place.
- HyperTeams SystemIt stops at that one machine. It does not know what runs on the next one.
- HyperTeams ConnectA control room per machine, all of them in one list — including which machine is awake.
- PaseoEach Hub trigger lists allowed users. Roles and per-item approval are not documented.
- HyperTeams SystemIt assumes the owner of the machine. The screen is behind one password.
- HyperTeams ConnectAccounts and roles, policy per folder and command, and pre-approval per item.
- PaseoHub records what arrived, what it matched and what ran. No approval records.
- HyperTeams SystemIt keeps that machine's run history. There is no notion of an approval.
- HyperTeams ConnectWho approved what, and when, kept as a policy audit trail.
- PaseoMixed into each agent account's usage. Nothing per person.
- HyperTeams SystemIt shows cost per job on that machine, with no owner attached.
- HyperTeams ConnectAttributed to a person and a team, with ceilings.
- PaseoFree under Apache 2.0. Hosted Hub is €15 per seat per month; self-hosted Hub is free.
- HyperTeams SystemOne command to install, using the Claude or ChatGPT account you already have.
- HyperTeams ConnectOnly the features that cross into a team are metered in credits.
Checked against each product's official documentation as of 2026-09-26. Their products change, and when they do this table becomes wrong — tell us and we will fix it.
Paseo docsWhat the control room does, and what Connect does
HyperTeams is two products. Which of them answers each row above is exactly where the boundary sits.
HyperTeams System
Runs the work on your machine
A program you install with one command. It assigns work per folder, runs jobs in parallel, and keeps going after you close the window. While you work alone, this is all you need.
- Where it runs
- Several jobs at once
- How far along it is
- If you close the window
- At a set time
HyperTeams Connect
Makes it something others rely on, unattended
It starts paying the moment there is a second machine and a second person: pooling machines into one list, filtering work others assign through approval, keeping an audit trail of what happened, and splitting cost per person.
- Several machines in one place
- When someone else assigns work
- Retracing it later
- What it cost
When do you move up a rung?
- L1 · Observe
You watch several machines. The moment there is a second one.
- L2 · Share
The team sees what was asked for. The moment you start sharing one password.
- L3 · Delegate
Others assign work and see the results. This is where approval, policy, and audit earn their place.
Running both
You don't remove or migrate what you use today. Here is how to layer HyperTeams on top of it.
- 1
Keep Paseo
Don't uninstall it. Keep driving agents by voice from your phone with Paseo.
- 2
Install the control room with one command
Install it on the same computer and register your working folders. Both use the agent accounts signed in on that computer.
- 3
Split the work
Ad-hoc coding goes to Paseo; scheduled work and jobs from colleagues go to the control room. HyperTeams does not drive Paseo.
Which one should you pick?
When to just use Paseo
When you want to talk to it
Dictate tasks or talk through problems in voice mode, with speech processed on the device.
When you want to host everything
Apache 2.0 open source with no telemetry or forced log-ins. Connect over your LAN, Tailscale or your own tunnel instead of the relay, and self-hosted Hub is free.
When work should start from issues and chat
Paseo Hub takes activity from GitHub, Linear, Slack and Discord and starts agents on your daemons. HyperTeams doesn't ship these integrations by default.
When HyperTeams is the answer
When something runs at the same time daily
HyperTeams SystemPick a time and the control room starts it on its own; a failure notifies your phone.
When the work isn't code
HyperTeams SystemRegister folders that aren't repositories and hand off reports, cleanup and research as cards, then open the result files directly.
When you want to allow others' jobs
HyperTeams ConnectThis is where Connect starts: accounts and roles, policy and per-item pre-approval, and an audit trail of who approved what.
When cost needs splitting
HyperTeams ConnectOnce several people share a subscription, cost is tracked per person and team, and caps stop it before it overflows.
A layer, not a replacement
Put it on top of what you already run
One command to install. Nothing you use today gets removed or moved — you only add the command screen above it.
curl -fsSL https://hyperteams.net/install.sh | bashKeep reading
- HyperTeams vs Claude Code
- HyperTeams vs OpenAI Codex
- HyperTeams vs Gemini CLI
- HyperTeams vs Cline
- HyperTeams vs OpenHands
- HyperTeams vs Conductor
- HyperTeams vs Claude Squad
- HyperTeams vs Vibe Kanban
- HyperTeams vs Orca
- HyperTeams vs tmux
- HyperTeams vs Cursor
- HyperTeams vs GitHub Copilot
- HyperTeams vs Devin
- HyperTeams vs OpenClaw
- HyperTeams vs Hermes Agent
- HyperTeams vs Manus
- HyperTeams vs Lindy
- HyperTeams vs NotebookLM
- HyperTeams vs n8n
- HyperTeams vs Zapier
- HyperTeams vs Make
Common questions
Paseo is an Apache 2.0 open-source app that runs a daemon on your computer, home server or VPS to drive agents such as Claude Code, Codex, Copilot, OpenCode and Pi, with clients for macOS, Windows, Linux, iOS, Android and the web. Remote access goes through an end-to-end encrypted relay, your LAN, or your own tunnel.
If driving agents from your phone is all you need, Paseo is enough, and it leads on voice. If you need work that starts on its own at set times, non-code work, and approvals, audit and cost attribution when colleagues assign work, HyperTeams is the answer.
Both sit on top of several of your own machines. Paseo Hub routes work arriving from GitHub, Slack and Discord to your daemons and keeps a record. Connect adds roles, policy, per-item pre-approval, an audit trail, and cost and caps per person on top of the machine list, so work can be handed to others with nobody watching.
Yes. Paseo through its iOS and Android apps and an end-to-end encrypted relay; HyperTeams by attaching an address in the app and installing it on your phone's home screen to check progress and add instructions. Neither needs router or firewall changes.
Yes. Both drive the agent accounts signed in on your computer. Usage limits belong to the account, so they share them. HyperTeams shows remaining quota and cost per job on one screen.