{"version":"2.1.323","anchor":"read-file-gains-offset-for-upload-livereply","canonical_anchor":"read-file-gains-offset-for-upload-livereply","heading":"Remote file reads gain offsets, upload screening and byte-range reply fields","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/read-file-gains-offset-for-upload-livereply","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote file reads gain offsets, upload screening and byte-range reply fields\n\nThe remote read_file request accepts offset, for_upload and liveReply, and its reply adds byte counts, an etag and screening fields\n\n**What**\n\nApps that control Claude Code remotely can ask it to read a file with a `read_file` request. Both the request and the reply gained fields.\n\nThe request now accepts:\n\n- `offset`, to start reading partway into the file.\n\n- `for_upload`, which screens the file for credentials (passwords, keys or tokens).\n\n- `liveReply`.\n\nThe reply, which carries the file contents, now adds these fields, all marked @internal:\n\n- `offset`, `read_bytes` and `total_bytes`, saying where the read started, how much was read and how large the file is.\n\n- `etag`, an opaque string that names the file as it was opened for this read.\n\n- `upload_screened` and `requested_path`.\n\nThe description of `lossy` now also covers a read that was cut at its start because `offset` was set. Before, the reply had only `contents`, `absPath`, `truncated`, `encoding`, `lossy` and `anchor`.\n\n**Why**\n\nRemote apps can read large files in pieces, tell whether a file changed between pieces, and have files checked for credentials before uploading them.\n\n- Area: Remote Control\n- Names: `read_file`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}