continuedev / continuedev/continue

Full-Screen Toggle Mode Focus Issues

Open
#3,550 5 comments 1 reaction 1 assignee View on GitHub

@RomneyDa is already working on this.

Since Dec 27, 2024.

area:chat ide:vscode kind:bug needs-triage os:windows
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
Relevant environment info
**OS:** Windows_NT x64 10.0.19045  
**Continue version:**  0.8.66
**IDE version:** Visual Studio Code   1.96.2 (user setup)  
**Model:** Ollama Qwen 2.5 local 32b coder, Deepseeker v3 (OpenRouter)
Description
Description:

When using Continue.dev in full-screen mode and attempting to handle it as a side menu, an issue arises where follow-up questions stop processing upon losing focus. Additionally, every time focus is shifted away from the extension, a new chat window is automatically opened (actually it jumps to beginning, but had case of new chat window yesterday, today jumping seen, see clip below in my comment). This behavior persists across different models, including Ollama Qwen 2.5 local 32b coder and Deepseeker v3 from OpenRouter, indicating that this might be an extension-specific issue rather than a model-related one.

The issue seems to stem from how focus and window management are handled within the extension when operating in a new window.

image

To reproduce
Steps to reproduce the problem:
  1. Open Continue.dev in full-screen mode in VS Code.
  2. Use the side menu-like functionality while interacting with the extension.
  3. Ask a follow-up question.
  4. Switch focus to the main VS Code window.
  5. Observe the behavior when returning to Continue.dev.

Expected Behavior:

  • Follow-up questions continue processing even after losing focus.
  • No new chat window is opened when focus is lost.

Actual Behavior:

  • The follow-up question stops processing as soon as the focus shifts away from the Continue.dev window.
  • A new chat window opens automatically when focus is lost.
Log output

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.