Title: Codex CLI conversation history cannot be scrolled in the terminal panel
Describe the bug
When running Codex CLI inside a Codirigent project, the terminal panel does not allow scrolling through the full conversation history.
The conversation content appears to exist, but only the text currently visible within the terminal viewport can be accessed. The scrollbar also behaves as though the visible portion is the entire terminal output.
In the same Codirigent environment, Claude CLI conversation sessions can be scrolled up and down normally.
To Reproduce
Steps to reproduce the behavior:
- Open a project in Codirigent.
- Launch Codex CLI in the terminal panel.
- Start a conversation and generate enough output to exceed the terminal viewport height.
- Attempt to scroll upward using the mouse wheel, touchpad, scrollbar, or keyboard.
- Observe that the terminal cannot scroll beyond the currently displayed screen.
- Launch Claude CLI in the same environment and generate enough output to exceed the viewport.
- Observe that the Claude CLI session can be scrolled normally.
Expected behavior
The Codex CLI terminal session should allow users to scroll through the entire conversation history, just as Claude CLI sessions do.
The scrollbar should represent the complete amount of terminal output rather than only the currently visible viewport.
Screenshots
If applicable, screenshots or a screen recording can be provided showing:
- The Codex CLI terminal with inaccessible conversation history
- The scrollbar indicating that no additional output exists
- Claude CLI scrolling normally in the same Codirigent environment
Desktop (please complete the following information):
- OS: Windows 11
- Codirigent version: 0.1.6
- Codex CLI version: [Please enter version]
- Claude CLI version: [Please enter version]
- Shell: PowerShell
- Terminal environment: Codirigent integrated terminal
Additional context
This issue appears to be specific to Codex CLI sessions within Codirigent because scrolling works correctly when Claude CLI is executed in the same project and terminal environment.
The Codex CLI conversation history does not appear to be deleted. New content continues to be generated, but previous output becomes inaccessible once it moves outside the visible terminal viewport.
The issue occurs regardless of whether scrolling is attempted with the mouse wheel, touchpad, scrollbar, or keyboard.
The following troubleshooting steps were attempted, but the issue persisted:
- Moving the terminal tab to a different position
- Changing the tab and panel layout
- Restarting Codirigent
- Running a repair installation of Codirigent
- Restarting Windows
Title: Codex CLI conversation history cannot be scrolled in the terminal panel
Describe the bug
When running Codex CLI inside a Codirigent project, the terminal panel does not allow scrolling through the full conversation history.
The conversation content appears to exist, but only the text currently visible within the terminal viewport can be accessed. The scrollbar also behaves as though the visible portion is the entire terminal output.
In the same Codirigent environment, Claude CLI conversation sessions can be scrolled up and down normally.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Codex CLI terminal session should allow users to scroll through the entire conversation history, just as Claude CLI sessions do.
The scrollbar should represent the complete amount of terminal output rather than only the currently visible viewport.
Screenshots
If applicable, screenshots or a screen recording can be provided showing:
Desktop (please complete the following information):
Additional context
This issue appears to be specific to Codex CLI sessions within Codirigent because scrolling works correctly when Claude CLI is executed in the same project and terminal environment.
The Codex CLI conversation history does not appear to be deleted. New content continues to be generated, but previous output becomes inaccessible once it moves outside the visible terminal viewport.
The issue occurs regardless of whether scrolling is attempted with the mouse wheel, touchpad, scrollbar, or keyboard.
The following troubleshooting steps were attempted, but the issue persisted: