Desktop/Cowork document review: batch multiple comments and edits on a rendered file into one submission
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Reviewing a document (typically .md) that Claude wrote in the desktop app or Cowork: the rendered view's feedback affordances send one chat message per change. Each small note — reword this sentence, fix that figure, cut this paragraph — becomes its own full round trip. Reviewing a 10-point document means 10 sequential chat exchanges, each waiting on the previous one. That is the slowest possible edit loop for prose, and it makes the app noticeably weaker than ordinary document tools for the review half of writing work. If Cowork is aimed at professional document work, the review loop matters as much as the drafting loop.
Proposed Solution
Word/Google Docs-style review mode in the file pane: let me attach multiple inline comments and edits to selections across the document, queueing them locally as I read, then submit the whole set as ONE request. Claude applies the batch in a single pass and returns one updated document. The queued comments should be visible and editable before submission (a review sidebar or pin list), and submission should be explicit — nothing sends while I'm still reading.
This complements #83476 (direct in-place editing of .md, which covers one-word fixes I'd rather just type myself) and is the reverse direction of #31888 (which batches Claude's proposed diffs for user approval; this batches the user's requested changes for Claude).
Alternative Solutions
Current workarounds: (a) sending feedback one button-click at a time and waiting out each round trip; (b) writing all my notes as a numbered list in a single chat message, which loses the anchor to the exact text each note refers to and makes Claude re-locate every target; (c) opening the file in an external editor, which defeats the point of doing the work in the app. Word and Google Docs solve this with anchored comments plus batched resolution; Cursor/VS Code solve the code equivalent with review-then-apply flows.
Priority
Nice to have
Feature Category
Other
Use Case Example
_No response_
Additional Context
_No response_