tailscale / tailscale/ts-browser-ext

Fork: Chrome/macOS login fix + exit-node picker & management UI

Open
#23 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
300
Forks
26
PR merge metrics
No merged PRs in 30d

Description

Hi! 👋

I reworked this extension to get it running smoothly on Chrome / macOS and added a few things that have come up in issues here. Sharing in case it's useful to others.

What I changed / added

  • Working login on Chrome/macOS — the popup's "Log in" link was a dead anchor (#login with no handler); it now opens the auth flow. Also fixed Chrome-vs-Firefox detection during --install (newer Chrome also defines browser, so the install command was wrongly generated as Firefox).
  • Exit-node picker — pick or clear a per-profile exit node right from the popup (related: #5, #3).
  • Management page at http://100.100.100.100/ — device status, tailnet machine list (address / OS / online), exit-node selector, and a Log out button, so logging out no longer requires removing & re-adding the extension.
  • Honest transient states — "Connecting…" / "Waiting for approval…" while the link comes up, instead of an error flash right after login.
  • Shipped the missing need-install icon and added a live popup refresh after login.

Repo: https://github.com/iazat/ts-browser-ext

If you'd like, I'm happy to split any of these into focused PRs against this repo — just say which ones are interesting and I'll send them in.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is a multi-part fork proposal rather than a focused change. Start by reviewing the popup login flow and --install browser detection, then assess the exit-node and management UI work against issues #5 and #3. Done would require a maintainer-selected scope and separate acceptance criteria for the chosen part.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
authentication, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.