{"version":"2.1.225","anchor":"artifact-comments-can-be-filtered-to-one-thread-or-resumed-w","canonical_anchor":"artifact-comments-can-be-filtered-to-one-thread-or-resumed-w","heading":"Artifact comments can be filtered to one thread or resumed with a cursor","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/artifact-comments-can-be-filtered-to-one-thread-or-resumed-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Artifact comments can be filtered to one thread or resumed with a cursor\n\nYou can read one artifact comment thread by id, or resume a cut-off listing with a cursor.\n\n**What**\n\nThe Artifact tool's `comments` action takes a `thread_id` to read a single thread and a `cursor` to continue a listing that was cut off by the size cap. Results echo back `thread_filter` and `cursor` so the model knows which view it is looking at.\n\n**Details**\n\n- `thread_id` and `cursor` are mutually exclusive and both must be lowercase UUIDs, each with its own validation error and error code\n- when a requested thread is not in the result, the model is told to re-run `comments` without `thread_id` for the full list\n- truncated listings carry a hint to re-run with `cursor`, and resumed listings carry a \"Resumed from the cursor:\" note; threads are listed newest first\n- the tool-use line renders counts such as \"read 1 comment thread (filtered)\"\n- available to anyone who can use the Artifact tool; neither field existed in 2.1.224\n\n**Evidence**\n\n`` `thread_id` (read one thread) and `cursor` (continue the list) cannot be combined \u2014 pass one. ``, `thread_filter`\n\n- Area: Artifacts\n- Names: `thread_id`, `cursor`, `comments`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}