Skip to main content
Barrier

Releases

Changelog

Changes to the Barrier desktop client.

  1. New six-page client, automatic Strict Mode with pre-launch checks, chain failover, a per-account computer limit and account switching with sign-in backup.

    Platforms:Windows · 64-bit (x64)macOS · Apple silicon (M-series)macOS · Intel

    New

    • A new client with six pages — Connect, Accounts, Cleanup, Browser, Plans and Me — in English and Chinese. You can connect without adding a Claude account.
    • Pressing Start turns on Strict Mode automatically, then checks and repairs the environment before launch. With an account selected it also checks that the account’s country, the exit and the system agree.
    • Start results from all four stages are kept; select a stage to see only its items. One-click fixes are at the bottom.
    • Windows: detection of Claude Code start-up items, periodic process checks in the workbench, process handling before an account switch, and one-click fixes for time zone and system language.
    • “My account”: account details, password, managed accounts, signed-in computers, orders and the usage agreement in one place.
    • A limit on signed-in computers per account: 2 by default, more can be added while buying or during the plan.
    • macOS: Claude-only keychain cleanup with a re-check that keeps other apps’ credentials.
    • Account switching saves and restores the local sign-in state and prefers a chain that matches the exit’s country and region; on macOS keychain items are backed up with the files.
    • Residential exits can be bought by country, showing the region, available IPs and remaining slots.
    • Windows: encrypted account configs and per-account browser binding.

    Improved

    • The proxy chain tests each node at a set interval (10 seconds by default) and replaces a failing front node without restarting the core; the fixed exit stays the same.
    • Stricter exit lock: in rule mode, DIRECT, sub-rule and unmatched traffic all go through the chain; only this computer and the LAN stay direct.
    • Remote subscriptions can no longer set inbound listeners, the control interface or Strict Mode settings.
    • After an abnormal exit, the next launch logs the previous run’s processes, start time, last log lines and crash report location.

    Fixed

    • After an abnormal exit the core could fail to start while Strict Mode still pointed traffic at a dead port.
    • On macOS the core could fail to start after a reboot; the app now falls back to its built-in core when the system service is unavailable.
    • A blocked chain kept retrying the same dead front node instead of recovering.
    • A blank page on macOS Big Sur.
    • The updater no longer uses a zip dependency with a known vulnerability.