Why people ask
A browser extension works inside your own Chrome, on LinkedIn's pages, while your computer is on and the tab is open. That has three consequences people run into: the laptop has to stay awake, everything happens from the same address you browse from, and the extension is sitting in the page LinkedIn serves you. Some people also just don't want another extension with access to their LinkedIn tab.
How it works here instead
Each customer gets their own persistent cloud browser on our server. It stays signed in to LinkedIn as you, and every tool works from it: Auto Connect, Message Sender, Auto Liker, Profile Scraper and Outreach sequences. Actions go through the same internal web API LinkedIn's own site uses, from that browser. We never open profile pages in a scraping loop.
Your computer is not involved. You start a run from any browser, on any device, and close the tab. The run carries on and its live log is there when you come back.
What you paste in, once
Your LinkedIn li_at cookie and your browser's user agent. The cookie is LinkedIn's signed-in session; the cloud browser uses it to be signed in as you, so we never ask for your LinkedIn password. How to get your li_at cookie has the steps for each browser.
The cookie is encrypted before it is stored, the key sits in a separate locked file on the server, it is never written to logs or shown back to you, and Delete my cookie removes it and wipes the cloud browser's LinkedIn session.
What changes for you
- Your computer can be off. Sequences run on their own, days apart, from the cloud browser.
- The session comes from your own static IP address in the country you pick (India, the United States, the United Kingdom, Canada, Germany, France, the Netherlands or Singapore), used only by your account, not from your home or office connection.
- Nothing to install or update. When LinkedIn changes something, we change it on the server.
- Nothing in your own Chrome has access to your LinkedIn tab.
What doesn't change
LinkedIn's terms still don't allow automation, wherever it runs. The caps (20 connection requests a day and at most 100 in any 7 days, 30 messages and 50 likes a day), the random gaps, and the stop on any security check matter as much in the cloud as in an extension. Running from a server lowers some risks; it does not remove the risk.
So what do you install?
Nothing. The app is a website. You sign in, paste the cookie once, and start runs from the same place on your laptop or your phone. There is no desktop app, no extension and no agent to keep running. The cloud browser is ours to keep up; you never see it except as the screenshot of your own profile that the probe on the cookie page shows you.
Keeping the cloud browser signed in
The cookie you paste is the session LinkedIn gave the browser you copied it from. Signing out in that browser, changing your LinkedIn password or using Sign out of all sessions ends it, for your browser and for the cloud browser alike. So after you copy it, close the LinkedIn tab rather than signing out. When it does stop working, replacing it takes a few minutes and your leads and sequences stay where they were.
You can watch any run from the app: every request, message or like shows up in the live log, with a cancel button, and the daily Telegram report sums up the day.
When an extension is the better choice
If you want to watch every action on your own screen, or you want the lowest possible price and don't mind keeping a computer on, an extension or desktop app may suit you better. Octopus CRM is a Chrome extension from $9.99 a month, and Linked Helper is desktop software from $15 a month with proxies bought separately. Both pages say where each one wins.