Account Authorization

How signing in to Thruline works, and what each sign-in method gives you access to.

Sign-in methods

From thrulinecontext.com/account/auth/login, you can sign in with:

GitHub OAuth permissions

Signing in with GitHub requests these scopes:

This is separate from the GitHub App installation, which is what powers automated PR reviews and is granted independently.

Account conflicts and merging

If you sign in with GitHub or Google using an email address that's already linked to a different Thruline account, Thruline detects the conflict and walks you through merging the two identities.

Sessions

Signing in starts a session that's remembered across visits until you sign out or the session is revoked. Your AI editor's connection to the MCP server authenticates separately, through its own OAuth flow:

Multi-organization access

If you belong to more than one GitHub organization, Thruline lets you operate in any of them from the dashboard's organization switcher. Repositories, team management, and billing are all scoped to the organization currently selected. Your personal account is separate from any organization — a personal subscription covers your personal repositories, and an organization's Team or Business subscription covers that organization's repositories.

Account recovery

If you signed in with email and password, use Forgot password? on the sign-in page to reset it. If you signed in through GitHub or Google, recovering access to that provider account restores your Thruline sign-in as well. Thruline doesn't hold a separate password for OAuth-only accounts.