Remote file reads gain offsets, upload screening and byte-range reply fields

What

Apps 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.

The request now accepts:

• offset, to start reading partway into the file.
• for_upload, which screens the file for credentials (passwords, keys or tokens).
• liveReply.

The reply, which carries the file contents, now adds these fields, all marked @internal:

• offset, read_bytes and total_bytes, saying where the read started, how much was read and how large the file is.
• etag, an opaque string that names the file as it was opened for this read.
• upload_screened and requested_path.

The 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.

Why

Remote apps can read large files in pieces, tell whether a file changed between pieces, and have files checked for credentials before uploading them.