# Saved cloud browsers with a power button and lasting logins

> Your saved browser is now a cloud computer you switch on. Sign-ins are refreshed every three days, and agents try single sign-on before asking you.

Sep 25, 2026. Topics: Agents. https://www.generalinput.com/changelog/2026-09-25-saved-browsers-power-button

Signing an agent into a website used to run through a guided flow where an agent checked and steered each sign-in. It was slow and brittle, so we replaced it with something plainer. On the Browser page (in beta), your saved browser is a computer with a power button: switch it on, browse and sign in to anything the way you would on your own machine, and switch it off. Agents, workflows, the CLI, and the MCP server reuse whatever you signed in to.

### How it works

- **Saves as you go.** The browser saves its state on each page load and every five seconds, so a dashboard refresh reconnects to the same session. It powers off after two minutes with nobody watching, or 15 minutes of inactivity.
- **Real logins only.** A site appears in your saved logins only when a sign-in cookie or token actually appears, not just because you visited.
- **Sign-ins kept fresh.** Every three days a background visit reopens each active login's site so it reissues its cookies before common one- and two-week timeouts.
- **Single sign-on first.** A saved login remembers its provider, like "signed in with github.com." At a sign-in wall, an agent clicks that provider's button once; anything beyond that waits for you.
- **Handing a sign-in back.** When an agent hits a wall it can't pass, it sends you a card that opens your browser on that exact page.