> ## Documentation Index
> Fetch the complete documentation index at: https://docs.newly.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Latest updates and improvements to Newly

<Update label="May 25, 2026" description="Per-project backends, compliance fixer, redesigned support widget, new chat bar, and more">
  ## New features

  * **Per-app marketing website generator** — Generate a polished landing page for any app to satisfy store compliance requirements, then edit it from a dedicated website chat panel. [Learn more](/features/marketing-studio)

  * **Brainstorming mode for plan mode** — The plan mode now asks deeper and better questions. [Learn more](/features/ai-chat)

  * **Redesigned in-app support widget** — The support widget has been rebuilt with a multi-ticket flow, a home/help/chat layout, and image attachments via drag, drop, or paste — making it faster to file issues and track replies.

  * **New chat bar and toolbar** — The project chat bar and tool strip have a fresh layout and design that surfaces actions more clearly and gives you more room to work. [Learn more](/features/ai-chat)

  * **Hub chat widget** — The marketing site now has a Gemini-backed Hub chat with a wandering mascot, so visitors can ask product questions and get linked to the right docs.

  ## Updates

  * **Markdown in question cards** — Clarifying-question cards in chat now render full markdown, so links, lists, and code formatting all come through.
  * **Friendlier tool errors** — When the agent hits an unknown-tool error, it now gets a recovery hint and keeps going instead of surfacing a raw error.

  ## Bug fixes

  * Fixed mascot rendering glitches in the Hub chat widget on mobile browsers.
  * Fixed activity events occasionally leaking across user sessions on shared workspaces.
  * Fixed in-flight builds racing with backend changes, which could leave a branch in a half-applied state.
  * Fixed a website-editor issue where build artifacts from one project could bleed into another.
  * Fixed the displayed average response time on the support widget to reflect the correct time.
</Update>
