used the /prune command now unable to use the agent "An unexpected error occurred, exiting."

[Daniel Comer]

I tried the /prune command to lower the context and use less tokens however i was getting a constant stream of errors and now only getting "An unexpected error occurred, exiting."

I've tried the following

re-auth on multiple terminals (powershell, windows terminal, vs code terminal) but all give this error when trying to run the rovodev agent. 

i also revoked the API key and created a new one but still will not work.

it seems to be that the session is stuck or an issue starting a new session.

any help will be appreciated

[Mats Lycken]

@Daniel Comer you need to delete your session folder that session, it has become corrupted. This happens to me regularly when doing /prune.

The session folder is stored in C:\Users\<username>\.rovodev\sessions

Delete the folder that has a session_context.json that is 0 bytes.

[dan voronov]

Hello team,

I'd like to provide some feedback regarding the `prune` command.

Firstly, the function of the `prune` command is not entirely clear to me; the description seems vague. If its purpose is to summarize the past conversation/context, it would be highly beneficial if this process happened automatically when the context window is nearing its limit. Alternatively, providing a configuration option for this automation would be helpful.

Frankly, I don't want to have to think about when to /prune or manually manage the context myself. This is precisely the kind of task I would expect an automated tool/agent to handle, especially if the goal is to continue the chat smoothly.

Secondly, I also encountered what appears to be a bug. When I executed the `prune` command, it resulted in the `session_context.json` file being zeroed out (emptied). This broke the session and required me to delete the entire session file to restore functionality, which was inconvenient.

Overall, the tool seems to consume tokens excessively. It would be great to have a more intelligent context manager that proactively handles summarization as the context window fills up, rather than solely relying on or requiring a user command like `prune` to manage this.

My environment is Windows 11, using PowerShell.