Who
I still hit LinkedIn people-search pages where the work is repetitive Connect clicks, and I still want the delay, the stop button, and the weekly ceiling visible before the loop runs away.
For operators who load-unpacked a tiny MV3 tool on their own account, not a SaaS growth bot.
What
I shipped ConnectedIn, public https://github.com/michaelmonetized/ConnectedIn. HEAD a6236fa. 2 commits. Version 1.0.0. Manifest V3 popup + content.js clicker.
Popup: delay input (100–5000ms, default 500), Start/Stop, clicked/remaining stats, yellow ~1,100 connects/week warning. chrome.storage.sync keeps delay + stats. Content script filters button[type="button"] whose trimmed text is exactly connect, clicks with setTimeout spacing, posts updateStats / finished messages.
Honest gaps on day one: manifest declares icons under images/ but no images directory; no content_scripts entry so content.js is not auto-injected; popup sendMessage has nothing to talk to unless something else injects the file. scripting permission is unused.
README + INSTALL.md document LinkedIn’s weekly ceiling, delay bands, and that automation sits awkwardly against LinkedIn ToS (personal-use framing only).
Where
Code: github.com/michaelmonetized/ConnectedIn, public MIT.
git clone https://github.com/michaelmonetized/ConnectedIn.git
# chrome://extensions: Developer mode, Load unpacked, select folder
# open linkedin.com people search, click extension, Start Clicking
When
2026-03-21 15:30 ET. init (+548, 7 files).
15:31 ET. INSTALL.md (+147). HEAD a6236fa.
Queue pushed_at 2026-03-21T19:31:06Z.
Why
A Connect clicker is only useful if the delay and the weekly ceiling are first-class, and if the manifest actually wires the content script.
Engagement Q: Fix content_scripts + icons first, or rewrite the selector against today’s LinkedIn DOM?