Get help and check changes

Fix sign-in and reconnect the right service

Your Mensara account, your Mind’s Portal, an AI client and a model provider can each have their own session. If one stops working, reconnecting a different one will not repair it. This guide helps you identify the boundary and make a harmless check after reconnecting.

Contents

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

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Fix sign-in and reconnect the right service

Guides · Get help and check changes · [How it works](https://app.mensara.ai/how-it-works)

Your Mensara account, your Mind’s Portal, an AI client and a model provider can each have their own session. If one stops working, reconnecting a different one will not repair it. This guide helps you identify the boundary and make a harmless check after reconnecting.

[Page as Markdown](https://app.mensara.ai/how-it-works/reconnect-and-sign-in.md)

## 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](https://app.mensara.ai/how-it-works/account-and-billing#check-the-organisation-and-signed-in-account) 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](https://app.mensara.ai/how-it-works/portal-mcp-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](https://app.mensara.ai/how-it-works/versions-and-changes) 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](https://app.mensara.ai/how-it-works/model-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](https://app.mensara.ai/how-it-works/interrupted-work) 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

- [Portal, MCP and CLI](https://app.mensara.ai/how-it-works/portal-mcp-cli)
- [Manage notifications and check your Mind’s health](https://app.mensara.ai/how-it-works/notifications-and-health)
- [Manage models and service connections](https://app.mensara.ai/how-it-works/model-connections)
- [Recover pending, failed or interrupted work](https://app.mensara.ai/how-it-works/interrupted-work)

Previous page: [Manage notifications and check your Mind’s health](https://app.mensara.ai/how-it-works/notifications-and-health)

Next page: [Recover pending, failed or interrupted work](https://app.mensara.ai/how-it-works/interrupted-work)

When a connection stops, the last action may have failed, may still be running or may already have completed without its response reaching you.

[Join the waitlist](https://app.mensara.ai/#waitlist)