Skip to content

[bug] Terminal output sometimes fails to render Cloud Code responses until interrupt/restart #666

Closed

Description

@geooff

Describe the bug

Sometimes Cloud Code completes and returns a response, but the terminal UI does not update to display it. The response appears to have been produced correctly (i.e., the underlying process/state has it), but it doesn’t render/flush into the terminal viewport.

The only reliable workaround is to Ctrl+C out of the Cloud Code session and then restart using Continue, at which point output resumes.

This is severe because it looks like the command is hanging or failed, even though it actually returned.

Steps to reproduce

  1. Open Superset’s integrated terminal
  2. Start Cloud Code
  3. Run any Cloud Code prompt/command that should return output
  4. Occasionally, Cloud Code will return internally, but the terminal output does not update

Repro frequency: intermittent (e.g., “sometimes” / “every X runs”) — I can provide more detail if needed.

Expected behavior

When Cloud Code produces output (tokens / final response), the terminal should immediately render it in the terminal window.

Actual behavior

Cloud Code returns a valid response, but the terminal UI does not display it (appears stalled). Output resumes only after:

  • Pressing Ctrl+C to interrupt Cloud Code, then
  • Restarting Cloud Code using Continue

Workaround

  • Ctrl+C to interrupt Cloud Code
  • Restart with Continue
  • Output begins updating again

Environment

  • Superset version: 0.0.49
  • Terminal context: Superset integrated terminal
  • Cloud Code: v2.0.76
  • Repro frequency: intermittent

Activity

  1. Kitenite commented on Jan 8, 2026

    @Kitenite
    Member

    @geooff i noticed this too across opencode and claude code today. I'm suspecting it's an issue with Anthropic. I had to interrupt and type continue. Don't think it's related to us since you're still able to interact with the terminal regularly.

  2. geooff commented on Jan 8, 2026

    @geooff
    Author

    I can confirm this is happening in v0.0.48 aswell. @Kitenite I agree with your thoughts.

  3. geooff commented on Jan 8, 2026

    @geooff
    Author

    Just some added context. This only seems to happen when switching between tabs. If I stay on the same chat the issue doesn't occur.

  4. Kitenite commented on Jan 8, 2026

    @Kitenite
    Member

    @geooff I think this is an issue on our side when terminal drops update when not visible. I will be adding a fix for this.

  5. Kitenite commented on Jan 9, 2026

    @Kitenite
    Member

    Releasing the fix #685

  6. Kitenite commented on Jan 9, 2026

    @Kitenite
    Member

    Closing as I think this is solved. Please reopen if you still have issues in the latest version @geooff . Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions