Sign in with GitHub
Sign in to browse and play GitHub recordings with a higher API allowance. Local recording, playback and live sharing work without a GitHub account.
Signed in to GitHub
- Public repositories
- Followers
- Joined GitHub
Checking website sign-in…
Website sign-in reads recording metadata and release information without repository write or Gist permissions. Your session lasts up to seven days, or until your GitHub token expires.
Authorize CLI uploads
termbacktime auth --storage repo --open
Enter the displayed device code on GitHub. Create a public TBT-Recordings repository if prompted, then install the GitHub App using Only select repositories and choose only that repository. The app needs Contents read/write and Metadata read. The CLI rejects broader repository access and stores and refreshes the login locally. CLI upload tokens stay on your computer and are separate from website sign-in.
The CLI fetches the public GitHub app ID from the website API once and caches it in ~/termbacktime/termbacktime.json. Later logins reuse that value; if GitHub rejects a stale Client ID before issuing a device code, the CLI checks the website for an updated ID. After switching websites or GitHub Apps, run termbacktime auth --storage repo --refresh-client-id --open to fetch it again. Removing the config also clears the cached ID and your saved token.
For Gists, use the separate termbacktime auth --storage gist --open login, or import a Gist token with termbacktime auth --storage gist --token-stdin. Repository imports must be user tokens from the configured GitHub App with access to only TBT-Recordings. Remove both local logins with termbacktime auth --logout.