Description
The twitter-cli tool caps the number of followers/following users it can fetch at 500, regardless of the --max flag value. This limit is imposed by the tool itself, not by X.com's API.
Root Cause
In client.py:
- Line 72:
_ABSOLUTE_MAX_COUNT = 500 (hardcoded ceiling)
- Line 148:
self._max_count = min(int(rl.get("maxCount", 200)), _ABSOLUTE_MAX_COUNT)
- Line 802 in
_fetch_user_list(): count = min(count, self._max_count) applies the cap before pagination begins
Evidence
The pagination logic itself works correctly - it fetches up to 40 users per page with cursor-based pagination. However, the loop at line 809 (while len(users) < count) uses the capped count, so it stops at 500 regardless of X.com's capability.
Request
Either:
- Increase
_ABSOLUTE_MAX_COUNT to a higher value (e.g., 1000 or 2000)
- Remove the hardcoded ceiling entirely and let users configure it via config
- Or document this limitation clearly
Users who follow many accounts (>500) cannot retrieve their full following list with the current implementation.
Description
The twitter-cli tool caps the number of followers/following users it can fetch at 500, regardless of the
--maxflag value. This limit is imposed by the tool itself, not by X.com's API.Root Cause
In
client.py:_ABSOLUTE_MAX_COUNT = 500(hardcoded ceiling)self._max_count = min(int(rl.get("maxCount", 200)), _ABSOLUTE_MAX_COUNT)_fetch_user_list():count = min(count, self._max_count)applies the cap before pagination beginsEvidence
The pagination logic itself works correctly - it fetches up to 40 users per page with cursor-based pagination. However, the loop at line 809 (
while len(users) < count) uses the capped count, so it stops at 500 regardless of X.com's capability.Request
Either:
_ABSOLUTE_MAX_COUNTto a higher value (e.g., 1000 or 2000)Users who follow many accounts (>500) cannot retrieve their full following list with the current implementation.