Terminal view becomes unscrollable after switching project or switching to another terminal
What is happening
Location: Project > Terminal > Cline / 9router
Description:
When using 1DevTool, the terminal scroll works normally right after creating and opening a Cline terminal. I can scroll up and down through the terminal output as expected.
However, after switching to another project or switching to another terminal such as 9router, the terminal view stops responding to scroll actions. The content appears to be stuck in its current position and cannot be scrolled anymore, even though the terminal has enough output to scroll.
Actual:
- Cline terminal scroll works normally at first.
- After switching project or switching to another terminal, scrolling no longer works.
- The terminal output becomes fixed/stuck and the user cannot move through the previous or later output.
Expected:
- Terminal scrolling should continue to work consistently after switching projects or switching between terminals.
- Each terminal tab/session should preserve and restore its scroll behavior correctly.
- The user should be able to scroll through terminal output regardless of which project or terminal was previously selected.
Impact:
This makes it difficult to inspect previous terminal output, debug command results, or continue working with long-running AI agent sessions. In terminals with large outputs, the user may be unable to review important earlier logs or generated content after switching context.
Expected result
See the description.
Actual result
Location: Project > Terminal > Cline / 9router Description: When using 1DevTool, the terminal scroll works normally right after creating and opening a Cline terminal. I can scroll up and down through the terminal output as expected. However, after switching to another project or switching to another terminal such as 9router, the terminal view stops responding to scroll actions. The content appears to be stuck in its current position and cannot be scrolled anymore, even though the terminal has enough output to scroll. Actual: - Cline terminal scroll works normally at first. - After switching project or switching to another terminal, scrolling no longer works. - The terminal output becomes fixed/stuck and the user cannot move through the previous or later output. Expected: - Terminal scrolling should continue to work consistently after switching projects or switching between terminals. - Each terminal tab/session should preserve and restore its scroll behavior correctly. - The user should be able to scroll through terminal output regardless of which project or terminal was previously selected. Impact: This makes it difficult to inspect previous terminal output, debug command results, or continue working with long-running AI agent sessions. In terminals with large outputs, the user may be unable to review important earlier logs or generated content after switching context.
How to reproduce
Imported from UserJot — original report did not use structured steps.
Reproducibility: Unknown · Impact: Minor issue
Environment
- VERSION
- unknown
- OS
- —
- ARCH
- —
- CHANNEL
- stable
Resolution progress
PENDING
—
REVIEWING
—
IN PROGRESS
—
COMPLETED
—
Discussion0
Newest first- No comments yet. Add context or ask a question below.
Sign in to comment, vote and follow this request.
Sign in to reply