You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release
Unclear Which tool these document queries belong to, and whether it is available to everyone, is not established.
What
An Artifact can hold a small database of documents that Claude can query. Two things change when Claude runs one of these queries with order_by, which sorts the results by a chosen field:
The result now includes ordered_by: {field, limit}. This repeats the field the results were sorted by and the limit that was actually applied, including a limit Claude did not set itself.
Ordered queries return a single page. When that page is full, the tool output warns that more results may exist beyond the ones shown. It tells Claude to raise query.limit, or to drop query.order_by and page through the results with query.cursor.
Why
Before, an ordered query gave no sign that it had stopped at a limit, so Claude could treat a partial list as the complete set. Claude now sees the limit that was used and is told how to fetch the rest.
Read from
Names in the bundlequery.order_by
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich tool these document queries belong to, and whether it is available to everyone, is not established.
