Identify where you are signing in
The Mensara account site manages organisation membership, billing and your Mind address. Your Mind’s Portal is the workspace web interface at that address. An external AI tool connects to the Mind through its own supported setup. A model provider supplies the AI response and may require separate consent.
Check the intended organisation, Mind address and signed-in person before changing anything. A teammate should use their own identity. Account and billing helps locate the account context.
Reconnect a chat or coding client
Use the current setup instructions for your chosen tool in the Portal. Follow its normal sign-in and consent flow for the intended Mind, then open a fresh tool session if the client requires one. Portal, MCP and CLI explains the supported connection routes.
Ask the connected agent to identify the Mind and principal, then read one harmless record you are allowed to use. A successful login message alone does not prove the tool can access the correct workspace. Do not copy tokens from another client or account.
Check the Portal’s diagnostics
In Settings → Connection status, inspect Access configured, Mind reachable, Access token accepted and Version supported. Start with the first failing check. Later unknown checks have not been tested successfully.
If the Mind is unreachable, collect the time and bounded error for the operator. If access is refused, have the owner inspect membership and effective access. If a version is unsupported, check the actual installed versions rather than repeatedly signing in.
Reconnect a provider or external service
For personal chat, use Settings → Model connection → Change provider. For a sensor’s external account, inspect Settings → Connections and use its owner-authorised connection route. These are separate from permission for an installed app to use that route.
After reconnecting, test the relevant harmless action and inspect its result. Managing connections explains the app grants and model access that may still be needed.
Recover unfinished work
Keep the reference to a proposal, run, invitation or payment that was in progress. Reconnecting does not tell you whether that action completed before the connection stopped. Inspect the original result before repeating it.
If sign-in remains blocked, give support the destination, time, role and exact bounded message. Never send a password, access token, device code or recovery key.
Related
Practical guides for people and agents