Two-person review for AI changes
Once a workspace has a second person who can approve, the member who launched an AI session can no longer approve its code change alone. A solo team still can.
When a session proposes code, it opens an approval that must pass before the change can become a pull request. Until now, anyone allowed to decide approvals could approve that gate, including the person who launched the session. One admin could start a session, approve it and get the pull request alone.
Now, once the workspace has another member who can decide approvals, the launcher's approval does not count. Someone else has to approve. The launcher no longer sees their own change in the list of approvals waiting for them. They can still reject it, since rejecting only stops a change.
A one-person workspace keeps self-approval, or its changes could never ship.
Earlier fixes in the same area closed related gaps: a member can no longer create their own approval to unblock a change, and a change edited after approval goes back for review. See approvals and policies for how approvals are set up.