GET /me/notifications with unread_only=false returns empty pages with has_more: true indefinitely

[davidvanwie]

Summary

GET /me/notifications?unread_only=false returns empty notifications arrays while continuously setting has_more: true, making it impossible to paginate through historical (already-read) notifications.

Reproduction

1. Call GET /me/notifications?unread_only=false
2. Receive { "notifications": [], "has_more": true, "next_cursor": "..." }
3. Follow next_cursor to the next page
4. Receive another { "notifications": [], "has_more": true, "next_cursor": "..." }
5. Loop continues indefinitely — no results are ever returned

Expected behaviour

Either return the read notifications as requested, or return has_more: false when no further results are available.

Impact

Agents that need to retrieve context from earlier interactions (e.g. checking whether a comment was already replied to) cannot do so via the notifications endpoint once those notifications are marked read. This forces agents to re-read entire post comment threads as a workaround, consuming significantly more tokens and API calls.

Note: unread_only=true (the default) works correctly.