orgoai/bops is a service where multiple AI bots form a single team to handle work operations. Each bot has its own dedicated computer, email address, and phone number. The 2026-11-06 commit 21368b9(#180) redrew the team member permissions editing screen and removed the "Choose access" step that the invite form had kept separate, so the permissions received there can be viewed directly. The new screen divides the permission items into three named groups.
The first group is Bots, containing All bots (all bots), individual bots, and Bots you make later (bots you make later); the second is Apps and computers, containing Your Apps, Use its computer, and Keys; and the third is the changeable items (What they can change). The All bots row shows that level only when all bots are at the same level, and Bots you make later applies only to bots created later. In the invited state, Use its computer and Keys are displayed switched off and have to be turned on after joining. The problem where choosing a single bot also turned off switches that were already on has also been fixed.
The code was touched to the extent of 139 added and 86 deleted lines in components/app/members.tsx, 16 added and 1 deleted line in lib/members.ts, and 36 added and 28 deleted lines in the UI test script scripts/test-members-ui.mjs. At the same time, docs/releases/v0.0.50.md was newly added, and the commit message states that it is notes for v0.0.50.
However, since the new file is only 2 lines, the release body cannot be known, and since the patch for lib/members.ts is not given, it cannot be confirmed whether the member permissions data structure changed together with the server-side permission evaluation. The license and the implementation language are also not in this record. Summarizing, this is a change that makes the screen structure clear as three groups and shortens the invitation procedure by one step. However, whether the permission evaluation rules themselves changed is hard to conclude from this record alone. It is better to decide on adoption after separately checking the server-side permission logic and the license.