Looping after deleting conversation when it is too long

Again today a history became too long and deleted itself while it was in a process. The process though canceled continued to loop until it had consumed all tokens even though it had been canceled and claimed it had errored out.

How do we get tokens back when the system erroneously uses all of them and the agent encounters a runaway tool-calling loop (specifically view_file on api.py) that causes it to rapidly consume context tokens before crashing, even though it displays as canceled.

Hi @Sean_Duffy,

Could you please provide a few details:

  • The specific version of Antigravity and Operating System you are currently using?
  • Any error messages or traces from the Developer Tools console (Help > Toggle Developer Tools > Console) when the loop occurs?
  • If possible, a screen recording showing the exact steps you take from initiating the task, to deleting the conversation, to the point where the error/loop happens?