linkedin-feed

Reads the logged-in account's home timeline. Each post's authorSlug feeds linkedin-get-profile; each urn feeds linkedin-react, linkedin-comment-post or linkedin-get-post.

Resolves in a single bridge call: it pages feed/updatesV2?q=chronFeed same-origin and reads the normalized payload, so it works from any page and never touches the DOM. v1 grepped the server-rendered /feed/ HTML for fields LinkedIn no longer ships (it moved the feed to SDUI) and fell back to DOM selectors that match nothing, it returned bare urns with every other field null or 0.

The extractor lives as text in the site's localStorage (key linkedin-feed) and is rebuilt on each call with synchronous eval. It is stored once and then persists across navigation and browser restarts, so on every run except the first it is already there.

Sponsored posts are included by default and flagged isPromoted: true (detected from the update's sponsoredTracking metadata, not from a locale-dependent label). Pass skipPromoted: true to drop them.

Default action: just call (step 1). The call itself reports NEEDS_STORE when the extractor is missing or out of date, only then do you store it (step 2) and call again.

Versioning. The stored extractor is gated by VER (must match the version in the frontmatter above). Both snippets carry VER = "2", keep them in sync with the frontmatter. When evaluate.js changes, bump version and VER in both snippets: the next call sees the mismatch, returns NEEDS_STORE, and re-stores automatically. Storage stays at two keys (linkedin-feed and linkedin-feed:ver), overwritten each store, versions never accumulate.

1. Call (do this every run, params only, single bridge call)

await (() => {
  const KEY = "linkedin-feed", VER = "2";
  const s = localStorage.getItem(KEY);
  if (!s || localStorage.getItem(KEY + ":ver") !== VER) return 'NEEDS_STORE';
  const fn = eval('(' + s + ')');
  return fn(document, { count: 20 });
})()

Returns the timeline posts. If it returns the string 'NEEDS_STORE', the extractor is missing or stale in this browser → do step 2 once, then run this exact call again.

Run this snippet verbatim. Never add an await before the eval, only the outer await is allowed; a pre-eval await trips LinkedIn's CSP and the call fails.

2. Store (only when step 1 returned NEEDS_STORE; persists until localStorage is cleared)

While logged in at https://www.linkedin.com/feed/ (the JSESSIONID cookie must be present), evaluate the following with the bridge, replacing <FN> with the contents of evaluate.js (the ( async (root, params) => { ... } ) function). Keep VER equal to the call snippet's:

(() => {
  const KEY = "linkedin-feed", VER = "2";
  const fn = (<FN>);
  localStorage.setItem(KEY, String(fn));
  localStorage.setItem(KEY + ":ver", VER);
  return 'stored';
})()

Returns "stored". The extractor passes through the model only here, once. Then go back to step 1.

Errors

• NEEDS_STORE → extractor missing or version-mismatched in this browser; run step 2 once, then retry step 1.
• re-auth / no JSESSIONID → no LinkedIn session in this browser; log in once.
• tool-broken → LinkedIn changed the API shape; recapture the extractor.

Success assertion

{ "type": "json", "jsonPath": "count" }