Free tools Windows power users keep installed
One-click scans. No signup required.
To use passwordless authentication with a private GitHub repository, add a passkey to the GitHub account that already has repository access. In GitHub, open Settings → Access → Password and authentication → Passkeys → Add a passkey, approve the prompt from your phone, computer, password manager, or FIDO2 security key, and then choose Sign in with a passkey at the next browser login. The passkey proves who you are; repository membership, organization permissions, and any SAML single sign-on policy still decide whether you can open the private repository.
A passkey changes browser sign-in. It does not automatically configure git clone, git pull, or git push. Those operations use a separate HTTPS or SSH credential flow, covered below.
What passwordless access means for a private repository
A GitHub passkey is a public/private cryptographic credential held by an authenticator. During sign-in, the authenticator proves possession of the private key without sending that key to GitHub. The credential is bound to the GitHub website domain, so a browser will not use it on a look-alike phishing site. With two-factor authentication enabled, GitHub can use a passkey to satisfy the password and second-factor requirements in one step.
The passkey authenticates your GitHub account. It is not a repository key and does not grant access by itself. The account must still be a collaborator, team member, or organization member with permission to read or write that private repository. An organization using SAML SSO may also require a login through its identity provider. Enterprise Managed Users authenticate through their identity provider rather than managing a normal personal-account passkey flow.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Before you begin
- Sign in to the exact GitHub account that can already see the private repository.
- Use an eligible, up-to-date browser and an authenticator you can unlock: a phone, Windows Hello or another computer authenticator, a supported password manager, or a FIDO2 hardware key.
- Keep an existing recovery method available. GitHub can still request your password for sensitive actions such as adding SSH keys, authorizing applications, or changing team membership.
- If the repository is in an organization, find out whether SAML SSO or an enterprise-managed identity provider is required.
Add a passkey to your GitHub account
- Open account settings. Sign in to GitHub, open your profile menu, and select Settings.
- Open authentication settings. In the left navigation, choose Access → Password and authentication.
- Start enrollment. Under Passkeys, select Add a passkey. GitHub may ask for your password or another existing sign-in method before allowing the change.
- Approve the authenticator request. Select Add passkey in the GitHub prompt, then follow the operating-system or browser dialog. Depending on the authenticator, you may scan a QR code with a nearby phone, unlock Windows Hello, enter a hardware-key PIN, touch the key, or approve a password-manager prompt.
- Finish registration. Wait for the success message and click Done. Give the entry a recognizable name if GitHub asks for one, such as “Work laptop” or “USB security key.”
- Test it in a private window. Open the GitHub login page in a private window, choose Sign in with a passkey, select an authenticator on the current or nearby device, and complete its biometric, PIN, passcode, or hardware-key prompt.
If the passkey sign-in succeeds but the repository is still unavailable, authentication worked; check the account, repository membership, organization invitation, and SSO authorization instead of registering another passkey.
Choose the right authenticator
| Authenticator | How it behaves | Recovery consideration |
|---|---|---|
| Phone or computer passkey | Uses the device’s built-in biometric or PIN. Cloud-backed credentials may synchronize through the same provider. | A synced credential can appear on another device after you restore the provider account. A device-only credential cannot. |
| Password manager | Stores and presents the passkey from a manager that supports passkeys. | Recovery depends on access to that manager and its account-recovery process. |
| FIDO2 hardware security key | A portable key can connect over USB, NFC, or Bluetooth. GitHub names YubiKey as an example of a FIDO2 key that can register as a passkey. | The passkey is device-bound and does not sync. Register a second key or another device-bound passkey before relying on one key. |
You do not need to buy a security key. An existing phone, computer authenticator, or compatible password manager is sufficient. A hardware key is useful when you want a separate physical credential that is portable and kept away from your everyday devices.
Sign in to GitHub with the passkey
- Open GitHub’s sign-in page.
- Select Sign in with a passkey rather than entering a password.
- Choose the authenticator offered by your browser. For a nearby phone or security key, choose the option to use another device and follow the QR-code, NFC, Bluetooth, or USB instructions.
- Unlock the authenticator with its biometric, PIN, passcode, or hardware-key touch.
After authentication, GitHub evaluates normal authorization. A passkey cannot bypass a removed repository invitation, a missing team permission, an organization policy, or required SAML SSO.
Passkey sign-in versus Git operations
GitHub has separate authentication paths for the website, APIs, desktop applications, and Git transport. A successful browser passkey login does not place a credential in your terminal.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
| Task | Credential path | What to configure |
|---|---|---|
| Open the repository in a browser | GitHub passkey | Register and use the passkey as described above. |
git clone, pull, or push over HTTPS |
GitHub CLI browser authentication or a personal access token stored by a credential helper | Authenticate the CLI or create a token with the repository permissions required by your organization, then let the helper store it. |
git clone, pull, or push over SSH |
An SSH key held on your computer | Create a key pair, add its public key to GitHub, load the private key into your SSH agent, and use an git@github.com: remote. A passkey does not replace this key. |
For an organization protected by SAML SSO, authorize the HTTPS token or SSH key for that organization when GitHub presents the SSO control. An enterprise-managed account may require the identity provider for browser and developer-tool access.
Verify that the private repository is reachable
- While signed in with the passkey, open the repository URL in GitHub. Confirm that private files and the repository’s normal actions are visible.
- Check the repository’s Settings → Collaborators and teams area, if you administer it, or ask an organization owner to confirm your permission.
- For HTTPS Git access, make sure your remote is the HTTPS URL and run a read-only operation such as
git ls-remote originafter configuring the CLI or token. - For SSH, run
ssh -T git@github.com, then testgit ls-remote git@github.com:OWNER/REPOSITORY.git. The SSH test confirms key authentication; repository authorization is checked by the second command.
Recovery and account hygiene
Register more than one device-bound passkey
Device-bound passkeys, including those on many hardware keys, cannot be recovered from cloud synchronization. If the device is lost, wiped, or damaged, its credential is lost. GitHub recommends registering device-bound passkeys on at least two different devices when they are your only passkey type.
Inspect the passkey list
Return to Settings → Access → Password and authentication → Passkeys periodically. Identify which entries are synchronized and which are device-bound. Remove a lost or unknown authenticator, but do not delete your only working recovery method before testing its replacement.
Keep another recovery route
Retain the account password, recovery codes if 2FA is enabled, or another supported authentication method. Passwordless does not mean that GitHub never asks for a password: sensitive account changes can still require it.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Review the account after a suspected compromise
Enable two-factor authentication, add a known passkey, and review SSH keys, deploy keys, authorized OAuth applications, and GitHub Apps. Remove entries you do not recognize and rotate any credentials that may have been exposed.
Troubleshooting
“Sign in with a passkey” is missing
Confirm that you are on GitHub’s real HTTPS sign-in page, using a browser and operating system that support passkeys. Try the account-settings enrollment path first. A managed enterprise account may intentionally use its identity provider instead of personal passkeys.
The phone or security key is not detected
Unlock the phone, enable the requested Bluetooth or NFC connection, or reconnect the USB key. For a hardware key, verify its PIN and touch sensor. Choose the browser option for another device if the credential is on a nearby phone.
Enrollment stops after the password prompt
GitHub may require an existing password or second factor before changing authentication settings. Complete that check, then restart Add a passkey. If the account is organization-managed, ask the identity-provider administrator which enrollment method is permitted.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Browser login works but the repository returns 404 or “not found”
GitHub often hides private repositories from accounts without permission. Verify that you used the account that was invited, that the invitation was accepted, and that the organization has not removed your team access. For SAML SSO, complete the organization’s identity-provider authorization.
git clone asks for a password
This is expected when the remote uses HTTPS and no CLI, token, or credential helper is configured. A browser passkey is not an HTTPS Git credential. Authenticate with GitHub CLI or configure an appropriate personal access token and helper, or change the remote to SSH and configure an SSH key.
An SSH command succeeds but Git still cannot read the repository
ssh -T proves that GitHub recognized the key, not that the account can access a particular repository. Check the remote owner and repository name, organization SSO authorization, and the account’s collaborator or team permission.
Performance, security, and operational trade-offs
- Phishing resistance: Domain binding prevents the authenticator from responding to an unrelated look-alike site.
- Convenience: A biometric or local PIN can replace repeated password and second-factor entry for browser sign-in.
- Portability: Synced passkeys are convenient across devices; hardware keys are portable but device-bound and require deliberate backup planning.
- Separation of duties: Keeping browser passkeys separate from SSH keys and HTTPS tokens limits the impact of losing one credential, but it means every access path must be configured independently.
- Organization control: SAML SSO and managed-user policies can add steps that an individual account does not have. Follow the organization’s policy even when personal passkey enrollment is available.
Or skip the browser setup
ScreenshotNeo is a separate website screenshot API and MCP server for developers; it does not authenticate to GitHub or replace a repository passkey. If your workflow also needs repeatable screenshots of documentation or private web pages, one GET request returns PNG, JPEG, WebP, or PDF output. Cookie and consent banners, newsletter popups, and chat widgets are removed before capture; bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing result. Its MCP server lets Claude, Cursor, or another MCP client call take_screenshot, get_page_info, and capture_pdf.
For a screenshot call, create an API key and use the documented parameters at https://screenshotneo.com/docs/:
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo includes 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 shots. See ScreenshotNeo, then create a free account.
Frequently Asked Questions
Can I use a passkey to access a private GitHub repository?
Yes, if the passkey belongs to the GitHub account that has repository permission. Organization SAML SSO or managed-user policies may require an additional identity-provider step.
Does a GitHub passkey work for git clone and push?
Not by itself. Configure HTTPS with GitHub CLI or a personal access token, or configure SSH with a key pair; those credentials are separate from browser passkeys.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do I need a security key for GitHub passkeys?
No. GitHub can use a phone, computer authenticator, or supported password manager. A FIDO2 key is optional and should be backed up because its passkey is device-bound.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
