v0.1.0 · Chrome / Chromium · MIT licensed
Inputr isn't on the Chrome Web Store yet. Until v1 ships, you side-load the release zip. Two minutes, end to end. No accounts, no telemetry, no network calls. The extension just runs.
Chrome lets any user load an unpacked extension folder. That's exactly what we're doing. Nothing here touches a remote server, nothing here asks for permissions Inputr doesn't already declare in its manifest.
Grab inputr-0.1.0-chrome.zip from the GitHub
release page. It's ~1 MB. The same artifact CI builds from
the source tree, signed only by the git commit it was built
from.
Double-click the zip (macOS) or right-click and
Extract All (Windows). You'll get a folder named
inputr-0.1.0-chrome. Move it somewhere stable
like ~/Applications. If you delete this folder
later, the extension disappears with it.
unzip inputr-0.1.0-chrome.zipchrome://extensions.
Paste the URL directly into the address bar. Chrome blocks
links to chrome:// URLs on purpose, so a
button can't take you there. Arc, Brave, and Edge accept
the same URL.
Top-right corner of the Extensions page. The toggle reveals three new buttons: Load unpacked, Pack extension, and Update. Inputr only needs the first. Developer mode stays on across browser restarts and only affects the Extensions page.
Select the unzipped inputr-0.1.0-chrome
folder, not the zip and not a parent directory. Chrome
reads manifest.json, registers the extension,
and the orange Inputr tile appears on the page. That's it.
Inputr is live in every tab from this moment on.
manifest.jsonClick the puzzle-piece icon next to your address bar, find Inputr in the dropdown, hit the pin. The icon glows orange when Inputr detects an upload box on the current page. That's your signal to click it.
Head to linkedin.com/in/me/edit/banner. The
Inputr toolbar icon should switch from grey to orange within
about a second. Click it and the side panel opens with the
banner's exact 1584 × 396 target preselected. If that
happens, you're done.
All checks run locally. No network.
You picked the wrong folder, or the zip is still zipped.
Load unpacked wants the folder that contains
manifest.json. Open the folder you selected,
confirm manifest.json is sitting right there at
the top, then try again.
Chrome remembers the path to the unzipped folder, not the contents. If you moved or deleted that folder, the extension unloads. Put the folder back where it was, or hit Load unpacked again and re-select its new home.
Chrome shows that nag once per session for any side-loaded extension. Click Cancel, never Disable. The banner will be retired once Inputr is on the Chrome Web Store. v1 is the target for that.
Download the next zip, unzip it, and either replace the old folder in place or pick the new folder via Load unpacked. Chrome then keeps your settings. Auto-updates are a Web Store feature and arrive with v1.
Inputr is MIT licensed and entirely client-side. The release
zip is built from the
main branch
with npm run zip. If you'd rather build it
yourself, the commands below produce the same artifact.
git clone https://github.com/namanbarkiya/inputr.git
cd inputr
npm install
npm run zip
# → .output/inputr-0.1.0-chrome.zipInputr ships free. No accounts, no tracking, no upsell. Open an issue or a PR if you spot something off. The Chrome Web Store listing arrives with v1.