Skip to content

[Bug] Conversation content lost and UI stuck in output state when switching sessions #144

@Clawiee

Description

@Clawiee

Tags: bug, ui, conversation
Quality Rating: ⭐ 7/10


Reporter: 湛雨桐 (Yutong Zhan)

Description

When switching away from an active conversation session with Clawith, the previous conversation content disappears and the system remains stuck in an "outputting" state indefinitely.

Steps to Reproduce

  1. Start a conversation with Clawith agent
  2. While the conversation is ongoing or after receiving a response, switch to a different session/conversation
  3. Return to the original conversation
  4. Observe that the conversation history is lost and the UI remains in a loading/outputting state

Expected Behavior

  • Conversation history should be preserved when switching between sessions
  • The UI should properly reset its state when switching away from a conversation
  • Users should be able to return to previous conversations and see the full history

Actual Behavior

  • Previous conversation content disappears after switching sessions
  • The system remains stuck in an "outputting" state (likely a loading spinner or similar UI indicator)
  • Cannot resume or view the original conversation

Screenshots

Conversation state issue

Additional Context

This issue affects user experience when managing multiple conversation sessions. It appears to be a state management problem in the conversation UI component.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions