Chrome, Edge and Brave extension that reads verification codes and sign-in links from Gmail and fills, copies or shows them.
One account is free. A one-time purchase unlocks more. For each new code it can auto-fill the page, copy the code, or only keep it in the popup. A verification link can be opened from the popup. Mail is read in the browser with the Gmail readonly scope. Checkout for extra accounts is ExtensionPay and Stripe.
- Chrome Web Store: Keytray.
- From a release: download
keytray-<version>-chrome.zipfrom Releases, unzip it, openchrome://extensions(Edge:edge://extensions), turn on Developer mode and choose Load unpacked on the folder that containsmanifest.json. - From source (needs Node.js and pnpm):
pnpm install && pnpm build, then load.output/chrome-mv3unpacked. Building needs your own Google OAuth client; SETUP.md has the Google Cloud project, test users and.envsteps.
You can remove the purchase code and build a copy for yourself. Selling it, charging for a copy, or profiting from it is reserved to the author. See LICENSE. This is not an OSI open-source license: use, modify and share for yourself, but do not sell it or charge for it.
See CONTRIBUTING.md.
A program on your computer (for example an AI agent driving Chrome) can ask Keytray to fill the newest verification code into a tab, or open the newest sign-in link in it. The program never sees the code or the link. It is off by default.
Set up:
- Run
native/install.sh. It registers a small helper (com.keytray.agent) with Chrome, Edge and Brave. Python 3 is required. On Windows runpowershell -ExecutionPolicy Bypass -File native\windows\install.ps1instead (Chrome and Edge). The CLI is then%LOCALAPPDATA%\Keytray\keytray.cmd. In WSL, the repo'snative/keytray-agent-cli.pyworks after the Windows install: it hands the call to the Windows helper. - Open Keytray Options, go to "Agent sign-in" and turn it on.
Or skip the click: run the installer with
--enable(Windows-Enable), or--allow-all(-AllowAll) to also allow all sites. This writes a per-machineconfig.json({"agentSignIn": true, "allowAll": true}) in the helper's folder; Keytray reads it when it starts. It has only those two switches and no site list on purpose. The off switch in Options always wins;agentSignInfalse or missing never turns it off by itself; deleting the file or settingallowAllto false removes the*the file added on the next browser start, and any program running as your user can write that file, and so can turn Agent sign-in on and allow all sites; switching Agent sign-in off in Options blocks that. Details:docs/agent-protocol.md. Uninstall keeps the file. - Use the CLI:
native/keytray-agent-cli.py status
native/keytray-agent-cli.py pending <tabId>
native/keytray-agent-cli.py fill_code <tabId> [--wait 60]
native/keytray-agent-cli.py open_link <tabId>
pending says whether the tab has a code field and whether a fresh code or link is waiting (sender and age only). fill_code fills the newest unused code that is at most 10 minutes old. With --wait N (up to 120 seconds) it checks Gmail every 5 seconds until one arrives. open_link navigates the tab to the newest sign-in link.
Safety rules:
- Only sites on the allowlist work (default github.com, google.com, vercel.com, apple.com; exact host or subdomain). Edit it in Options. Every frame that receives a code must match too, and a link is only opened if its own host is allowed.
- Allowed sites can be
*(Options: Allow all sites): every https site; the code still goes only to frames on the tab's own site or a listed site, a link opens only on the tab's site or a listed site, and the rate limit stays. - Fill never submits the form. The agent clicks the button itself.
- A code is filled once, then marked used.
- At most 10 requests per 10 minutes. The last 200 requests are listed in Options with time, command, site and result. They never contain codes or links.
- Replies strip any field named code, otp, link, url, token, secret or password.
- On Windows the helper listens on the named pipe
\\.\pipe\keytray-agent-<user>; a client needs the key in%LOCALAPPDATA%\Keytray\agent.key. - The helper listens on
~/Library/Application Support/Keytray/agent.sock(Linux:~/.local/share/Keytray/agent.sock), readable only by your user. Anything running as you can reach it, which is why the allowlist and the off switch exist.
