pastilhasandClaude Opus 5
2bd96a9a98
f0af723granted chat to every role by default, which is right, but the route still refuses non-owners — so a new member gets a tile that resolves and an API that 403s, the exact broken stateb4f88ecandeda004awere built to remove. The fix is not to withdraw the grant. It is to answer the question the member actually has, which is "what do I do about it": their own claude, in their own home, needs them to sign in once with their own Anthropic account. The platform cannot do that for them — logging in is an interactive act against an account that is theirs, and the alternative, pointing them at the owner's credential proxy, spends the owner's subscription on their turns. GET /api-status returns two booleans about the caller's own home plus the one instruction that fits their case, so the UI can render a terminal saying "run claude once" rather than an error. Its own router, deliberately not on chatRouter: that router refuses every non-owner wholesale and is right to — reads there leak the owner's project directory names — which means an endpoint on it could not be read by the accounts that need it most. Same `chat` capability, no owner gate, and nothing in the response describes anyone but the caller. Frontend not done: nothing calls this yet, so behaviour is still unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>