[1.88.1] - 2026-10-26
- FIXED: Some AI apps could not work with b4's MCP server - LM Studio, also through LobeHub, refused every request because five tools without arguments, such as b4_status, lacked a field it requires. With Allow active probes on, apps using OpenAI's API refused every request too, because one tool description was longer than that API accepts. Gemini CLI adds an argument of its own to tool calls, and b4 refused those calls.
- FIXED: b4_check_domain told AI apps that a domain was covered when a set listed only one of its subdomains - an ad-blocking set that lists ads.youtube.com made youtube.com look covered, so an AI app could decide that nothing needed adding. A link or a host with a port was reported as not covered instead of being checked by its host. A very long name kept the router's processor busy for minutes, in the web interface's domain checks as well.
- FIXED: Other MCP tools gave AI apps wrong information - b4_recent_connections named its columns wrongly and said that an empty answer meant no traffic since b4 started, though it keeps only the last 500 events. b4_logs_tail called every line of the error log an error and could return older lines from the rotated log while skipping newer ones. The setting descriptions that AI apps read through b4_get_topic got some modes wrong, for example they called every SNI mutation mode compatible with real servers.
- FIXED: Settings changed through MCP could behave differently from what the AI app was told - a set switched on with b4_set_config_value matched nothing until b4 restarted. A port filter added to a set without targets, or the removal of its last target, made the set act on every connection on its ports, and the reply did not say so. Out-of-range numbers and unknown option values were saved and reported as applied, and some of these numbers could stop b4.
- FIXED: MCP permission checks had gaps - a write waiting behind another one was still saved after Allow configuration changes was turned off. An AI app could move a SOCKS5 server without a password from 127.0.0.1 to a network address, and could point the addresses b4 fetches its Telegram server lists from at any address, local ones included. The tool hints told AI apps that b4_find_bypass_strategy changes nothing, although its apply action rewrites sets.
- FIXED: Copy JSON copied a set as dozens of lines, too long for a chat message - in 1.88.0 the copy took the formatted text of the Set Configuration JSON box. Copy JSON in Discovery's Apply as a set dialog copied the set formatted too.
What's Changed
- feat: enhance JSON export functionality and improve copy behavior by @DanielLavrushin in #464
- Enhance domain handling and validation in API by @DanielLavrushin in #465
Full Changelog: v1.88.0...v1.88.1