Your workspace in the browser
Open the link your operator sent, sign in once, and see the controls your role allows — the board, comments, instructions, and the terminals you may watch or control.
Open the link your operator sent, sign in once, and you see your team's workspace with exactly the controls your role allows. Nothing runs in the browser. It is a window onto the Mac your team runs Push on, the same way the iPhone app is.
Signing in
Sign in with Apple, Google or GitHub at push.computer/account. Your account lists every workspace you can reach in the workspace directory; choose up to four to show and one as Default. A private link opens its item as soon as you are in.
The browser stays connected across reloads and new tabs. Disconnect, or signing out, removes it. On a new browser or a new computer, sign in again.
Roles
What you can do is decided by the role the owner gave you and by the permissions on each folder: file work, run work, view terminal, control terminal. The page shows only the controls your role allows, and never grants one. Roles are offered to your exact account and accepted by you, on your own device.
A comment from someone without run work still lands on the session's thread, as context. It wakes nothing on its own.
One-time approval
Viewers and commenters are admitted without an approval step. Anything more — sending an instruction, starting or stopping a run, creating work, moving it to another folder, watching or controlling a terminal, administering the workspace — is approved once, from the owner's trusted iPhone or Mac. After that, this browser is remembered for that workspace; the owner can remove it from the workspace's devices. A new browser, or a changed host key, needs approval again.
The board
When every shown computer serves it, the workspace page is the same board the Mac shows — Todo, Active, Completed — filtered to the folders you may see. Otherwise it keeps a list.
- Open a session to read its thread: notes, messages from Slack or a linked Linear ticket, recordings, files.
- Comment. If the session is live, the comment reaches the agent mid-run.
- Tell the agent what to do sends an instruction, when your role has run work on that folder.
- New session creates a Todo in a folder where you may file. Creating starts nothing; Run starts it in a real terminal on the Mac. When Run is unavailable, the button says why.
- Stop a run, or move work to another folder you have access to.
With one workspace open, Settings lists its members and their roles, and its vocabulary and memory if your role can configure the workspace.
Watching and taking control of a terminal
Watching a terminal and typing into it are separate grants. With view terminal you see the live output. With control terminal you can take over, and the browser asks first: "Take control of this terminal? Typing will run on the connected computer." Until you confirm, nothing you type goes anywhere.
When the computer is asleep or offline
The computer's row says so; for your own computers it also says when it was last online. The page connects again on its own once the computer answers. Requests you sent meanwhile wait and are delivered when it reconnects.
If the page says "Update Push on the computer to open this workspace", the Mac is running an older Push than the browser needs. Ask your operator to update it. If it says "You no longer have access", ask the workspace owner.
Safari
Safari does not keep the connection across tabs yet. Each new tab asks you to connect again. Other browsers keep it.