ilml-plugin-linkedin 1.17.1 → 1.18.0

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## 1.18.0
+- **The automation now runs as one consistent browser "device", so LinkedIn stops treating every run as a brand-new sign-in.** Previously each command opened a throwaway browser profile — which looked like a new device to LinkedIn every time, triggering "new device" emails, early session drops, and repeated login/password prompts. The plugin now keeps a persistent Chrome profile per account (stored next to your saved session), so LinkedIn sees the same trusted device across runs: fewer security emails, fewer forced re-logins, lower ban-risk. Your existing session carries over automatically on the first run after updating — no re-login needed.
+- **`ilml linkedin login` is clearer about what to do.** It opens the browser and, if that profile is already signed in, tells you so and just asks you to press Enter to re-save. Otherwise you sign in manually, then **press Enter in the terminal** to save your session — don't close the window yourself; it closes automatically once saved. (The old docs said "close the window", which could actually lose the login — now fixed.)
+- **`apply` no longer silently runs on a logged-out page.** If your session has expired, it now detects LinkedIn's login wall and stops with a clear "Run: ilml linkedin login" instead of scraping an empty page and reporting "no jobs".
+- **Clearer session messages across commands.** "Cookies expired" is now "not logged in, or session expired" (accurate on a first-ever run too), and a command warns up front when no saved session is found.
+- **Cleaner recovery when the browser crashes mid-run.** A hung browser is now fully shut down before restarting into the same profile, avoiding a rare profile-lock clash on restart.
+- **If the browser profile ever gets stuck** (e.g. Chrome crashed mid-run): delete the `chrome-profile/` folder in your plugin state and run `ilml linkedin login`. The README's "First-time LinkedIn login" section documents this, plus `LINKEDIN_CHROME_PROFILE_DIR` to store the profile elsewhere. No schema change — your contacts, conversations, jobs, and quota data are untouched.
+
+## 1.17.2
+- **Sending a message is now reliable, and never falsely reports "sent".** Two fixes to `messages --send` (and the draft push): (1) it opens the conversation **directly from the person's profile URL** instead of searching for them by name — the name search was failing on accented names (e.g. "Marc-André"), refusing to send to a valid contact; (2) it now **verifies the message actually went through** before reporting success — it only says "sent" (and marks the contact messaged) once the composer has cleared and no LinkedIn error appeared. Previously it declared "sent" the instant it clicked Send, so a send that LinkedIn rejected with a "try again" error still got recorded as sent. No schema change.
+
 ## 1.17.1
 - **Fixed: `sync-connections` was saving a contact's name with their headline glued onto it** (e.g. "Bijan SaniiSoftware Industry Executive" instead of "Bijan Sanii"). On the connections page LinkedIn puts the name and headline inside one link, and the scan read them concatenated with no separator. It now reads the name from the rendered first line only, so new scans store clean names. (Contacts already saved with a glued name still work — the name is display-only — and are tidied separately.) No schema change.
 

package/README.md

@@ -152,7 +152,7 @@ LinkedIn requires an authenticated browser session, so a one-time login is neede
 ilml linkedin login
 ```
 
-A real browser window opens. Sign in to LinkedIn (manually solve any captcha or 2FA). When you see your feed, close the window — your session cookies are saved locally for future runs.
+A real browser window opens. Sign in to LinkedIn (manually solve any captcha or 2FA). When you see your feed, **come back to this terminal and press Enter** to save your session — don't close the browser window yourself, cookies are captured on Enter and the window then closes automatically. (If the profile is already signed in, the command detects it and just asks you to press Enter to re-save.)
 
 Sessions live in your active ilml scope (`<scope>/.ilivemylife/plugins-state/linkedin/cookies.json`), so:
 
@@ -160,6 +160,19 @@ Sessions live in your active ilml scope (`<scope>/.ilivemylife/plugins-state/lin
 - Plugin updates do **not** wipe your session — you don't need to re-login after `ilml plugin update linkedin`.
 - `ilml logout` does wipe the session in that scope (alongside other user-tied data) — clean handoff between users on a shared machine.
 
+### The browser profile (one trusted device)
+
+To keep LinkedIn treating the automation as **one consistent device** — instead of a fresh "new device" every run (which triggers "new device" emails, early session drops, and higher ban-risk) — the plugin keeps a **persistent Chrome profile** per account, next to your session:
+
+```
+<scope>/.ilivemylife/plugins-state/linkedin/chrome-profile/<account>/
+```
+
+You normally never touch it. Two things worth knowing:
+
+- **Resetting it:** if the profile ever gets stuck or corrupted (e.g. Chrome crashed mid-run), delete that `chrome-profile/` folder. The next command rebuilds a clean profile and seeds it from your saved session automatically — no re-login needed. Only if the saved session has also expired do you run `ilml linkedin login` to sign in again.
+- **Pointing it elsewhere:** set `LINKEDIN_CHROME_PROFILE_DIR` to an absolute path to store the profile somewhere specific (e.g. a faster disk). Optional — leave it unset to use the default location above.
+
 ## Daily commands
 
 | Command | What it does |