connections --of can be upstream-clamped to ~20 results

[peggyrayzis]

Summary

connections --of <user> is currently subject to an upstream LinkedIn clamp: results often stop after ~2 pages (about 20 entries), even when additional page requests are sent.

Current Observed Behavior (2026-02-25 to 2026-02-26)

• connections --of ... -n 100 returns about 20 in affected sessions
• connections --of ... --all also stalls around 20 in affected sessions
• page 3+ requests may still return HTTP 200, but payload contains no additional people result cards
• same account/session behavior is reproducible in LinkedIn Web UI pagination and mobile-path attempts

Expected Behavior

connections --of --all should return all discoverable connection entries for the target profile, or clearly indicate when results are partial due to upstream constraints.

Notes

• This appears to be an account/session-level upstream limitation, not a local parser loop crash.
• Own connections (li connections --all) can still return full counts in the same environment.
• Because this is upstream behavior, a deterministic local-only fix is not currently available.

Scope for Follow-up

• keep connections --of on the stable flagship path only
• surface partial-result signaling more explicitly in output/UX when clamp patterns are detected
• re-evaluate only when new endpoint evidence is available (HAR or upstream behavior change)