v3.1.0

@frontman-ai/client

Patch Changes

• #1415 3ab55f5 Thanks @BlueHotDog! - Give annotated elements the same bounded DOM context as get_dom, including their parent and direct children, so agents can follow selectors instead of broadly searching source files. Keep get_dom shadow traversal compatible with navigable indexed >>> paths. Resolve Next.js React Server Component annotations through server-side source maps without issuing invalid browser requests for React's virtual source URLs, while preserving client-component source locations beneath server components.

• #1416 f8c6c52 Thanks @uinstinct! - Allow a second paste within five seconds to expand a pasted-text chip in place.

• #1415 3ab55f5 Thanks @BlueHotDog! - Prevent task failures from rendering duplicate error banners and reconnect cleanly after React Strict Mode lifecycle cleanup.

• #1415 3ab55f5 Thanks @BlueHotDog! - Stop reporting Astro DOM ancestors as component invocation callsites, attach React component props instead of selected host-element props when ownership matches, and preserve current-page context in task diagnostics.

• #1402 c30f33e Thanks @BlueHotDog! - Make Frontman work immediately on WordPress sites using Plain permalinks.

• #1410 f0868c4 Thanks @uinstinct! - Keep the thinking indicator visible for the whole AI turn, including while text is streaming.

• #1436 0224d40 Thanks @BlueHotDog! - Align Tiptap packages on version 3.30.1 and upgrade the repository to Yarn 4.18.

• #1409 6732667 Thanks @BlueHotDog! - Use explicit new-tab sign-in and sign-out flows in top-level and embedded Frontman clients. Ensure WordPress installations receive the updated hosted client instead of a browser-cached bundle.

@rescript/webapi

Patch Changes

• #1415 3ab55f5 Thanks @BlueHotDog! - Give annotated elements the same bounded DOM context as get_dom, including their parent and direct children, so agents can follow selectors instead of broadly searching source files. Keep get_dom shadow traversal compatible with navigable indexed >>> paths. Resolve Next.js React Server Component annotations through server-side source maps without issuing invalid browser requests for React's virtual source URLs, while preserving client-component source locations beneath server components.

@frontman-ai/astro

Patch Changes

• #1415 3ab55f5 Thanks @BlueHotDog! - Give annotated elements the same bounded DOM context as get_dom, including their parent and direct children, so agents can follow selectors instead of broadly searching source files. Keep get_dom shadow traversal compatible with navigable indexed >>> paths. Resolve Next.js React Server Component annotations through server-side source maps without issuing invalid browser requests for React's virtual source URLs, while preserving client-component source locations beneath server components.

• #1430 2646d4c Thanks @BlueHotDog! - Load packaged ripgrep binaries at runtime so grep and file search work from bundled integrations.

@frontman-ai/frontman-core

Patch Changes

• #1415 3ab55f5 Thanks @BlueHotDog! - Give annotated elements the same bounded DOM context as get_dom, including their parent and direct children, so agents can follow selectors instead of broadly searching source files. Keep get_dom shadow traversal compatible with navigable indexed >>> paths. Resolve Next.js React Server Component annotations through server-side source maps without issuing invalid browser requests for React's virtual source URLs, while preserving client-component source locations beneath server components.

@frontman-ai/nextjs

Patch Changes

• #1415 3ab55f5 Thanks @BlueHotDog! - Give annotated elements the same bounded DOM context as get_dom, including their parent and direct children, so agents can follow selectors instead of broadly searching source files. Keep get_dom shadow traversal compatible with navigable indexed >>> paths. Resolve Next.js React Server Component annotations through server-side source maps without issuing invalid browser requests for React's virtual source URLs, while preserving client-component source locations beneath server components.

• #1430 2646d4c Thanks @BlueHotDog! - Load packaged ripgrep binaries at runtime so grep and file search work from bundled integrations.

@frontman-ai/vite

Patch Changes

• #1415 3ab55f5 Thanks @BlueHotDog! - Give annotated elements the same bounded DOM context as get_dom, including their parent and direct children, so agents can follow selectors instead of broadly searching source files. Keep get_dom shadow traversal compatible with navigable indexed >>> paths. Resolve Next.js React Server Component annotations through server-side source maps without issuing invalid browser requests for React's virtual source URLs, while preserving client-component source locations beneath server components.

• #1430 2646d4c Thanks @BlueHotDog! - Load packaged ripgrep binaries at runtime so grep and file search work from bundled integrations.

@frontman-ai/frontman-wordpress

Patch Changes

• #1402 c30f33e Thanks @BlueHotDog! - Make Frontman work immediately on WordPress sites using Plain permalinks.

• #1409 6732667 Thanks @BlueHotDog! - Use explicit new-tab sign-in and sign-out flows in top-level and embedded Frontman clients. Ensure WordPress installations receive the updated hosted client instead of a browser-cached bundle.