All pages

Docs · AI features

Your account and GitHub

Availability: macOS (Settings → Account) · iOS · Linux and Windows (sidebar → Account) · trmnly.dev dashboard · trmnly account on any platform.

One TRMNLY account carries your sign-in, your credits, and the devices you've paired. This page is about the first of those, and in particular the question that used to have no answer anywhere in the product: which GitHub account am I connected as, and can TRMNLY reach my repositories?

Two different grants

They are easy to confuse, and doing the first does not do the second.

What it grants Where it happens
GitHub sign-in Identity. It proves who you are, so the account you reach on trmnly.dev is yours. "Continue with GitHub" on trmnly.dev, or trmnly account login
Repository access Reading and pushing to repos. Installing the TRMNLY GitHub App at github.com/apps/trmnly

Signing in with GitHub and never installing the app is a normal, common state. It looks fine until something needs a repository — a cloud clone, a job that pushes a branch — and then fails. That is why every account surface shows the two as separate rows.

Where to look

Every surface shows the same two rows, in the same words, because they all read one answer from GET /api/v1/me.

  • macOS — Settings → Account (⌘,), the GitHub section. It appears whenever this Mac is paired, whether or not credits are configured, and re-checks whenever TRMNLY becomes the active app — which is exactly what happens when you come back from installing the app in your browser.
  • iOS — the Remote tab's Account section.
  • Linux and Windows — the sidebar's Account page. This is also where you sign in: those platforms have no Settings window, and the page runs the device-code flow for you.
  • trmnly.dev — the dashboard's GitHub panel.
  • Any terminal — trmnly account.

What the rows mean

GitHub sign-in

Shown Means
@name That GitHub account is linked. Opening it goes to the profile.
Linked (GitHub user #123) Linked, but trmnly.dev could not recover the username — it will fill in on your next sign-in.
Not linked This account signs in with a password. Link on trmnly.dev opens the dashboard, whose GitHub panel links it. Signing in with GitHub using the same verified email address attaches it to the account you already have.

Repository access

Shown Means
Installed on @name · All repositories Everything on that account, including repos created later.
Installed on @name · 3 selected repositories Only those three. Manage changes the selection on GitHub.
No repositories selected (amber) Installed, but its selection is empty, so it reaches nothing and a clone would fail. Fix it with Manage, not by reinstalling.
Suspended on GitHub (amber) The installation still exists but grants nothing until you unsuspend it.
Not installed Install GitHub App opens GitHub. Install it on the account or organization that owns the repos you want.
Unavailable on this server The deployment has no GitHub App configured. Nothing to fix on this machine.
Couldn't load GitHub status The lookup failed, or the server is older than this feature. It is not a "no" — use Refresh.

Signing in without a Settings window

On Linux and Windows, and over SSH anywhere:

trmnly account                 # who you are, your GitHub link, repo access
trmnly account --json          # the same, for scripts
trmnly account login           # GitHub device code; prints the code and URL
trmnly account logout          # revoke this machine's token

login prints a short code, opens (or names) github.com/login/device, and waits. GitHub's token never reaches this machine: trmnly.dev exchanges it and hands back an ordinary TRMNLY device token, which is what gets stored — in the Keychain on macOS, in $XDG_STATE_HOME/trmnly with 0600 on Linux.

It refuses to sign in while another account's token is stored, so you do not silently replace one. The exception is a token trmnly.dev already rejects (revoked from the dashboard, or its device deleted): there is no account left to protect, so it is replaced.

On macOS that token is the same sign-in Remote Control pairs with, so trmnly account logout there unpairs Remote Control too, and asks for --yes before it does.

An installation TRMNLY doesn't see

An installation is tied to your TRMNLY account through the GitHub account that installed it. If you installed the app before ever signing in with GitHub, there was nothing to tie it to.

  • On your own GitHub account it repairs itself: the next time any account page loads, the install is recognised as yours.
  • On an organization it does not, because being in an org is not owning it. Sign in with GitHub first, then change the installation's repository selection on GitHub — saving it re-sends the installation to TRMNLY, which attaches it to you.

Signing out, and deleting the account

The macOS app only runs signed in to an approved trmnly.dev account (see Getting started and, for the lock window's other reasons, Updates → Your licence and updates). Signing out with trmnly account logout, or revoking this Mac on trmnly.dev, takes effect at once: the next launch asks you to sign in again, rather than running offline for up to a week.

Deleting the account is self-service: Settings (trmnly.dev/app/account) → Delete account at the bottom of the page, or the iOS app's Account tab → Delete account. Type DELETE to confirm. It removes every paired Mac and phone, the cloud workspace and its saved files, scheduled jobs, stored keys, chat rooms you own and feedback you sent; messages you posted in other people's rooms are replaced with a note that the author deleted their account. A monthly plan ends immediately, any credit balance is lost, and a desktop licence's seats go with the account. It can't be undone. If you installed the GitHub App, uninstall it on GitHub too. Signing out of a phone is separate and leaves the account alone.