[Bug] Conversation becomes unusable after an error (errors repeat on every new prompt)

[krxdow]

Bug: Conversation becomes unusable after an error (errors repeat on every new prompt)

Version

Dive Desktop v0.14.1

Environment

Linux desktop

Additional setup

I am also using Dive with an MCP (Model Context Protocol) server. It is possible that the issue could be related to this integration.

Provider

OpenRouter

Model

GLM-5

Related issue

I previously opened a related issue myself:
#336

The problem reported there appears to be similar. Unfortunately the issue still persists.

I also attempted the following steps to reset the environment:

rm -rf ~/.dive

Then I reinstalled the package and reconfigured everything from scratch.

Despite these steps, the problem still occurs.

Description

After an error occurs during a request, the conversation becomes unusable.
All subsequent prompts return errors even if the new prompt should be valid.

It appears the client keeps an invalid internal state after the first failure.

Errors observed

First error returned by the provider:

Error code: 404 - {'error': {'message': 'No endpoints found that support image input', 'code': 404}}

Later prompts return another error:

Error in query, type: AttributeError, content: 'AIMessage' object has no attribute 'chunk_position'

Context

I am using GLM-5 through OpenRouter.

Initially I attached an image to a prompt. I later understood that the model may not support image inputs, so the 404 error is expected.

However, after this first error occurred, the conversation appears to be stuck.

Even when:

• removing the image from the prompt
• sending a new text-only prompt
• pasting or importing a completely new prompt

The errors continue.

Steps to reproduce

1. Start a conversation
2. Use GLM-5 via OpenRouter
3. Send a prompt that results in an error (for example attaching an unsupported image)
4. Send a new prompt with only text
5. Errors continue to appear

Expected behavior

A failed request should not break the conversation state.

After an error, the next prompt should send a fresh request and the chat should continue normally.

Actual behavior

The error state appears to persist across prompts and the conversation becomes unusable.

[ckaznable]

@krxdow Would a new session still result in a failed conversation?