v0.16.0
New
- Proxy usage per route and static proxy pool — admins can now attribute proxy traffic to individual routes and accounts, and assign dedicated static proxies to specific connections for predictable syncing
- Proxy health monitor in the admin panel — periodic background probes keep proxy status current so you can spot connectivity issues before they affect users
Improved
- Large-workspace loading is significantly faster — the engine now throttles connection binding and folder-fetch bursts, cutting main-thread blocking and reducing churn during reconnects
- "Reconnect Required" badges now only appear when there is a real connection problem — the badge no longer shows when the backend Telegram session is healthy, preventing unnecessary re-logins and phone flood limits
- Proxy connection status in Settings now always shows the correct state — it no longer appears as loading when your accounts are healthy
Fixed
- Audio messages now play correctly for all incoming messages
- "Socket closed" connection errors affecting some workspaces are resolved
- Supergroup and channel history loads correctly — "Invalid realtime command payload" errors for history navigation are gone
- The page no longer freezes while chatting or forwarding messages
- Account setup no longer floods the app with repeated 400 errors while Telegram authentication establishes
- Online status is now consistent — the indicator in the chat table matches the one in the chatter header
- Sender names in group chat message bubbles and previews are always correct
- Unread counts stay accurate as messages stream in and connections reconnect
- Messages no longer duplicate in the chat view when two or more connected accounts share the same chat
- Sender labels no longer appear as "other" in chat history; reaction popovers now load correctly
- Joining a workspace no longer crashes the CRM chat table
- Chats stay in folder views after you reply — "Exclude read" folders no longer evict chats immediately after a send
- Dead Telegram sessions now automatically recover instead of staying stuck indefinitely
- Users removed from a workspace no longer re-appear on refresh via the onboarding invite link
- Trial owners can now subscribe before purchasing workspace seats — the dead-end 400 error is fixed
- Media and video playback no longer fails with rate-limit errors; streaming requests bypass the generic rate limiter correctly
- Subscription purchases work reliably — resolved auth conflicts that caused 401/403 errors at checkout
- Search results are now complete and consistent across all connected accounts
- "Time since first incoming message" now counts from when Telegram received the message, not from when you opened Entergram
- Broadcast flow cleaned up — removed obsolete Auto-Translate and After-Send automation options
- Email change requests can now be cancelled from your account settings
- MCP now sends messages to Telegram contacts you have never chatted with before — the previous error on first contact is resolved
- Chat selection in the light theme is clearly visible again — the row highlight now has proper contrast in white mode