Remix.run Logo
▲ agline_in 6 hours ago

The shared named profile is handy, but how do you deal with one agent's actions spilling over to the others? For example, one agent logs out, switches accounts, or trips a site's rate limit, and every other agent on that profile inherits it. Is there a way to give an agent a forked or read-only copy of the profile's cookies?

▲tomaskafka 3 hours ago | parent | next [-]

This - for some scenarios I want the cookies shared (multiple agents watching eg fb marketplace), for others I want to have their own sandbox. And the GUI could indicate this eg. by putting tabs that share profile into blocks.

▲pklym 2 hours ago | parent | prev [-]

Not yet. For now, state-save in one workspace and state-load in a fresh one gives an in-memory copy, so a logout stays there. Fork flag can be done.