{"version":"2.1.284","anchor":"probe-read-back-requested-for-list-files-actions","canonical_anchor":"probe-read-back-requested-for-list-files-actions","heading":"Artifact and file-listing requests can ask for a read-back","tier":"internal","area":"Remote Hosts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/probe-read-back-requested-for-list-files-actions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Artifact and file-listing requests can ask for a read-back\n\nA new readBack option asks the server to read state back for artifact frame requests and list_files actions, with read_back noted on share status\n\n**Unclear.** Which tool or connector this belongs to is not known.\n\n**What**\n\nA new read-back option appears in several places where Claude Code talks to remote artifacts (content Claude publishes or shares) and connected resources:\n\n- The artifact frame boot request takes a new `readBack` option, which adds `&readback=1` to the `\/api\/frame\/...` address.\n\n- The check run before a remote action now receives an options object, `{ readBack: h.action === \"list_files\" }`, so `list_files` actions ask for a read-back. Before, it was called with only the slug, context and action.\n\n- `artifact_share_status` success reports can now carry `read_back: true`.\n\n- Separately, inherited task-notification turns now mark their origin with `producer: \"session-task\"`.\n\n**Why**\n\nIn practice, a read-back asks for the state to be read again rather than taken from what was assumed, so file listings and artifact checks may reflect what is actually there right after a change.\n\n- Area: Remote Hosts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}