Companion
What the planned phone companion will let you see and answer away from your computer, how it pairs, and how its access ends.
On this page
The companion is Lanes and Rocket! on an iPhone. It keeps you in charge of agent work when you are away from your computer: you see what needs you, answer it safely and review results. It never holds a secret, never decides an answer itself and never becomes a second authority. The companion is not part of Hypervibe's first release: phone pairing and the relay it uses come in a later release, the first phone release. This page describes that plan. All of it is Planned.
The phone shows what needs you and lets you answer #
- One list. Every open item addressed to you, your teams or your roles appears in one list across workspaces.
- The exact effect. An approval card shows the command and its working directory, or the file with lines added and removed, plus its risk flags. An agent's summary is labelled as one and never replaces the effect.
- Two steps on touch. You choose, then confirm, and the confirm control never sits where your first press was.
- One answer path. Your answer goes to the item's authority, and one receipt closes the item on every surface. An answer the phone could not confirm reads Not confirmed yet, with Retry and Look up outcome, and is never shown as failed.
- Results. A result shows its verdict, evidence, limitations, diff and cost, and an unknown cost reads Unknown. If you are the receiver, you accept it, or reject it with a reason. A pass is never shown as acceptance.
- Content-free notifications. A notification carries a fixed sentence and a count, never prompt, lane or message text. It only opens the item; it never answers.
A question that asks for a secret value is never answered on the phone. It reads "Answer it in the lane".
Pairing asks you what the phone may do #
On Just me, the single-person profile, you pair by QR code or a one-time code through the Lanes relay, which forwards the phone's traffic to your computer unchanged and holds no credential. Your computer asks "This phone can open terminals and answer agents" and gives the phone the interactive grant, which lets it act as well as read, only when you say yes. On a team, the phone shows a code, you approve it in a browser signed in with your team identity, and team policy decides the grant.
| Action on the phone | Needs the interactive grant |
|---|---|
| Read Needs you, lanes, sessions and results | No |
| Answer a decision or an approval | Yes |
| Accept or reject a result | Yes |
| Steer or interrupt a Rocket! session | Yes |
| Open or type into a lane's terminal | Yes |
Without the grant, every item is read-only, and Jump opens the item's lane. The phone's settings show its grants and the reason any is missing.
Only one client holds a session's input #
A Rocket! session on the phone is a native view, not a terminal you type into. The read-only session view comes first, then steering, interrupting in two steps and starting a session. Only one client holds a session's input at a time, so the phone and your computer never type over each other. While your computer holds input, the phone cannot send until input is handed to it, and a request that is rejected or expires changes nothing. A reconnect resumes where it left off, with no gaps or duplicates. When Throttle drops part of an earlier turn, such as the model's reasoning, instead of sending it again, the session shows that as a quiet note. Offline, the phone keeps the last good view with its age and refuses a write instead of queueing it. A lane's terminal is the fallback for agent clients with no answer channel.
Revoking a phone ends its access #
Signing out revokes the phone's connection, and you can revoke a lost phone from your computer or the Platform. A team administrator can also pause it. The requirement is that within 60 seconds the phone's calls are refused; it then shows that access ended, drops every content view and clears its local history. The 60-second figure is a requirement, not a measurement. An app lock hides everything, including in the app switcher. The phone never receives a secret value, because Throttle holds every credential, and an agent never acts through the phone.
iPhone comes first #
| Platform | Plan |
|---|---|
| iPhone | Planned The first phone release, through TestFlight and the App Store, after Hypervibe's first release |
| iPad layout | Planned A later release |
| macOS and Windows | Unavailable Not part of the first release |
| Android | No companion in the current plan |
Deeper views, such as builds, Fleet hosts, message threads and detailed economics, follow in later releases.
Where to go next #
- Lanes explains lanes, Needs you and decisions.
- Rocket! explains sessions and exact-effect approvals.
- Hypervibe platform covers devices, grants and revocation.
- Standings explains what Planned means.