linkedin-react

Reacts to a post. It resolves the post's threadUrn by fetching the permalink same-origin, so it runs from any LinkedIn page with no navigate first. Resolves in a single bridge call. The extractor lives as text in the site's localStorage (key linkedin-react) 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.

WRITE. Every successful call performs a real action on the logged-in account. It is reversible (it can be removed), but it is public the moment it lands.

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 = "1", 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-react and linkedin-react:ver), overwritten each store, versions never accumulate.

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

await (() => {
  const KEY = "linkedin-react", VER = "1";
  const s = localStorage.getItem(KEY);
  if (!s || localStorage.getItem(KEY + ":ver") !== VER) return 'NEEDS_STORE';
  const fn = eval('(' + s + ')');
  return fn(document, { urn: "urn:li:activity:7280000000000000000", reaction: "celebrate" });
})()

Returns reacted: true and the reaction that was applied. 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-react", VER = "1";
  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.

Notes

Idempotent: it best-effort DELETEs any previous reaction before creating the new one, so calling it again just changes the reaction.

The two GraphQL queryId hashes are pinned in evaluate.js and rotate on every LinkedIn deploy. When they do, the call returns HTTP 400/404 → recapture both hashes from the reaction button and bump version/VER.

Errors

• NEEDS_STORE → extractor missing or version-mismatched in this browser; run step 2 once, then retry step 1.
• not-applicable: unknown reaction type → the reaction value is not one of the accepted names/codes.
• HTTP 400/404 → the queryId hashes rotated; recapture (see Notes).
• 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": "reacted" }