Clearer chat, stronger miniapps, and more reliable project work

This release makes everyday work easier to follow. Chat navigation and message details are clearer, projects and tasks have more structure, and miniapps and specialists handle boundaries and failures more safely.

Chat keeps its place and gives more context

Browse Channels now restores focus to the right place, and emoji-only messages can be larger without making the conversation feel cramped. Attachment previews open at a more useful size, message timestamps reveal both local and UTC time on hover, and project rows match the density of the rest of the chat interface.

When a specialist cannot start, chat now explains the failure and provides a traceable reference. Provider errors preserve their original cause, and the chat and garden Workers bundle the Loro runtime they need instead of relying on missing deployment assets.

Projects and tasks are easier to manage

Workspace-bound task coordination now has clearer observability, so task work can stay connected to the workspace that owns it. Project settings have a cleaner layout and can open directly from the Projects page, while key routes preload their data before navigation finishes.

Settings also clears stale workspace model warnings after hydration, resets scroll position when sections change, and prevents view-only members from writing sandbox profiles.

Miniapps are safer and more dependable

Interactive documents now run in isolated child frames and preserve useful crash reports when something goes wrong. Browser and Code miniapps regain their expected styles, and the Polar Marketplace experience has been rebuilt around a clearer flow. TAP Email can attribute actions using existing sessions without asking users to reconnect.

Oversized MCP tool catalogs no longer crash the app, and WebRTC is blocked inside isolated document frames so embedded content cannot bypass the intended boundary.

Specialists have clearer access boundaries

Chloe now receives read-only project access, while GitHub access works correctly for Chloe and language experts. Pending permissions are handled before a specialist resumes, and installed membership is consistent across mentions and custom installs.

A steadier platform foundation

Analytics now uses one PostHog identity and records chat outcomes more consistently. The release also improves CI diagnostics, keeps release automation focused on the right pull requests, and synchronizes canonical model metadata so the platform and its settings stay aligned.

AWS profile validation now reports the actual Bedrock configuration problem, making provider setup failures easier to diagnose.

2.24.1 patch release

Package MCP credentials can now be declared and managed for Email and other packages. TAP stores those values in the existing OS keychain and injects them only at the signed server endpoint, so live MCP tools can authenticate without exposing credentials in status responses or diagnostics.

Workspace migration also removes oversized copied profile avatars from older task extensions while preserving task content and assignment metadata. Those workspaces can start normally again, and the migration is safe to run more than once.