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
{{ message }}
Repository navigation
Commit c299092
Browse filesBrowse the repository at this point in the historyBrowse files
Say plainly that a person's Bots share their computer, and fix the rest of the review
A person's computer follows the industry standard for an always-on agent's
computer: every Bot the person uses runs on it, a public Bot somebody else made
included, and a command any of them runs can reach anything there. The admin
Computers screen and the provider's description now say so, and an isolated
Bot's Setup says before it is made public, and while it is, that everybody who
uses it shares its computer and what is signed in to there.
Also from the review:
- Ticking Isolated asks the Bot owner's switch, the one runs are decided by,
not the editor's, so an administrator can no longer save a tick the Bot never
runs with.
- A Sandbox is cut by computer key: an isolated Bot keeps its files at the root
of the volume it had, instead of having them hidden by a new workspace root.
- With the supervisor, a private Bot's old files come to its folder on its
owner's computer, once, the same way its old profile does.
- A reset also forgets snapshots and page pictures filed under the Bot alone
from before computers were per person.
- Helm's computer requests 2Gi with an 8Gi limit, sized for a person's
browsers, with sizing guidance in values.yaml.
- An unreadable Isolated switch is logged, not silently read as off.
0 commit comments