Give better context
Attach files, screenshots, and camera context
Good context is selected, visible, and removable. FireCursor turns workspace files and Android media into attachment chips so you can verify what will be sent before the next message.
Quick answer
The shortest useful version.
Attach only the artifact that proves the issue, review its chip and project context, explain what the agent should inspect, remove accidental or sensitive items, then send.
Step by step
Do this with confidence.
- 01
Choose the evidence type
Use @ for a workspace file, the attachment action for a screenshot or gallery image, or the camera for a physical-device state.
- 02
Inspect the attachment chip
Confirm the file name or preview and remove anything unrelated before sending.
- 03
Add an observation
Tell the agent what is wrong and what a correct result should look like. An image without a question is ambiguous.
- 04
Protect sensitive content
Crop or avoid secrets, personal notifications, customer data, and pairing details. Use the minimum evidence required.
High-value uses
- A layout defect visible only on a device
- An Android system installer or permission screen
- A terminal or test error captured away from the desk
- A design reference paired with the exact component file
- A workspace file attached with @ for implementation context
Why reviewable chips matter
Mobile share flows make accidental context easy. A visible, removable attachment state creates a last checkpoint before information enters the agent conversation.
After sending, treat the attachment as part of the session record and apply the provider’s data boundary to it.