Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
80 commits
Select commit Hold shift + click to select a range
f4fbe07
chore(plan): complete planning for PAN-5500
Nov 19, 2026
b058d98
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
b40e869
docs(anywhere): fix Note, plans and account claims (lines 1-173)
Nov 19, 2026
d321d0f
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
6fbfb70
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
0e89654
docs(anywhere): date every shipped row and roadmap step (lines 175-321)
Nov 19, 2026
1b2a67d
docs(anywhere): record anywhere-shipped-roadmap.ac4 evidence
Nov 19, 2026
61fee65
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
a579de1
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
067ef91
docs(anywhere): fix pricing reasoning and run page-wide checks
Nov 19, 2026
db4aa84
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
4c24c48
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
d00b5d7
docs(cli/account): fix base URL, failure messages, JSON output, token…
Nov 19, 2026
fed8d67
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
9e5dc92
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
9d55bb4
docs(linked-machines): fix link request, SSH, Fly, fingerprint and re…
Nov 19, 2026
fbac19e
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
d903e7a
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
cf4bfbe
docs(linked-machines): fix fleet versions, --machine fly, placement o…
Nov 19, 2026
ee212ab
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
80fbf65
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
1b6121f
docs(cli/machines): fix error remedies, reboot timing, Update all, di…
Nov 19, 2026
667033c
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
c6b56a5
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
1f0e6ef
docs(cli/pair): replace stale release note and fix error texts
Nov 19, 2026
d0421f9
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
b55fe8a
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
8dfb601
docs(cli/devices): remove stale release note, cover paired phones
Nov 19, 2026
75a2ecf
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
ee2cb33
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
c6dca96
docs(mcp): fix harness list, tool parameters and agent-only routes
Nov 19, 2026
a3dad9d
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
3ffad5f
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
31e77d7
docs(mcp): fix provisioning tables, scopes and fleet reach
Nov 19, 2026
df8e456
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
ab30f2a
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
7a88d26
docs(cli/mcp): fix refusal kinds, URL variables, Hermes key, relay ad…
Nov 19, 2026
0b3cf08
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
5c8b1c4
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
54b8bf7
docs(cli/token): fix list scope, revoke refusal and internal name
Nov 19, 2026
4296664
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
c157702
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
151e7b7
docs(session-vault): remove stale release notes, limit harness claims
Nov 19, 2026
1e981fa
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
6029c10
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
823e44d
docs(cli/vault): describe shipped dashboard features, fix save/exclud…
Nov 19, 2026
ff8a5da
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
9757381
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
2315fb4
docs(tailscale): fix setup steps, stored state and machine-link note
Nov 19, 2026
db2c6c8
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
fda886f
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
202673e
docs(cli/tailscale): fix status output, exit cases, add missing errors
Nov 19, 2026
5389304
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
20bb76c
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
23e795e
docs(remote-access): remove stale notes and roadmap, fix descriptor a…
Nov 19, 2026
bb1a527
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
af5d31b
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
7998c59
docs(shared-sessions): date the release, fix harness and terminal claims
Nov 19, 2026
d46c79d
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
651cc1c
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
cabc906
docs(cli/share): fix messages, join URL and token-mint behavior
Nov 19, 2026
9dbe40a
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
68f9f61
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
edae561
docs(triggers): date the release, fix rate-limit, Funnel and inbox cl…
Nov 19, 2026
dc619fd
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
9423e96
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
b6c3897
docs(cli/triggers): date the release, fix inbox, JSON and remove beha…
Nov 19, 2026
39bda09
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
cece92b
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
94044e5
docs(bots): fix default access, connector files and troubleshooting
Nov 19, 2026
a029f80
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
4f80c9c
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
9df1ce2
docs(phone): describe both phone setups, remove transitional notes
Nov 19, 2026
67a25f2
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
d884bea
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
a90ce2e
docs(push-notifications): remove stale ship notes, fix config and fai…
Nov 19, 2026
54e3693
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
e535781
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
6169179
docs: validate the Anywhere docs group and draft the PR body
Nov 19, 2026
52026b8
chore(workspace): plan artifacts for PAN-5500
Nov 19, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
617 changes: 617 additions & 0 deletions .pan/continues/PAN-5500.xbrief.json

Large diffs are not rendered by default.

1,519 changes: 1,519 additions & 0 deletions .pan/drafts/PAN-5500.md

Large diffs are not rendered by default.

Large diffs are not rendered by default.

187 changes: 104 additions & 83 deletions anywhere.mdx

Large diffs are not rendered by default.

51 changes: 30 additions & 21 deletions cli/account.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: pan account
title: "pan account: sign this machine in to overdeck.ai"
sidebarTitle: "pan account"
description: Optional overdeck.ai sign-in for this machine (directory and hosted features)
---

Expand All @@ -9,7 +10,7 @@ Sign this machine in to your overdeck.ai account with GitHub's device flow. Sign
optional: `pan share` needs it, and `pan join` runs this sign-in itself when the machine is not
signed in (see [`pan share and pan join`](/cli/share)).
It is the prerequisite for the directory ([PAN-2356](https://github.com/eltmon/overdeck/issues/2356))
and Shared Sessions — see [`anywhere`](/anywhere).
and Shared Sessions; see [`anywhere`](/anywhere).

You can also sign in from the dashboard: **Settings → Anywhere → Account → Sign in**, in a
browser on this machine. It writes the same `account.json` as `pan account login`, and the
Expand Down Expand Up @@ -38,9 +39,9 @@ hardcodes the sign-in host.
| `--base-url <url>` | Account service URL. |

The base URL resolves in order: `--base-url`, then the `OVERDECK_ACCOUNT_URL` environment
variable, then the default `https://account.overdeck.ai`. An invalid URL (wrong scheme, a
path, a query, or a fragment) exits 1 before any network call with
`Invalid account service URL: <url>`.
variable, then the default `https://account.overdeck.ai`. It must use `https`, or `http` on
`localhost`, `127.0.0.1` or `[::1]`, and have no path, query or fragment. Anything else exits
1 before any network call with `Invalid account service URL: <url>`.

An unsupported platform exits 1 before any network call:

Expand All @@ -54,7 +55,7 @@ Signing in again on a machine that already has a token prints:
Already signed in as <login>; signing in again replaces this machine's token.
```

and still runs the flow — the service rotates this machine's token in place. On success:
and still runs the flow: the service rotates this machine's token in place. On success:

```
Signed in to <baseUrl> as <githubLogin> (device <label>, <deviceId>).
Expand All @@ -66,7 +67,7 @@ If your GitHub account is not on the invite list, or you cancel the GitHub step:
This GitHub account is not on the overdeck.ai invite list, or sign-in was cancelled. Ask the operator to allow it, then run: pan account login
```

Other failures: `The sign-in code expired. Run: pan account login`; `Cannot reach <baseUrl>: <reason>` when the first request fails with a network error three times in a row (it is retried after 1 s and 2 s), or when the service is unreachable for several consecutive polls. `<reason>` names the underlying network cause when there is one, for example `fetch failed (ECONNRESET: socket hang up)`; or, if a token arrived but reading the account afterward failed, the token is still saved and it prints `Signed in (device <label>, <deviceId>), but could not read the account: <reason>. Run: pan account status`.
Other failures: `The sign-in code expired. Run: pan account login`; `Cannot start sign-in at <baseUrl>: HTTP <status>` when the service answers the first request with an error status; `Sign-in failed: <error>` when polling returns an error other than pending, slow down, denied or expired; `Cannot reach <baseUrl>: <reason>` when the first request fails with a network error three times in a row (it is retried after 1 s and 2 s), or when three polls in a row fail with a network error or an HTTP 5xx answer (then `<reason>` is `HTTP <status>`). `<reason>` names the underlying network cause when there is one, for example `fetch failed (ECONNRESET: socket hang up)`; or, if a token arrived but reading the account afterward failed, the token is still saved and it prints `Signed in (device <label>, <deviceId>), but could not read the account: <reason>. Run: pan account status`.

## status

Expand All @@ -80,7 +81,7 @@ With no stored token:
Not signed in. Run: pan account login
```

(exit 0 — sign-in is optional). Otherwise this calls `GET /v1/me` against the stored base
(exit 0; sign-in is optional). Otherwise this calls `GET /v1/me` against the stored base
URL and prints:

```
Expand All @@ -95,45 +96,53 @@ operator to renew the invite.`

| Flag | Effect |
| --- | --- |
| `--json` | Print `{ signedIn, baseUrl, githubLogin, githubId, deviceId, label, access, reachable }`. Never includes the token. |
| `--json` | Print `{ signedIn, baseUrl, githubLogin, githubId, deviceId, label, access, reachable }`. `access` is `{ status, expiresAt }`, where `status` is `active` or `grant_expired`, or `null` when the service did not confirm the token. Signed out, it prints `{"signedIn":false}` and exits 0. A rejected token or an unreachable service still prints the JSON, with `reachable` true or false, and exits 1. Never includes the token. |

If this machine's token was revoked or the account was deleted: `This machine's sign-in is
no longer valid (<error>). Run: pan account login`, exit 1 — the token file is kept so you
no longer valid (<error>). Run: pan account login`, exit 1; the token file is kept so you
can see this message again rather than silently sign you out. If the account service is
unreachable: `Signed in as <login> (account service unreachable: <reason>)`, exit 1, using
the login cached in the token file.

`status` shows no plan. To see your plan and relay use, open the account page at
https://account.overdeck.ai/account, or Settings → Anywhere → Account in the dashboard.

## logout

```bash
pan account logout
```

Revokes this machine's device on the account service (`DELETE /v1/devices/<deviceId>`) and
deletes the local token file either way — a 204, 401 or 404 all mean the device is gone or
already invalid:
deletes the local token file either way, since a 204, 401 or 404 all mean the device is gone
or already invalid:

```
Signed out. This machine's device token was revoked.
```

If the service cannot be reached, the token file is still deleted locally, and this prints
to stderr and exits 1:
If the service cannot be reached, or answers with a status other than 204, 401 or 404, the
token file is still deleted locally, and this prints to stderr and exits 1:

```
Signed out locally, but could not revoke the device on <baseUrl>: <reason>. Revoke it from another signed-in machine or ask the operator.
```

With no stored token: `Not signed in.`, exit 0, no network call. `logout` never touches
anything under `${OVERDECK_HOME}` besides `account.json` — not the Session Vault key, not
anything under `${OVERDECK_HOME}` besides `account.json`: not the Session Vault key, not
`environment-id.json`.

## The token file

`${OVERDECK_HOME}/account.json`, mode `0600`, written atomically. Holds `baseUrl`,
`accessToken`, `deviceId`, `label`, `githubLogin`, `githubId` and `signedInAt`. A corrupt or
unreadable file is never rewritten silently: reading it fails with a message naming the
path and `Delete it to sign out locally.`
`${OVERDECK_HOME}/account.json`, mode `0600`, written atomically. Holds a format version `v`
(always 1), `baseUrl`, `accessToken`, `deviceId`, `label`, `githubLogin`, `githubId` and
`signedInAt`. A corrupt or unreadable file is never rewritten silently: reading it fails with
a message naming the path and `Delete it to sign out locally.`

It never holds the Session Vault key, a vault passphrase, or any conversation content; see
[`pan vault`](/cli/vault) for those.

## Get help

It never holds the Session Vault key, a vault passphrase, or any conversation content —
see [`pan vault`](/cli/vault) for those.
Still stuck? Ask on the [Overdeck Discord](https://discord.gg/ZpHE2ZTv5P) or file a
[GitHub Issue](https://github.com/eltmon/overdeck/issues).
34 changes: 25 additions & 9 deletions cli/devices.mdx
Original file line number Diff line number Diff line change
@@ -1,12 +1,13 @@
---
title: pan devices
title: "pan devices: list and revoke paired devices"
sidebarTitle: pan devices
description: List or revoke the devices paired with this machine's dashboard
---

# `pan devices`

Manage the devices paired with this machine's dashboard. Released in v0.64.0. Settings →
Anywhere's **Revoke** has the same effect (next release, v0.65.0). See
Manage the devices paired with this machine's dashboard. Released in v0.64.0. The
**Revoke** button in **Settings → Anywhere → Paired devices** does the same. See
[Remote access](/configuration/remote-access#list-and-revoke-devices).

## list
Expand All @@ -15,35 +16,50 @@ Anywhere's **Revoke** has the same effect (next release, v0.65.0). See
pan devices list [--json]
```

Lists paired devices with columns `ID NAME CREATED LAST USED REVOKED`.
Lists paired browser devices and paired phones (the Overdeck app) with columns
`ID NAME CREATED LAST USED REVOKED`.

| Flag | Effect |
| --- | --- |
| `--json` | Print the device array as JSON. |
| `--json` | Print the device array as JSON; each entry has `id`, `name`, `kind` (`device` or `phone`), `scopes`, `createdAt`, `lastUsedAt` and `revokedAt`. |

With no paired devices: `` `No paired devices. Pair one with `pan pair`.` ``

It needs the running dashboard: without one it prints the not-running message and exits 1.
A dashboard that rejects the internal token prints the same token message as `pan pair`
and exits 1. Any other dashboard error prints `pan devices list failed: <message>` and
exits 1.

## revoke

```bash
pan devices revoke <id>
```

Revoke a paired device and close its live connections.
Revoke a paired device and close its live connections. Revoking a phone also closes its
secure-channel connections.

Through the dashboard it prints:

```
Revoked device "<name>" (<id>); its live connections were closed.
```

With no dashboard running it writes the revocation into `~/.overdeck/access-tokens.json`
and prints:
With no dashboard running it writes the revocation of a paired browser device into
`~/.overdeck/access-tokens.json` and prints:

```
Dashboard not running; revoked in the registry. No live connections were open.
```

An unknown id prints `No paired device with id <id>.` and exits 1.
A phone cannot be revoked this way: with the dashboard down, a phone's id prints
`No paired device with id <id>.` Start the dashboard and run the command again.

An unknown id prints `No paired device with id <id>.` and exits 1. A dashboard that
rejects the internal token prints the same token message as `pan pair` and exits 1. Any
other dashboard error prints `pan devices revoke failed: <message>` and exits 1.

## Get help

Still stuck? Ask on the [Overdeck Discord](https://discord.gg/ZpHE2ZTv5P) or file a
[GitHub Issue](https://github.com/eltmon/overdeck/issues).
Loading
Loading