On the hosted service the console is at
app.mithunai.com, and the others at chat.mithunai.com, agents.mithunai.com and gateway.mithunai.com. The console’s sidebar links to the other surfaces your deployment has set up, under the main navigation. A surface your deployment does not run is not listed.
How the surfaces fit together
- Models. Chat, Agents and the console’s assistants all reach models through the Gateway. No surface holds provider credentials of its own.
- Knowledge. Chat reads the knowledge you connected in the console, through the same read-only tools the MCP server offers. It cannot change your sources or settings.
- Organisation. What you see on every surface belongs to your organisation and to no other. See Organisations and roles.
Who can sign in to each surface
You sign in once, with your MITHUNAI account. Opening Chat, Agents or the Gateway sends you to the MITHUNAI sign-in and back.
If you open Chat or Agents with an account that is not a member of that organisation, sign-in is refused with the message “This account is not a member of the organisation this application belongs to.” Ask an Owner or Administrator of that organisation to add you. One sign-in has the detail.
What differs from the console’s answers
An assistant in the console, the widget, the API and MCP answers only from your content, cites it, and abstains when your content does not cover the question. That rule belongs to the answer engine.- Chat is a general chat workspace. A reply that comes from your knowledge is grounded and cited in the same way; other replies are the model’s own.
- Agents act instead of answering: they run steps and call tools. They are not bound by the grounding rule.
- The Gateway routes model calls. It does not retrieve, ground or cite anything.