5 client-side LinkedIn tools — all opt-in, all local to your browser.
These tools are off by default. Enable the ones you want in the extension's Options page under LinkedIn Features. Everything runs in your browser — Video Controls Plus never automates LinkedIn actions or sends your data anywhere.
Connection Tagger is a local organizer that lets you label your LinkedIn connections with colored tags (by industry, role, relationship, or priority) and attach private notes. It reads connection names and headlines only from the connections page you are currently viewing and stores everything in your browser; it does not message, follow, or change anything on your LinkedIn account.
Example: After a conference you open your connections page, bulk-select the twelve people you just added, and apply your custom "Conf 2026" tag plus a note like "met at the API panel" so you can find them again next quarter.
Does tagging change anything on my LinkedIn profile or notify the person? No. Tags and notes are stored privately in your browser only. Nothing is sent to LinkedIn and the connection is never notified.
Where is my tag and note data stored? In your browser's local extension storage. It never leaves your device unless you choose to export it to a CSV or JSON file yourself.
Is the auto-tagging powered by AI? No. Auto-tag suggestions work by matching keywords you define against a connection's headline text. There is no AI or cloud service involved.
Can it tag my entire connection list automatically? It only sees the connection cards currently rendered on the page you are viewing. You scroll and tag the people you want; it does not crawl your whole network in the background.
What happens to a connection's tags if I delete a tag? Deleting a tag removes it from every connection that had it and also removes any auto-tag rule pointing to it. The connections themselves and their notes stay.
Tags, notes, and the auto-tag keyword rules live only in your browser storage and are never uploaded. The tagger only sees connection cards rendered on the page you are currently on, so it cannot tag connections you have not scrolled to. Auto-tag suggestions are simple keyword matches against the headline text, not AI, and LinkedIn layout changes can affect which cards are detected.
Inactive Connection Detector tracks interactions you log with each connection and flags people you have not engaged with for a while (90 days by default) so you can decide who to reconnect with. It works from interactions you record yourself in the extension, not from your real LinkedIn message history, and it only drafts reconnection message text for you to copy; it never sends anything.
Example: You set the threshold to 120 days, log the occasional message and post like as you go, then run a scan before the holidays and get a ranked list of past collaborators you have gone quiet with, each with a ready-to-edit "it's been a while" draft.
Does it automatically read who I have messaged on LinkedIn? No. It only counts interactions you log yourself inside the extension. It does not access your real LinkedIn messages or activity feed.
Does it send reconnection messages for me? No. It generates draft text with the person's first name filled in. You copy it and send it manually on LinkedIn if you want to.
How is relationship strength calculated? By a local rule of thumb: how many interactions you logged in the last 90 days and whether they went both ways. It is a heuristic, not data from LinkedIn.
Can I change what counts as inactive? Yes. The default threshold is 90 days, and you can set it to whatever number of days fits how often you like to stay in touch.
Is any of my interaction data uploaded? No. Interaction records, templates, and settings are stored only in your browser and never leave your device.
The detector only knows about interactions you log yourself; it cannot read your actual LinkedIn inbox or activity history. Relationship strength (strong, moderate, weak, dormant) is a simple heuristic based on how many interactions you recorded and how recent they are, not an official LinkedIn metric. Reconnection messages are templates with the contact's first name filled in, and you must send them manually. All of this data stays in your browser.
Connection Request Assistant helps you write better connection-request notes using reusable templates that auto-fill the person's first name and headline keywords from the profile you are viewing, and it lets you track which requests were accepted. It only produces draft text and keeps records locally; it does not send connection requests or automate anything on LinkedIn.
Example: Before sending a request to a designer, you open their profile, pick the Collaboration template, and the assistant fills in their first name and a keyword from their headline; you tweak one line, paste it into LinkedIn's note field, and send it yourself.
Will it send connection requests automatically? No. It only generates and fills in draft note text. You copy it into LinkedIn and send the request yourself, which keeps it compliant with LinkedIn's terms.
Where do the acceptance rates come from? From outcomes you log yourself after sending requests. The assistant cannot detect acceptances automatically; you mark each request accepted or declined.
Are the best-time suggestions based on my data? No. They are fixed, general timing tips (such as Tuesday-Thursday mornings), not an analysis of your personal account activity.
Does the A/B testing use any cloud service? No. The A/B test simply compares the acceptance numbers you record for two templates, entirely within your browser.
What profile information does it read? Only the name and headline visible on the profile page you currently have open, used to fill placeholders like {firstName} and {industry}.
The assistant never sends requests or clicks Connect for you; it only prepares draft text you copy manually, keeping it TOS-friendly. Acceptance rates and A/B test results are computed only from outcomes you record yourself. The "best time to send" suggestions are fixed general guidance (Tuesday-Thursday mornings), not personalized analysis of your account. Profile details are read only from the page you are on, and all templates and stats stay in your browser.
Quick Profile Preview shows a small hover card with a person's name, headline, location, and a highlight or two without making you click away from the page you are on. It builds the preview only from information already visible on the current page and caches it briefly in your browser; it does not fetch or load other people's profiles in the background.
Example: While scanning search results, you hover over each name to read their headline and current role in a popup, deciding who is worth a full profile visit without opening a dozen new tabs.
Does the preview load other people's full profiles in the background? No. It only shows information already rendered on the page you are on. On a list it uses the name and headline from that list; full details appear only when you are on the person's own profile page.
Is preview data sent anywhere? No. Previews are cached in your browser's local storage for about 30 minutes and are never uploaded.
Why does a preview sometimes show little detail? Because it only uses what is on the current page. List pages expose limited data, so the card is light; visiting the actual profile shows more.
Does the Message button send a message? No. It just opens LinkedIn's own message-compose page so you can write and send the message yourself.
Can I control when the card appears? Yes. You can change the hover delay and turn individual sections (mutual connections, highlights, recent posts) on or off in the feature settings.
The preview only uses data already present on the page you are viewing; when you are on a list it shows the name and headline hints from that list, and richer details (photo, highlights) appear when you are actually on someone's profile. It does not silently load remote profiles, so previews on a list page are intentionally lightweight. Cached previews expire after about 30 minutes and stay only in your browser. The Message button just opens LinkedIn's compose page; it does not send anything.
Mutual Connection Analyzer reads the mutual connections listed on the page you are viewing, organizes them, and helps you draft a warm-introduction request to ask one of them to introduce you to a target person. It generates introduction message text and tracks intro outcomes locally; it does not contact anyone or send introductions for you.
Example: You want an introduction to a hiring manager and see you share five mutual connections. You run the analyzer, pick the colleague you know best, copy the casual intro template, add "I'm exploring roles on her team," and message that colleague yourself to ask for the intro.
Does it find all my mutual connections with someone automatically? No. It only reads the mutual connections shown on the page you are currently viewing. Mutuals LinkedIn does not display are not captured.
Does it send the introduction request? No. It generates a draft intro message for you to copy. You send the request to your mutual connection yourself on LinkedIn.
How does it decide who is the best introducer? It sorts mutuals by a local relationship-strength heuristic. Because the page rarely exposes real strength, many show as "unknown," so treat the ranking as a starting point.
Is my analysis and intro data stored online? No. Everything is kept in your browser's local storage. Cached analyses expire after about 24 hours, and exports happen only when you trigger them.
Are the success rates real LinkedIn data? No. They are calculated only from outcomes you log yourself when you mark an intro request accepted or a connection made.
The analyzer only reads mutual-connection cards that are actually rendered on the page you are on; it cannot discover mutuals that are not shown. Intro suggestions and confidence levels are based on a simple relationship-strength heuristic, and since the page does not always expose strength, many mutuals appear as "unknown." It produces draft intro messages only and never sends them. Analyses, intro requests, templates, and stats are stored only in your browser, and cached analyses expire after about 24 hours.
All features
Last updated 2026-11-10 by the Video Controls Plus team.