Open Chat Updates

Web development URLs are now worktree-aware, so each Git worktree can get its own branch-prefixed .localhost address automatically. Setup also prints the expected URL patterns, making it easier to find the right local site when switching between worktrees.

The README header now includes a sponsorship badge for E2B for Startups, with a direct link to the program page. This makes the project’s sponsorship more visible and gives readers a quick way to learn more.

This release adds support for sending password reset emails and tightens a few safety-related defaults. It also consolidates streaming job handling, including richer stream content updates and new migrations to keep existing message data compatible with the latest streaming and reasoning format.

Streaming is now more reliable, with clearer handling for timeouts, message timing, and web search availability. This release also adds automatic database health alerts and strengthens authentication setup, helping prevent common sign-in and callback issues in preview environments.

This release adds Vercel Speed Insights across the web app, so performance data can be collected on every page. This helps you and the team spot real-world speed issues and track how changes impact the experience over time.

This release adds new chat utilities, including chat exports, chat forking from a chosen message, and dedicated title generation and saving. It also tightens a few key guardrails, like rate limiting for prompt template auto-save and clearer message and file validation, so everyday usage is more reliable.

This release adds new ways to work with conversations, including exporting a chat, forking from a specific message, and generating titles with more control. It also tightens a few safeguards, like rate limiting for template auto-save and stronger validation around messages and file uploads.

This release adds automated test coverage for the Settings page to help catch regressions earlier and keep account and preference flows behaving consistently as the app evolves. While there are no visible UI changes, this work supports a more reliable experience over time by validating key Settings interactions.

You can now trigger preview cleanup manually and provide a PR number, which helps remove leftover previews when an automatic cleanup did not run. This also ensures cleanup can run safely for manual requests, while keeping PR-based cleanup behavior intact for normal closed pull requests.

Deployments for the web app are now less likely to run at the wrong time. This helps ensure the intended build process runs only when required, reducing accidental or incomplete deploys and keeping releases more predictable.