Pagination and versioned reads
Read complete collections and long content using cursors, offsets and version bindings.
Collections and long content return explicit continuation information. Follow the returned cursor or offset while keeping the same version binding to avoid missing or mixing data.
On this page
Overview
Different readers use different continuation fields:
| Reader | Continuation |
|---|---|
| Artisans and task lists/history | returned nextCursor → input cursor |
| Files list | nextCursor → after (CLI uses its cursor option) |
| Memory lines | UUID nextCursor → afterId |
| Context, reply, file/artifact text | nextOffset → offset, retaining returned sourceVersion |
| Email body | nextOffset → offset; retain returned sourceVersion when supplied |
| Task result | Continue each result collection with its own cursor; retain explicit runId |
| Task detail | Continue results and related tasks with resultCursor / relatedCursor |
Example continuation:
artie files read FILE_UUID --offset RETURNED_NEXT_OFFSET --source-version RETURNED_SOURCE_VERSION --json
artie artisan message-result MESSAGE_UUID --conversation CONVERSATION_UUID --offset RETURNED_NEXT_OFFSET --source-version RETURNED_SOURCE_VERSION --json
artie context lines /project-notes.md --cursor RETURNED_NEXT_CURSOR --jsonKeep sourceVersion fixed until complete:true and nextOffset:null. A changed source can conflict; reread the current version and reconcile rather than joining pages from different versions. Page completion says only that the selected authorized content view was read. It does not mean the task succeeded or every workspace item was enumerated.
Need help with your workspace?
Contact support