May 20, 2026

External chat via Discord, Ubiquiti control, location search

Discord integration was rearchitected from a tool into a dedicated communication channel

Discord integration was rearchitected from a tool into a dedicated communication channel. A new ExternalChatMessageProcessor (ECMP) handles inbound Discord messages, distinguishing owner messages as ‘user’ and third-party messages as ‘third-party-user’. The processor enforces a new ‘discord’ policy context with defaults that allow research tools but deny personal data tools. Discord.send_message is the sole communication action. The old DiscordAbility tool and its actions were removed, and the Brain UI policy tab was renamed to ‘External chat’ with a Discord sub-tab.

A UniFi network control capability was added with nine actions for managing clients, devices, WLANs, traffic rules, port forwarding, and guest authorization. The ability supports dual authentication, SSL fallback, and conditional UI in the Brain policy tab. It was included in the discoverable lists for UMP, DMN, and Subagent processors. A follow-up fix hardened input validation, thread safety, SSL handling, and unreachable error checks.

All LLM provider clients now send app identification headers. OpenRouter and compatible aggregators receive HTTP-Referer and X-Title headers so Chalie appears on usage dashboards. The change affects all four provider clients and bumps the version to 0.7.1.

Episodic recall output now includes a location_name field (formatted as ‘at:’) derived from geocoded places. A new optional location parameter on memory.recall filters episodes by place name or saved place label, and AND-gates with the query parameter.

  • Discord is now a communication channel with its own ECMP processor and policy context, instead of a tool.

  • Discord policy defaults restrict personal data tools but allow research and sending messages.

  • Ubiquiti UniFi capability with nine network control actions added and exposed to all processors.

  • All LLM providers send app identification headers for dashboard visibility.

  • Memory recall supports location-based filtering and episodic recall shows location name.

  • Input validation and thread safety hardened for Ubiquiti integration.