Copy and Add FIles or Folders

Ideas Feature Requests
,
1

Composer / Agent mode — copy and attachments

  1. Copy / Copyblock workflow
  • Copying assistant output is awkward: the “⋯” menu is not practical (extra clicks) compared to other tools (e.g. Codex) that expose a visible one-click copy on the message.
  • When a background shell/terminal block appears (e.g. “Stopped … in background”), the stream splits into segments. Often only the segment after the tool/widget gets the copy affordance, while the main assistant text above cannot be copied as one block. This breaks workflows that rely on copying full agent output (e.g. COPYBLOCK handoffs between agents).
  • Request: visible one-click “Copy message” on each assistant text block, and/or “Copy entire turn” (all assistant-visible text in that turn, independent of tool widgets).
  1. Attaching files or folders (@ / add context)
  • Adding files or folders does not behave reliably: the product should resolve the exact path the user means, but instead the assistant often has to search the repo by name to find the right path.
  • Request: more reliable path resolution for attached files/folders so context matches the user’s intent without guesswork or repo-wide name search.
5

For adding files and folders as context, you can @-mention them directly in chat to pull them into the conversation. More on how context works: Adding Context. If the path picker isn’t reliably finding what you mean, that’s something we’re actively working on.

On the copy side — agreed that grabbing assistant output should be easier, especially when tool calls split things into multiple segments. Both are on our radar.