"Continuing autonomously (3 premium requests)" after model completion

[joshlacal]

Describe the bug

Hi! I get that our 'free lunch' is over and Copilot requests now "Continu[e] autonomously (3 premium requests)" when in 'autopilot' but I've experienced this issue I believe to be a bug multiple times:

I missed a screenshot of the first time, but the model will finish, and then it will charge another set of premium requests, sometimes just seeming like a forced call re-explaining the changes or updating the plan without explaining changes. Is there any way we could either not be charged for a subsequent request after the model decides it's 'done', or prevent it from happening?

Affected version

v0.0.410

Steps to reproduce the behavior

1. put in autopilot mode
2. run the model on a long running task

Expected behavior

if the model is 'done' do not encourage it to continue

Additional context

No response

[joshlacal]

[minhdqdev]

Yeah, I'm seeing that too. A lot of the recent bug reports are related to autopilot mode. The temporary workaround is to stop using autopilot until the maintainers work on it.

[mgelei]

Same here.

● Continuing autonomously (3 premium requests)
● All 12 todos are done, all 357 tests pass, and the commit is made. The implementation is complete.

NB, both the test running and the commit happened before the +3 request charge.

If my prompt costs 6 requests, not 3, that's fine, but then please put 6 on a the pricetag as well, instead of pulling shenanigans like this.

[danielpuglisi]

Same here. $0.12 just for it to say "I'm done" lol

[mgelei]

lol

again, my problem is not that a task costs 0.24 instead of 0.12, that's fair, but then tell me "this tasks costs double because it was a lot of work", instead of questionable bugs

I'm a bit skeptical about this bug tbh, because I've never seen this additional request message under normal circumstances, only at the end of a conversation round

[anirudhsengar]

I'm facing the same issue, not sure how to stop it from doing this... :(

[luigi370]

Having the same issue.