QuickTab

Well behaved browser tabs for Zendesk agents.

QuickTab is a Chrome extension that keeps your Zendesk Support agent tabs under control. When a new browser tab tries to open a Zendesk Support /agent link, QuickTab checks whether you already have an agent tab open. If you do, it routes the link to that existing tab instead of spawning another one — so you end up with a single, tidy Zendesk agent tab rather than a wall of them.

QuickTab starts working the moment it's installed. No setup required.

Fork notice

This is a maintained fork of the original zendesklabs/QuickTab, which was archived and is no longer maintained or supported by Zendesk. The upstream extension was also removed from the Chrome Web Store as Google tightened its Web Store restrictions.

I've forked the project to continue its development — modernizing the codebase, fixing bugs, and keeping it working with current versions of Chrome and Zendesk. Contributions, issues, and feedback are welcome.

The original work is licensed under the Apache License 2.0, and this fork continues under the same license. See LICENSE.

Permissions

QuickTab requests permission to read and change your data on zendesk.com sites. It needs this to watch tab navigation and redirect Zendesk agent links to your existing agent tab.

Installing locally (unpacked)

Because the extension is not published on the Chrome Web Store, install it as an unpacked extension. Build it first — the app/ directory is source and will not load directly, as the stylesheets and templates need compiling.

npm install
npm run build

1. Open chrome://extensions in Chrome.
2. Enable Developer mode (top right).
3. Click Load unpacked and select the generated build/ directory (the one containing manifest.json).

After changing anything under app/, run npm run build again and press the reload button on the extension's card in chrome://extensions. Both steps are needed — service worker changes in particular only take effect after that reload.

The zip in releases/ predates the Manifest V3 migration and will no longer load in current Chrome. Build from source instead.

Building from source

Command	What it does
npm run build	Compiles into build/
npm run watch	Rebuilds on change (still reload in Chrome to pick it up)
npm run package	Builds and writes a .zip into releases/

The sources are native ES modules, so there is no bundler. The only compile steps are dart-sass for the stylesheets and the Handlebars precompiler for the templates — templates must be precompiled because runtime compilation needs new Function(), which the Manifest V3 content security policy blocks. See scripts/build.mjs.

Roadmap

• Migrate from Manifest V2 to Manifest V3 (required by current Chrome). Done.
• Refresh the build toolchain and dependencies. Done — Grunt, Webpack and Ruby Sass are gone.
• Verify compatibility with the current Zendesk Support agent workspace.
• Carry existing users' saved settings over from localStorage to chrome.storage.

Contributing

See AGENTS.md for repository conventions and development setup.

License

Apache License 2.0. See LICENSE.