Connection, access and permission problems
Find the setting that owns the missing access.
Select the intended workspace and confirm the signed-in account before changing a connection. Access can depend on the workspace role, repository installation, provider account, or a specific tool server.
Missing GitHub repository
Check the GitHub app installation's selected repositories, the owning GitHub account or organization, and the workspace's repository attachment. Refresh the list after changing installation access. A personal GitHub identity link does not grant installation access.
Use GitHub and repositories.
Model unavailable or authorization expired
Inspect the model picker, the selected provider's integration page, and the affected teammate's model restrictions. Reconnect ChatGPT, Claude, or Cursor using the flow for that provider.
Do not paste provider keys or authorization codes into session chat. A valid connection can still have provider-side limits.
Slack or Sentry no longer works
For Slack, check bot identity, team connection, channel membership, incoming workspace, and any reauthorization request. Existing threads keep their original mapping. For Sentry, check the authorized organization and projects, then the trigger's documented scope.
A successful connection is different from a specific incoming event being eligible to start work.
An external tool is unavailable
Check the workspace MCP server: enabled state, public HTTPS address, supported transport, authentication header, and server availability. New sessions capture the enabled server set. Disabling or deleting a bound server can block its use, and an unavailable server can prevent a turn from starting.
For an external coding client calling Uno, inspect Uno MCP troubleshooting instead. The two directions use different connections.
A setting or mutation is forbidden
Check membership and role. A viewer can inspect permitted information without being allowed to change it. A Session API key needs the correct workspace and scope; MCP authorization retains the user's own limits.
Share the error, affected workspace, and relevant record link with an admin. Keep secret values and access tokens private.