Dia Browser, browser profile

### Which destkop app does this feature request relate to?

- [ ] Select a project 👇
- [x] Agent-TARS (cli, server, agent, tool etc.)
- [ ] UI-TARS Desktop

### What problem does this feature solve?

Hi team,

First of all, thank you for the incredible work on Agent TARS / UI‑TARS.

I have a question about browser usage and profiles in the desktop app:

Is there a way to configure UI‑TARS (or the browser operator) so that it:

1. Uses a different browser than Chrome/Chromium (for example, the Dia browser), and

2. Reuses the already logged‑in browser profile/session from that browser, instead of starting a fresh session?

My goal is to let the agent operate on sites like Twitter/X using my existing logged‑in browser profile, so the agent doesn’t have to perform the login flow itself each time. Ideally, the agent would attach to or reuse the current profile (cookies, sessions, etc.) of the system browser (or a specified browser) rather than launching an isolated profile.

If this is not currently supported, is there any recommended workaround (e.g., pointing the browser operator at a specific profile directory or session) or is this something that’s on the roadmap?

Thanks in advance for your guidance!

### What does the proposed features look like?

N\A

Start by examining the desktop app's browser operator and its current browser/profile-session configuration. Determine whether the requested Dia browser support and reuse of an existing logged-in profile can be specified from the issue alone; done would require a documented, working way to select that browser and reuse its session.

Written by the indexing model from the issue text.