chrome-go-codes

Go Codes

A Chrome extension that maps short codes to URLs and triggers them from the omnibox. Mappings sync across devices via Chrome profile.

Type go in the address bar, hit space (or tab), enter a short code, press Enter — the active tab navigates to the mapped URL.

Features

• Omnibox keyword: go <code> jumps to the mapped URL.
• Sync across devices: stored in chrome.storage.sync (one key per code).
• Manage page: click the toolbar icon to add or delete codes (re-adding a code overwrites it).
• 500-code limit with live counter, progress bar, and color-coded warning thresholds.
• Material You UI: built with Material Web (MD3) components and design tokens.
• System theme aware: light/dark mode follows prefers-color-scheme via the M3 baseline palette.
• Search & sort: filter saved codes and toggle A→Z / Z→A on the manage page.
• Minimal permissions: only storage. No tab tracking, no host permissions.

Install (unpacked)

The Material Web bundle (src/vendor/material.js) is committed, so you can load the extension without a build step.

1. Clone or download this repo.
2. Open chrome://extensions.
3. Toggle Developer mode (top right).
4. Click Load unpacked and select the src/ directory.
5. (Optional) Pin the extension from the puzzle-piece menu so the icon appears in the toolbar.

Development

The UI uses Material Web components. They’re bundled locally (the MV3 script-src 'self' CSP blocks remote scripts) into a single self-contained ESM file via esbuild.

npm install        # install @material/web + esbuild
npm run build      # bundle build/material-entry.js -> src/vendor/material.js
npm run watch      # rebuild on change (non-minified)

Edit build/material-entry.js to add or remove Material components from the bundle. Re-run npm run build and commit the regenerated src/vendor/material.js. The release workflow also rebuilds it from source before packaging.

Usage

Add a code

1. Click the toolbar icon — opens the manage page.
2. Enter a short code (no spaces) and a URL. URLs without a scheme get https:// prepended automatically.
3. Click Add.

Use a code

In any new tab or the address bar:

go <space> <code> <Enter>

The active tab navigates to the URL mapped to <code>. Modifier keys (Ctrl/Cmd+Enter, etc.) follow Chrome’s standard omnibox behavior — open in new tab, background tab, etc.

Delete a code

Click the trash icon next to the row on the manage page.

Customizing the omnibox keyword

The keyword is hardcoded to go in src/manifest.json. Chrome does not allow runtime changes to manifest values. To change it:

1. Edit src/manifest.json → omnibox.keyword.
2. Reload the extension at chrome://extensions.

File structure

build/
└── material-entry.js   esbuild entry — imports the Material Web components used
src/
├── manifest.json       MV3 manifest, omnibox + action config
├── background.js       Service worker: omnibox handler, toolbar click handler
├── manage.html         Manage UI markup (Material Web components)
├── manage.css          Material You (MD3) tokens + layout, adaptive light/dark
├── manage.js           CRUD logic against chrome.storage.sync
├── vendor/
│   └── material.js     Bundled @material/web (committed, regenerated by build)
└── icons/              16/48/128 PNGs

Storage schema

Each code is stored as its own top-level key in chrome.storage.sync (which is scoped per-extension, so no risk of collision with other extensions):

key:   "<shortcode>"
value: "<url>"

Keys starting with _ are reserved for future metadata (e.g., settings). User-entered codes cannot begin with _.

Limits (Chrome):

• 8 192 bytes per item
• 512 items total per extension
• 102 400 bytes total

The extension caps users at 500 codes, leaving headroom.

Design notes

• Material You (MD3): Material Web components (buttons, outlined text fields, icon buttons, linear progress, dialog, checkbox) themed with the M3 baseline (purple) color roles. All --md-sys-color-* tokens live in manage.css, so components and hand-rolled surfaces stay in sync. Light/dark follows prefers-color-scheme.
• Font: system UI stack — M3’s --md-ref-typeface-* tokens are remapped to the native stack so no web fonts ship.
• Bundled, not remote: Material Web is vendored into src/vendor/material.js so it loads under the MV3 script-src 'self' CSP.

Roadmap ideas

• Import/export JSON for backup or migration
• Omnibox suggestions while typing
• Quick add via popup
• Bulk edit on the manage page

License

MIT

This site is open source. Improve this page.