anomalyco / anomalyco/opencode
[FEATURE]: Desktop: Double-click Review / Context tab to maximize/restore pane (JetBrains-style) - Recreated
@Brendonovich is already working on this.
Since Sep 12, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Issue recreated after 60 day closing
Description
In the OpenCode Desktop app, I’d like to be able to quickly focus a pane by double-clicking its tab header.
Specifically: double-clicking the Review or Context tab header should maximize that pane to fill the Desktop window’s main content area (inside the app), and double-clicking again should restore the previous split sizes — similar to JetBrains IDEs.
This is not about OS-level fullscreen/maximize (title bar behavior). It’s about maximizing/restoring the in-app pane.
Rationale
When reviewing files on the diff, screen real estate is really important. Also, concentrating only on the diff during the review process provides better focus/flow.
Plugins
No response
OpenCode version
Steps to reproduce
- Open OpenCode Desktop
- Ensure the layout shows the
Reviewand/orContexttab/pane (ideally in a split view) - Double-click the
Reviewtab header (orContexttab header)
Current Behavior
- Double-clicking the
Review/Contexttab header does not maximize/restore that pane.
Expected Behavior
- Double-clicking the
Reviewtab header toggles theReviewpane between:- Maximized (fills the main content area within the Desktop window)
- Restored (returns to the previous split sizes)
- Same behavior for the
Contexttab header. - Restoring should return to the exact previous split sizes (like JetBrains).
- This should be an in-app layout toggle (not macOS native fullscreen / not OS title bar maximize).
Screenshot and/or share link
No response
Operating System
Terminal
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.