Allow opening the browser panel before/at the start of a new session

Status Open
Maintainer reply None cached
Activity 1 comment · opened Jul 18, 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

When starting a new session in Claude Code, I often need to work on a specific webpage (debugging a live site, reviewing a page, testing something in the browser). The browser panel button isn't available until the session has already started, so I have to begin the chat first, ask Claude to wait, and only then open the browser and load the page I actually want to work on. This adds unnecessary friction and back-and-forth to what should be a starting condition of the session.

Proposed Solution

I'd like the browser panel toggle/button to be available right from the new session screen, before the first message is sent. That way I could open the browser panel, load the target page, and only then start the conversation — with the right context already in place from the first prompt, instead of having to ask Claude to wait.

Alternative Solutions

Currently I work around this by starting the chat, explicitly telling Claude to wait, and then opening the browser panel to load the page once it becomes available. It works, but it's an extra manual step every time and delays getting to the actual task.

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

Example scenario:

  1. I need to debug an issue on a live webpage.
  2. I open a new Claude Code session and want the browser panel open with that page loaded before I say anything.
  3. With this feature, I could load the page first, then start the conversation with full context already visible.
  4. This would save time because I wouldn't need to start the chat, ask Claude to wait, and only then load the page.

Additional Context

This would be especially useful for workflows tied to a specific webpage from the very beginning of the session (debugging, reviewing a live site, etc.), where having the browser context present from the first prompt avoids unnecessary round-trips.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗