The PR panel is useless and actively in the way — give us a way to disable it or fix the base branch logic

Resolved 💬 3 comments Opened Apr 17, 2026 by ybaidiuk Closed Apr 20, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

This PR creation panel that sits above the input box is genuinely annoying and, frankly, half-broken by design. A few things that need to be addressed:

  1. Why the hell is it hardcoded to compare against master?

Not everyone merges feature branches straight into master. Epic branches exist. Stacked PRs exist. Release branches exist. When I'm on DEV-12323_chart and my actual target is an epic branch, the panel proudly shows me +5439 -166 against master — a completely meaningless diff that has nothing to do with the PR I'm about to open. It's misinformation dressed up as a helpful UI.

  1. Why can't I change the base branch from the UI?

There's no selector. No dropdown. No way to tell the panel "hey, my target is epic/DEV-12323, not master." For a tool that lives inside a dev workflow, this is a baffling omission.

  1. Why can't I just turn this thing off?

No setting in settings.json. No env var. No CLI flag. No /config option. If I don't want the panel, my only option is to ignore it — which defeats the point of having configurable tooling in the first place.

<img width="1228" height="263" alt="Image" src="https://github.com/user-attachments/assets/197eae2f-5cfc-4ffa-8ae0-a7c7da5c2adc" />

Proposed Solution

What I need:

A setting to hide the PR panel entirely (e.g. "ui.prPanel": false)
A way to pick the base branch from the UI, not assume master/main
Ideally both

Until then, this panel is noise. Please either make it useful or make it optional.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗