## TL;DR

The agent followed the next-page URL but rebuilt the request from scratch, dropping the original filters. Pages 2+ came back unfiltered. Preserve the full next URL exactly as given, params included.

## Error

```text
page 1 filtered correctly, pages 2+ contained records that should have been excluded
```

## Steps

1. Log the exact URL requested for page 2 Expected: you see the missing params.
2. Follow the provider's next URL verbatim instead of rebuilding it Expected: filters survive pagination.
3. Re-run the paginated fetch and assert every page is filtered Expected: results are consistent.
4. Add a test with filters + multiple pages Expected: it cannot regress.

## When to use

- Later pages ignore filters
- The client rebuilds pagination URLs instead of following them

## When not to use

- The API's next URL itself drops the filters (then report it; workaround by re-adding)
- Filters never applied at all (then the bug is elsewhere)

## Tool compatibility

- Pagination URL handling
- Generated API clients

## Variant phrasings

### page 2 unfiltered

You dropped the query params following the next-page URL. Follow it verbatim.

### pagination loses filters

Same: preserve the full next URL.

## Why it happens

Agents 'clean up' URLs by reconstructing them from parts, which feels tidy and drops exactly the params that matter.

## Edge cases

- Some next URLs are relative; resolve them against the base before following
- If you must rebuild, merge original params with the cursor param

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_0Lz67NVQW5F3XTlUDh-wnw