| Files | Last commit | Last update |
|---|---|---|
Add named browser profiles for agents (#2972) * Add named browser profiles for agents An agent can use the shared browser session, a session of its own, or a named profile. Many agents can use the same named profile, so they share the sign-ins of that profile. The profiles are on the host computer. - Migration 45 adds the browser_profiles table. It does not change rows. - A tab opens and restores in the partition of its profile. A tab of a deleted profile does not open in a different session. - Server settings have a "Browser profiles" section: create, rename, color, clear data, and delete. Delete moves the agents to Shared. - Tabs in a named profile show the profile name and color. - The new optional Team API capability browser-profiles-v1 lets an owner or admin manage profiles on a joined server, from desktop and from the web client. Members see the tab labels only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Say where browser profile data stays for a remote server The subtitle said "this computer". On a joined server the data stays on the host, so the text now says "the computer that runs OpenBot". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fix browser profile review findings - Do one profile change at a time, so an agent cannot move into a profile while a delete moves its agents out. - Send only expected refusals (name in use, missing profile, limit) to a joined server as 409. Other failures stay private. - Use catalog text when a tab still uses a session that Clear empties. - Read one profile by its id, and read the agents once for each list. - Keep one profile store per server id on desktop and web, so a new server summary does not reset the list. The server settings section lists again when it changes to another server, and names the agents of that server in the delete question. - Do not report a change as failed when only the list after it fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Remove an unused browser session helper and a forwarding decoder Nothing calls agentOwnBrowserSessionEnabled now. Its doc named it as the rule for ownBrowserSession, but a named profile applies first. decodeBrowserProfileSummary only called decodeSummary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Do not export BrowserProfileFailure Only browser-profile-service.ts uses it. Knip failed the Check job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Take the browser session choice only through the profile service No client sends ownBrowserSession in updateAgent now. The IPC parser still took it, and that path did not use the serialized profile change. The field moves from UpdateAgentInput to the internal update types. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 17 days ago | |
Add named browser profiles for agents (#2972) * Add named browser profiles for agents An agent can use the shared browser session, a session of its own, or a named profile. Many agents can use the same named profile, so they share the sign-ins of that profile. The profiles are on the host computer. - Migration 45 adds the browser_profiles table. It does not change rows. - A tab opens and restores in the partition of its profile. A tab of a deleted profile does not open in a different session. - Server settings have a "Browser profiles" section: create, rename, color, clear data, and delete. Delete moves the agents to Shared. - Tabs in a named profile show the profile name and color. - The new optional Team API capability browser-profiles-v1 lets an owner or admin manage profiles on a joined server, from desktop and from the web client. Members see the tab labels only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Say where browser profile data stays for a remote server The subtitle said "this computer". On a joined server the data stays on the host, so the text now says "the computer that runs OpenBot". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fix browser profile review findings - Do one profile change at a time, so an agent cannot move into a profile while a delete moves its agents out. - Send only expected refusals (name in use, missing profile, limit) to a joined server as 409. Other failures stay private. - Use catalog text when a tab still uses a session that Clear empties. - Read one profile by its id, and read the agents once for each list. - Keep one profile store per server id on desktop and web, so a new server summary does not reset the list. The server settings section lists again when it changes to another server, and names the agents of that server in the delete question. - Do not report a change as failed when only the list after it fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Remove an unused browser session helper and a forwarding decoder Nothing calls agentOwnBrowserSessionEnabled now. Its doc named it as the rule for ownBrowserSession, but a named profile applies first. decodeBrowserProfileSummary only called decodeSummary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Do not export BrowserProfileFailure Only browser-profile-service.ts uses it. Knip failed the Check job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Take the browser session choice only through the profile service No client sends ownBrowserSession in updateAgent now. The IPC parser still took it, and that path did not use the serialized profile change. The field moves from UpdateAgentInput to the internal update types. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 17 days ago | |
Give each browser profile its own proxy (#5145) * Give each browser profile its own proxy A named browser profile can use a saved proxy: socks5, http or https, with an optional sign-in. The password is encrypted and shows only as a mask. A SOCKS5 proxy with a sign-in goes through a relay on 127.0.0.1. When the proxy cannot be set, the tab does not open, so pages never go out without the proxy. A badge shows when the proxy does not answer or refuses the sign-in, and the page error names the proxy. A member can also share the connection of their own computer as the proxy of a profile on a joined server. The computer opens only public internet addresses. Owners and admins manage proxies from the desktop app and the web (browser-proxies-v1, browser-egress-v1). Migration 56 adds the browser_proxies and browser_profile_proxies tables. Closes #3443 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fix proxy relay races and egress edge cases from review - Apply one profile proxy at a time, so two tabs that open together do not open two relays and leave one open. - Stop the relay of the old proxy when a proxy change closes the tabs. - Keep a saved password only when the address still has a user name. - Connect to a SOCKS5 proxy at an IPv6 address without the brackets. - Refuse a site name that browser-egress-v1 cannot carry before it goes to the computer, which closes the channel on a bad frame. - Open a new egress channel when the last one is closing. - Stop the computer proxy muxes before the team WebRTC bridge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Remove unused proxy relay and port exports Knip found five exports that only their own file uses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Refuse a proxy address with a password and no user name The database refused such a proxy, so the save failed with a generic error. The parser now refuses the address, and the dialog shows that the address is not valid. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 5 days ago | |
Give each browser profile its own proxy (#5145) * Give each browser profile its own proxy A named browser profile can use a saved proxy: socks5, http or https, with an optional sign-in. The password is encrypted and shows only as a mask. A SOCKS5 proxy with a sign-in goes through a relay on 127.0.0.1. When the proxy cannot be set, the tab does not open, so pages never go out without the proxy. A badge shows when the proxy does not answer or refuses the sign-in, and the page error names the proxy. A member can also share the connection of their own computer as the proxy of a profile on a joined server. The computer opens only public internet addresses. Owners and admins manage proxies from the desktop app and the web (browser-proxies-v1, browser-egress-v1). Migration 56 adds the browser_proxies and browser_profile_proxies tables. Closes #3443 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fix proxy relay races and egress edge cases from review - Apply one profile proxy at a time, so two tabs that open together do not open two relays and leave one open. - Stop the relay of the old proxy when a proxy change closes the tabs. - Keep a saved password only when the address still has a user name. - Connect to a SOCKS5 proxy at an IPv6 address without the brackets. - Refuse a site name that browser-egress-v1 cannot carry before it goes to the computer, which closes the channel on a bad frame. - Open a new egress channel when the last one is closing. - Stop the computer proxy muxes before the team WebRTC bridge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Remove unused proxy relay and port exports Knip found five exports that only their own file uses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Refuse a proxy address with a password and no user name The database refused such a proxy, so the save failed with a generic error. The parser now refuses the address, and the dialog shows that the address is not valid. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 5 days ago | |
Give each browser profile its own proxy (#5145) * Give each browser profile its own proxy A named browser profile can use a saved proxy: socks5, http or https, with an optional sign-in. The password is encrypted and shows only as a mask. A SOCKS5 proxy with a sign-in goes through a relay on 127.0.0.1. When the proxy cannot be set, the tab does not open, so pages never go out without the proxy. A badge shows when the proxy does not answer or refuses the sign-in, and the page error names the proxy. A member can also share the connection of their own computer as the proxy of a profile on a joined server. The computer opens only public internet addresses. Owners and admins manage proxies from the desktop app and the web (browser-proxies-v1, browser-egress-v1). Migration 56 adds the browser_proxies and browser_profile_proxies tables. Closes #3443 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fix proxy relay races and egress edge cases from review - Apply one profile proxy at a time, so two tabs that open together do not open two relays and leave one open. - Stop the relay of the old proxy when a proxy change closes the tabs. - Keep a saved password only when the address still has a user name. - Connect to a SOCKS5 proxy at an IPv6 address without the brackets. - Refuse a site name that browser-egress-v1 cannot carry before it goes to the computer, which closes the channel on a bad frame. - Open a new egress channel when the last one is closing. - Stop the computer proxy muxes before the team WebRTC bridge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Remove unused proxy relay and port exports Knip found five exports that only their own file uses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Refuse a proxy address with a password and no user name The database refused such a proxy, so the save failed with a generic error. The parser now refuses the address, and the dialog shows that the address is not valid. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> | 5 days ago |
| Files | Last commit | Last update |
|---|---|---|
| 17 days ago | ||
| 17 days ago | ||
| 5 days ago | ||
| 5 days ago | ||
| 5 days ago |