You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Uses a different browser than Chrome/Chromium (for example, the Dia browser), and
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
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:
Uses a different browser than Chrome/Chromium (for example, the Dia browser), and
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!
Beta Was this translation helpful? Give feedback.
All reactions