---
title: "Use Skyworker from a phone"
description: "Pair a phone or another browser, read the inbox, start tasks, get notifications and open a terminal."
---

> Documentation Index
> Fetch the complete documentation index at: https://skyworker.system3inference.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Skyworker from a phone

`init` deploys a second Worker, `<name>-app`, with a web client. The client shows the inbox: one row for each session, with what waits for you first. A device that you pair uses it.

## Pair a device

```sh
skyworker pair
```

The command prints a QR code and a link. Scan the code with the camera of the phone, or open the link in another browser.

- The code works once, for 5 minutes. It is a secret until then. Do not paste it anywhere.
- The device gets its own device token for 30 days.
- The device never gets the control token or a workspace password.

If the install has no web client yet, `pair` fails with `this install has no app Worker yet`. Run `skyworker upgrade`, then `skyworker pair` again.

`skyworker pair --json` prints the link, the time it expires and the scopes, in place of the QR code.

## What a device can do

A paired device can:

- see every session and read its messages;
- reply to a session, and cancel the turn that runs;
- answer a permission request of OpenCode with Allow once, Always allow or Reject;
- start a task;
- wake a workspace;
- open a terminal in a workspace.

A wake costs money while the workspace runs. The list itself wakes nothing.

To pair a device that cannot open a terminal, run `skyworker pair --no-terminal`.

## Read the inbox

The inbox groups sessions as `Waits for you`, `Ended, not read`, `Working` and `Earlier`. Workspaces that are not awake are listed below. The list refreshes every 30 seconds while the page is visible. The Refresh button reads it at once.

The attention state of a session is one of `working`, `waiting`, `idle`, `done`, `failed` and `stopped`. A session that changed and that you did not read has an `Unread` mark.

A session screen shows the messages, the result record, and a reply box. One button sends the reply, or stops the turn that runs.

## Start a task from the phone

Open New task. Choose:

- **Workspace.** A workspace that exists. To make one, run `skyworker connect` on your computer.
- **Harness.** OpenCode, Claude Code or Codex.
- **Checkout.** `Workspace checkout` or `Own worktree`. An agent that works in the checkout makes `Own worktree` the default. An own worktree starts from the default branch on origin.
- **Push the branch and open a pull request.** Off by default.
- **Task.** The text for the agent.

A task from a device commits and does not push. Turn on the push switch to get the push for that one task. You can also ask for the push in a reply later.

Starting a task wakes the workspace. The button then says `Wake and start`.

## Saved messages and wake

The messages of a session are in its workspace. A device saves the messages of each session that you read. It keeps the 40 newest sessions. A saved session opens with no wake.

A session that you did not read on this device needs a wake. The session screen has a `Wake workspace` button. Settings is a button at the bottom of the inbox. In Settings, a choice wakes the workspace by itself when you open a session that has newer messages. It is off at first.

The Settings screen has a button that removes the saved messages. `Forget this device` removes them too. After a revoke, the app removes them when it next opens.

## Notifications

Notifications use Web Push from your own Worker. A device gets one when a session waits for you or ends while you are away. Turn them on in Settings.

On an iPhone or iPad, notifications work only when you open Skyworker from the Home Screen. Tap Share, then Add to Home Screen.

If the browser blocks notifications, Settings says where to allow them.

## Open a terminal

A device paired with the terminal scope can open a terminal in a workspace from the session screen. It is the same tmux session that `skyworker shell` opens. Closing the page detaches. What runs there keeps running.

## List and revoke devices

```sh
skyworker devices
skyworker devices --revoke <id>
```

The list shows each device with its id, name, scopes, pairing age, last seen time, push state and expiry. A revoked device cannot use the web client any more. An open terminal of a revoked device closes within 30 seconds.

`Forget this device` in Settings revokes the device on the server and pairing is needed again.

Source: https://skyworker.system3inference.dev/docs/guides/phone/index.mdx
