[1.80.0] - 2026-08-25
- FIXED: Telegram kept reporting the MTProto proxy as incorrectly configured and switching it off, and the 1.78.0 fix was aimed at the wrong cause - the dialog comes from a single four-byte -444 relayed back from a data center, not from a slow dial, and b4 could send an ordinary session to a data center's media edge
kwsN-1, which answers a non-media session with exactly that. Both names lead to the same address, so that fallback routed around nothing, and a -444 ends the connection instead of reaching the client. - ADDED: An MCP server that can act on b4 rather than only describe it - the AI could read status and change one setting at a time, so anything a user asked for came back as instructions to carry out by hand. It gains per-setting facts, geosite and geoip search, target and set editing, the last update's transcript, and behind a separate Allow active probes permission, testing whether a domain loads and running Discovery.
Settings > Integrations. - ADDED: A log line for every MCP tool call and every request the endpoint turns away - a server able to rewrite strategy sets and make the router fetch a site left no trace, and a client guessing at the access token was refused silently.
- FIXED: A Discovery run's result became unreachable the moment the run ended - only the copy held in memory was consulted, and that is dropped 30 seconds after a run finishes, though the web interface had always applied the same result from saved history. A strategy named while a run was still testing also read as settled, and stopping a run early threw away what it had found.
- FIXED: The Discovery history file grew by roughly half a megabyte per domain tested - every strategy a run tried was saved with a full copy of the set b4 built to test it, so the hundred entries the file keeps could reach 60 MB on a router whose flash holds far less.
- FIXED: The watchdog judged every watched domain on a fetch that skipped b4's own bypass - its checks carried the mark b4 puts on traffic it has already handled, so the verdict described the unprotected path rather than the set meant to be protecting that domain.
What's Changed
- Implement MCP topic handling and enhance target expansion reporting by @DanielLavrushin in #323
Full Changelog: v1.79.0...v1.80.0rc1