尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Chrome extension that routes web-app links to the right installed PWA window and account.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Every web-app link, in the right window, for the right account.
Clicking a Meet link in Gmail, Calendar, or Slack usually opens a new browser
tab instead of the Meet PWA you already have installed. After a day of that
you've got duplicate Gmail tabs, stray Meet tabs, and PWA windows you can't
tell apart — and it gets worse the moment you have more than one Google
account.檢視完整 README ↗Every web-app link, in the right window, for the right account.
Clicking a Meet link in Gmail, Calendar, or Slack usually opens a new browser tab instead of the Meet PWA you already have installed. After a day of that you've got duplicate Gmail tabs, stray Meet tabs, and PWA windows you can't tell apart — and it gets worse the moment you have more than one Google account.
Dock is a Chrome extension that fixes this without replacing your browser. It catches matching links and routes them into the right already-installed PWA window, for the right account, and gives you one shortcut to jump to any app window instantly. It makes no network requests — nothing it does ever leaves your device.
See Dock — v1 Spec Web App Link Router & Switcher.md
for the full product spec this implements.
authuser=, /u/N/, or a stored mapping), and keeps a
window's identity correct even when you switch accounts from inside the
PWA itself, reusing an already-open window for that account instead of
spawning a duplicate.Ctrl/Cmd+Shift+Space) — a fuzzy-searchable popup listing
every app window, grouped by account with an open-window count per login,
live calls surfaced first, one-click close per window or per account.Early. The core routing flow (rules engine, account extraction, the navigate/focus/open-new decision, the switcher) is implemented and unit tested. A few things the spec calls out as "spike first" are implemented but not yet verified against real installed PWAs — see CONTRIBUTING.md for exactly what's unverified and how to help. Not built yet: onboarding screens, the favicon overlay, end-to-end tests.
Add to Chrome — Dock is live on the Chrome Web Store.
Prefer to build it yourself, or want the current main instead of the
published version?
git clone https://github.com/sirius93/dock.git
cd dock
npm install
npm run build
Then chrome://extensions → enable Developer Mode → Load unpacked →
select the dist/ folder that npm run build produced. npm run watch
rebuilds the JS on save.
chrome://apps).Ctrl/Cmd+Shift+Space opens the switcher: type to fuzzy-search app,
account, or tab title; Enter focuses; Ctrl+W or the row's ✕ closes it.Dock keeps rules, account colours, and its in-memory window registry — nothing about your browsing history, and no network requests, ever. One small content script runs on Google Workspace pages (and any domain you add a custom rule for) so Shift-click can bypass routing for that one click; it reads only the clicked link's href and the Shift key state, nothing else from the page. See PRIVACY_POLICY.md for the full detail, and the spec's Privacy and security section for the original design intent (the favicon overlay it describes isn't built yet).
Manifest V3, one service worker, no build framework beyond esbuild. Routing
logic is written as pure, tested functions (src/rules.ts, src/accounts.ts,
src/router-logic.ts) separate from the thin chrome.*-calling layer that
wires them to real events (src/router.ts, src/registry.ts). See
CONTRIBUTING.md for the full file map.
PRs and bug reports welcome — see CONTRIBUTING.md for setup, conventions, and what's most useful to work on right now.
MIT © Nandan Kumar