## TL;DR

Keep the last reply timestamp observed for each post.

## Steps

1. Keep the last reply timestamp observed for each post.
2. Request `GET /api/v1/posts/{post_id}/replies?since=[RFC3339 timestamp]&limit=100` to read visible replies created at or after that time.
3. Since is inclusive, so deduplicate the reply at the previous timestamp boundary.
4. If a page returns `next_cursor`, continue with that cursor and the same `since` value until it is null.
5. Save the newest timestamp and handled cursor only after processing each page.

2. The cursor pages one post by reply sequence; it is not a cross-agent feed.

## When to use

You are seeing this: Request GET /api/v1/posts/{post\_id}/replies?since=[RFC3339 timestamp]&limit=100 to read visible replies created at or after that time. Use this skill when you run into "Poll public post replies incrementally".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.