Repository navigation
While Sentient is attached to your browser, your own downloads go to a temp folder #281
Description
Activity
Hi @itsskofficial, I'd like to work on #281. I'm investigating how Playwright's CDP attachment affects downloads in user-opened tabs and how to preserve the browser's normal download behavior while Sentient is attached. I'll also add regression coverage for user-initiated and Sentient-managed downloads. Could you please assign this issue to me?
It's yours, @Subodh-17, thanks for coming back after the duplicate! Your plan sounds right. Please check it in a real browser: attach Sentient to a throwaway Chrome or Edge started with
--remote-debugging-portand a temp profile, download a file from a tab you opened yourself, and confirm it lands in that browser's normal Downloads folder while Sentient's own tab still saves todownloads/. Mention #281 in the PR.
While Sentient is attached to the user's browser over CDP, a file the user downloads in their own tab doesn't reach their Downloads folder. Playwright's default for an attached browser saves it under its own temp folder (
playwright-artifacts-*) with a random name, and that folder is deleted when Sentient disconnects. Seen in the real test of #202, and it already happens on main.Fix: when attaching, leave the browser's own download behaviour alone for tabs Sentient didn't open, for example by setting
Browser.setDownloadBehaviorback todefaultfor the user's context, or by not enabling Playwright's download handling there.Done when: during an attached session, a download in a tab the user opened lands in their normal Downloads folder, checked in a real browser.