Deep Dive
1. Bot Package Patch Update (15 January 2026)
Overview: This minor patch updated the bot development kit to properly label missing data in private chats. It ensures bots run more reliably when users send them direct messages.
The update changed the code to return "undefined" instead of "null" for the spaceId variable when a bot is in a direct message (DM) context. This is a technical refinement that helps developers write cleaner, less error-prone code for their automated agents.
What this means: This is neutral for $TOWNS because it's a minor backend fix for developers. It doesn't change the core protocol or directly improve the end-user experience, but it helps maintain a stable environment for builders creating bots on the network.
(Source)
2. Direct Message Support for Bots (2025)
Overview: This earlier update was a significant addition, allowing automated bots to participate in private one-on-one conversations, not just public group chats.
It introduced an isDm flag that developers can check to know if a message came from a private chat. This enabled a new category of personal assistant and customer service bots within the Towns ecosystem.
What this means: This was bullish for $TOWNS because it expanded the protocol's utility. By enabling private bot interactions, it opened doors for more sophisticated and personalized automated services, potentially increasing developer engagement and real-world use cases.
(Source)
Conclusion
Towns' codebase has seen incremental, developer-focused improvements over the past year, with the last documented feature enhancing bot versatility. The development pace suggests ongoing maintenance rather than rapid protocol evolution. What new features might be in the pipeline to drive the next wave of user adoption?