Skip to main content
You can now take over a conversation from the AI, and a resolved conversation stays closed. New settings control where the widget shows, and developers got official SDKs, analytics in the API, and a larger MCP server.

​
New

  • Select Take over the chat on a conversation to stop the AI while your team replies. Select Release to AI to give it back. See Reply and take over.
  • Mark as Resolved now closes a conversation. The visitor cannot send new messages, and only your team can open it again. This works in the widget, in all channel integrations, and in the API.
  • When a visitor who left an email is waiting for your team, SiteGPT emails them your reply with a link back to the conversation. Replies close together go out in one email. See When SiteGPT emails your reply to the visitor.
  • Lead and escalation emails now have a button to reply to the visitor. A reply to the email also goes to the visitor, not to SiteGPT. See Notifications.
  • Delete all data of one visitor from the Leads page. See Delete a lead or all of a visitor’s data.
  • Use Allowed Domains in Settings > General to let the widget load only on your own websites. See Control where the chatbot appears.
  • Use Excluded Pages in Settings > General to hide the chat icon on the pages that you name.
  • Show a conversation starter only on some pages. The CLI and API v2 support this too. See Conversation starters.
  • Choose the language of the message timestamps in the widget, in Language & Region. See Change the widget language and text.
  • Read your chatbot’s daily engagement numbers through API v2, the SDKs, the CLI, and MCP. See Analytics.
  • Official API v2 SDKs for TypeScript, Python, and Go.
  • Use the Convex component to get chatbot answers and sync content from your Convex app.
  • The SiteGPT MCP server now has more tools, for example to chat with a chatbot, read analytics and leads, and add content. In AI apps that support it, some tools show views inside the conversation. See MCP.
  • The SiteGPT MCP servers are listed in the official MCP registry. Run npx -y @sitegpt/mcp to start the server on your own computer.
  • AI agents can ask the SiteGPT support agent questions over the A2A protocol. See A2A.
  • AI agents can create a SiteGPT account and sign in with AgentID. See Use SiteGPT with AI agents.
  • sitegpt.ai pages and docs pages have a Markdown version for AI agents. A docs MCP server lets agents search these docs.

​
Improved

  • When an answer is longer than the chat window, the window now stays at the start of the answer.
  • The chat widget got accessibility fixes for contrast, keyboard focus, and screen readers.
  • The Attention view in chat history no longer shows resolved conversations.
  • Unknown API paths now return a JSON error with a hint. GET /api/v2/health checks that the API is reachable without a token. See API conventions.
  • MCP answers no longer include internal IDs or teammates’ email addresses.
  • The CLI and API now show the current model names everywhere.
  • The WordPress plugin is tested with WordPress 7.1.

​
Fixed

  • Connecting Messenger, Google Chat, Zoho, and Freshdesk Messaging works again.
  • Replies sent from the iPhone app reach the visitor again. App versions 1.0.1 and 1.0.2 also show lead and handoff messages and let you retry lists that fail to load.
  • A short network error while SiteGPT checks your quota no longer makes content fail to train.
  • A chat icon with a transparent background no longer shows a shadow.