What is new in MITHUNAI
Changes customers can see, newest first, each dated to the day it was completed. Work in beta says Beta, and what it has not yet done.
Published by MITHUNAI.
Last updated
November 2026
Beta: Microsoft Teams answers and approvals, and Expensify for Finance
Beta. Access on request. MITHUNAI can answer in Microsoft Teams: ask the bot in a personal chat or by mention and it replies from your knowledge with numbered sources, or says “I don’t know”. An administrator connects the Teams organisation, and where approvals in Teams are switched on, an AI employee’s action waits on a card that only the person it is linked to can decide. Beta. Access on request. Both are off until your deployment sets them up and not yet tried against a real account: neither has yet run against a real Teams tenant. Teams as a chat tool for the employees themselves is still not connectable. The Finance employee can also read card spend and receipts in Expensify, read only: it approves, returns and reimburses nothing. Four more Beta features arrive switched off: a Sales mailbox for each rep (drafts only), a stored widget presentation, an AI gateway policy for one organisation set by platform staff, and kept answer-quality eval sets and runs.
MITHUNAI Team (Beta): DevOps takes webhooks, and what stays unconnected
Beta. Access on request. The DevOps employee can take signed Sentry and PagerDuty webhooks as its starting point, and Support can pick up new Freshdesk, Intercom and Zendesk tickets by itself. Both are off until your organisation switches them on, and each is not yet tried against a real account. DevOps only proposes: a rollback or restart is never sent. Every write across the six employees waits for a person: Allow once, Deny or, where rules are on, Always, which the riskiest actions never offer. Microsoft Teams, ServiceNow and expense systems other than Ramp cannot be connected yet.
MITHUNAI Team (Beta): the Marketer posts, Finance reads the books
Beta. Access on request. The Marketer posts to X and LinkedIn and reads Google Search Console, and the Finance employee works in QuickBooks Online or Xero and reads card spend in Ramp. Each tool is connected with your own credential and is not yet tried against a real account. Every post waits for a person’s approval; the Marketer finds which pages lost search clicks and why; Finance drafts bills and invoices and re-codes bill lines for approval, and nothing it does pays, transfers, refunds or approves.
AI search visibility: a proposed fix for a question you lose
Beta. Not yet run against a real AI search engine. For a question an engine answers without you, a section can be drafted from your own knowledge and sent, once a person approves it, as a GitHub pull request or a WordPress draft. It is built and tested and not yet tried against a real account.
The widget as a search box, a sidebar or a form deflector, in Beta
Besides the chat panel, the widget can sit in your page as a search box, dock as a sidebar, or stand beside your support form and show a cited answer before the form is sent, counting the requests it turned away. Over MCP, a client can now rate an answer its key received. Both are built and tested, and neither has yet run on a real page or client.
A re-sync that would remove much of a source waits for you
When a re-sync would remove more than 45% of a source’s documents, nothing is removed until a person confirms the removal or keeps the documents. It has not yet held a real source’s re-sync.
Audit-log export and answer-quality scores, built
Owners and administrators will be able to export their organisation’s audit log as CSV or JSON Lines, and score an assistant against an eval set of their own questions for grounding, citations and the sources they expected. Both are built and tested and not yet deployed; the scores have not yet run against a live model.
Model spend budgets, personal-data redaction and fallback, built
The platform can hold a monthly model-spend budget with alerts at 50, 80 and 100% and, if you choose, refuse past it; keep e-mail addresses, phone and card numbers and similar out of prompts; fall back to a second model; and answer an exact repeated question from a cache. Each is set for the whole deployment, not per organisation, is not yet deployed, and has not run against a real provider.
MITHUNAI Team (Beta): approvals you control and more tools
Beta. Access on request. Each proposal now waits on a card that reads Deny, Allow once or, where your organisation turns approval rules on, Always allow, never for money, deleting, publishing or access. The Support employee can be tried on solved tickets first, and works in Freshdesk and Intercom as well as Zendesk; the IT service desk prepares access changes in Okta, Google Workspace or Microsoft Entra ID; DevOps investigates with Sentry, Datadog and PagerDuty and drafts the postmortem; Sales drafts follow-ups in one Gmail or Outlook mailbox you name. Each tool is connected with your own credential and is not yet tried against a real account.
Proposed answers and answering in Slack, in Beta
For a group of questions your sources could not answer, Proposed answers drafts an answer from those sources for a person to review and publish. Answering in Slack, in the thread with numbered sources or “I don’t know”, is built and off until set up: it has been tested against a scripted Slack and is not yet tried against a real account.
October 2026
A monthly answer allowance for every organisation
Every product that answers counts against one monthly allowance per organisation, and the Dashboard shows it as “X of Y answers used this month”.
Change a member’s role, remove a member or hand over ownership
Owners and administrators manage the people in their organisation from Settings, and an owner can hand the organisation to someone else.
Top questions
The console lists the questions people ask most, counted without naming anyone who asked.
More kinds of source
GitHub issues, pull requests and discussions; your own question-and-answer pairs; OpenAPI schemas in JSON or YAML; and public Zendesk help centres and Discourse forums.
Edit, pause and resume a source
A connected source can be changed, paused and resumed without removing it and starting again.
A one-line widget snippet and a three-step website setup
Adding the Ask AI widget to a site is one line to paste, and the console walks through connecting a website in three steps.
Source analytics and coverage gaps
The console shows which sources answers come from and which questions found nothing to answer from.
September 2026
MITHUNAI Chat and MITHUNAI Gateway at their own addresses
Chat, a workspace for your team over your own knowledge, and the Gateway, one OpenAI-compatible endpoint for your model providers, are live at chat.mithunai.com and gateway.mithunai.com.
MITHUNAI’s own public addresses
The console is at app.mithunai.com, the HTTP API under /mithunai/api/v1 and the widget bundle at mithunai-widget.js.
An abstention says what kind of gap it found
When an assistant declines, it says whether nothing relevant was found or the sources could not support an answer.