Description
I'm hitting a loop where a 400 Bad Request from the Anthropic API completely bricks a Crush session.
The Bug: When using the playwriter MCP, it sometimes returns image data with non-ASCII characters in the base64 string. Anthropic rejects this immediately.
The problem is that Crush persists this "bad" message in the context. Since it stays in the history, every single message I send after that (even just saying "continue") triggers the same 400 error. I have to kill the session and start over to fix it.
Error Details
{"type":"error","error":{"type":"invalid_request_error","message":"messages.178.content.0.tool_result.content.0.image.source.base64: string argument should contain only ASCII characters"}}
It would be great if we could have a way to manage the session history—maybe a /undo or /delete command to drop the last message so we can recover from API errors like this without losing the whole session.
Version
v0.30.3
Environment
tmux
Description
I'm hitting a loop where a 400 Bad Request from the Anthropic API completely bricks a Crush session.
The Bug: When using the playwriter MCP, it sometimes returns image data with non-ASCII characters in the base64 string. Anthropic rejects this immediately.
The problem is that Crush persists this "bad" message in the context. Since it stays in the history, every single message I send after that (even just saying "continue") triggers the same 400 error. I have to kill the session and start over to fix it.
Error Details
It would be great if we could have a way to manage the session history—maybe a /undo or /delete command to drop the last message so we can recover from API errors like this without losing the whole session.
Version
v0.30.3
Environment
tmux