Try to pack as much clear work into your prompt as you can so you don't go back and forth.

Do hacks like “read prompt.md, and follow its instructions. When you’re done, read it again and follow its instructions.” And then you have some background process appending to the file to keep it warm and you just keep writing there?

▲

cylemons 10 hours ago | parent | next [-]

There is a limit on how much copilot can do in one request, pretty generous but after some time vscode will say "this request is taking very long, do you want to continue" and that would count as a seperate request

	▲	ValentineC 6 hours ago \| parent [-]
		> but after some time vscode will say "this request is taking very long, do you want to continue" and that would count as a seperate request I don't think that's true. In VS Code, that's also configurable via the chat.agent.maxRequests setting. There was absurd latency in the Copilot Opus 4.6 model on 1st and 2nd April which led to lots of my requests timing out with nothing to show though.

▲

19 hours ago | parent | prev | next [-]

[deleted]

▲

esafak 18 hours ago | parent | prev [-]

You could do that. I was just trying to say that if you make your original prompt complete enough, and you have well-defined success criteria, you can tell it to keep going until they are met.

	▲	Cerium 17 hours ago \| parent [-]
		Agreed - my experience mirrors this. > "Fix the following compile errors" -> one shot try and stops. > "Fix the following compile errors. When done, test your work and continue iterating until build passes without error" -> same cost but it gets the job done.