Skip to content

feat: Embedded browser? #37

Closed
Closed

Description

@juliusmarminge

Cursor's built-in browser is quite good. would be nice having a browser per thread? might get heavy though 😆

Activity

  1. nckre commented on Mar 7, 2026

    @nckre

    @juliusmarminge would recommend checking out portless from @ctate as a light alternative.

    Automatically spin up a portless server with the url of the git worktree, so {worktree}.{project}:1355 and you could just add an action to open this in your default browser quickly from t3code

    This has worked well for me in local development

  2. acoiro commented on Mar 12, 2026

    @acoiro

    I built this for myself, I’m sharing it via PR (#963) in case any part of it is useful as a starting point or source of ideas. The PR also includes a reconstruction plan and screenshots.

    The current browser runtime keeps only the 3 most recently used web views alive and evicts the rest. That tradeoff was mainly to keep memory usage bounded, and it could be made smarter.

    in-app-browser.mp4
  3. TimoKruth commented on Mar 27, 2026

    @TimoKruth

    This looks a lot like cmux in the video from @acoiro. To be honest I like it if it stays lightweight.

    If t3code is enabled to be integrated into cmux as a first citizen app and cmux integrates the project->chat/task based side bar part it can be combined into each other and it would "solve" the browser question for everybody who wants it. And it includes a little more...
    I built a repo that forks both projects and adjusts them as little as I could to integrate them into each other. for t3code this means primarily changes on how a chat can be started without the sidebar being active.

    Project link: https://github.com/TimoKruth/cmux-t3code

    Image
  4. akarabach commented on Apr 9, 2026

    @akarabach
    Contributor

    @t3dotgg @juliusmarminge @maria-rcks design mode in Cursor 3 is amazing

    Image
  5. juliusmarminge commented on Apr 9, 2026

    @juliusmarminge
    MemberAuthor

    Yes. Will put the browser thing on the roadmap in the short-ish future.

    Just need to figure out auth cause thats where most of the current solutions breaks down that i can't sign in to any service which makes them pretty unusable for any real work

  6. akarabach commented on Apr 14, 2026

    @akarabach
    Contributor

    @juliusmarminge totally get the auth concern - that's the tricky part for sure.

    On the competitive side though, Cursor keeps shipping hard on this front. Their built-in browser is getting better and better, and they're even planning to add an iOS emulator directly into Cursor. We're falling behind here and I think this needs to move up in priority.

    I'd love to help push this forward. Two options from my side:

    1. You set the direction - share your vision for how the browser should work (architecture, auth approach, UX) and I'll pick it up and start implementing based on that.
    2. I prepare a plan first - I can put together an implementation plan / proposal and share it with you for review before writing any code.

    Whatever works best for you.

    Also, one thing I've been thinking about beyond just the browser - a custom Vite plugin that would help the design tool understand which component is currently highlighted, map DOM elements back to source components, etc. Kind of like what Cursor's design mode does. But obviously the browser itself is the prerequisite and needs to land first before any of that makes sense.

  7. juliusmarminge commented on Apr 14, 2026

    @juliusmarminge
    MemberAuthor

    yea so for design mode we could use some of Aidan's work in react-grab or whatever right? tanstack devtools also injects source paths to components.

    for the browser view, I wanna improve the layout system first (#2011) so that you're not limited to where you place the browser. if you wanna work on the actual brwoser implementation in the meantime be my guest :)

  8. akarabach commented on Apr 15, 2026

    @akarabach
    Contributor

    @juliusmarminge PR #963 from @acoiro was closed without a code review. Since the browser implementation on the roadmap, could you take a quick look at that PR and share what you'd want done differently? Would help us avoid going down the wrong path.

  9. added a commit that references this issue on Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementRequested improvement or new capability.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions