[BUG] claude agents breaks with "Can't access this organization" after auto-update to 2.1.132

Resolved 💬 2 comments Opened May 15, 2026 by joshdjuric Closed May 19, 2026

Description

After Claude Code auto-updated to 2.1.132 (at ~4:55 AM on 2026-05-15), claude agents stopped working. Attempting to authenticate shows a browser page with:

Can't access this organization You don't have access to this organization or it doesn't meet the requirements for Claude Code. Contact your organization admin to request access or check your Claude Code settings.json configuration.

This was working fine on the previous version throughout 2026-05-14.

Steps to Reproduce

  1. Have forceLoginMethod: "console" and forceLoginOrgUUID set in ~/.claude/settings.json (Console org auth)
  2. Update to Claude Code 2.1.132
  3. Run claude agents
  4. Attempt to authenticate → browser shows "Can't access this organization"

Expected Behavior

claude agents authenticates and displays background sessions as it did on the previous version.

Actual Behavior

Auth flow redirects to a browser page with "Can't access this organization" error. Interactive claude terminal sessions continue to work fine — the regression is specific to claude agents.

Environment

  • Claude Code version: 2.1.132
  • OS: macOS 25.4.0
  • Auth method: forceLoginMethod: "console" with forceLoginOrgUUID set in settings.json
  • Updated at: 2026-05-15 ~04:55 local time (auto-update)

Notes

Interactive terminal sessions work without issue — the problem is isolated to the claude agents view. Likely a change in how claude agents handles auth for Console-org setups introduced in 2.1.132.

~ Automated via Claude

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗