Divide the request sensibly#
Explain the symptom aloud, then paste the exact error or filename into the reviewed draft. For example: “The attached screenshot shows the error after opening this file. Diagnose it before changing code.” Add the identifier as text rather than repeating it phonetically.
Check the pasted material for private paths, credentials or unrelated content. An attachment can communicate a visible state, but it should not replace an explicit statement of what you want the agent to do.
Avoid false precision#
A transcript that resembles a technical term is not proof that the right object was captured. If the term determines the task, verify it against the original source. Optional refinement should not silently normalize an unfamiliar string into a more common but different name.
The Mac companion supports an editable reply draft and attachments in the reviewed release. This mixed-input workflow is a practical use of those capabilities, not an automatic code-aware identifier guarantee or a promise of integration with every editor.