What do you include before moving a bug from chat into code edits?

Asks what context makes a coding-agent bug handoff useful instead of vague.

When a bug starts in chat and then moves into actual code edits, I find the handoff matters more than the tool choice. The useful packet seems to be symptom, reproduction path, environment, latest error, failed attempts, and the next safe inspection step. Without that, the coding tool spends time rediscovering context. What fields do you include before asking for edits?