Skip to content

Releases

Veil 1.14.2

Choose a tag to compare

@github-actions github-actions released this 07 Nov 18:36
42ce768

Fixed

  • TUN keeps working when a custom rule sends a LAN address through the proxy
    (for example a NAS at 192.168.10.25). Opening the LAN range for that rule
    also pulled the router into the tunnel, and every connection failed with
    "network is unreachable" again. The IPv4 default gateway now stays on the
    physical interface while the rule's address still goes through the tunnel.
  • The log pane follows the pointer steadily while you drag it taller or
    shorter, instead of jumping, and remembers its height once you let go.
  • The Sources tab opens quickly on large subscriptions: server rows are built
    as they scroll into view instead of all at once.

What's Changed

Full Changelog: v1.14.1...v1.14.2

Veil 1.14.1

Choose a tag to compare

@github-actions github-actions released this 07 Nov 13:25
701b2ea

Fixed

  • TUN no longer breaks every connection on networks where DHCP hands out the
    router as both the gateway and the DNS server (for example 192.168.10.1).
    Routing the system resolver into the tunnel also sent the gateway itself
    into the utun, so the core's direct dials failed with "network is
    unreachable". A resolver that is also the default gateway now keeps its
    physical route; a separate LAN resolver is still routed into the tunnel.
  • Bring the existing main window forward when opening Veil from the menu bar.
  • Render server rows as they approach the visible area and batch latency updates to keep large subscriptions responsive.

What's Changed

New Contributors

Full Changelog: v1.14.0...v1.14.1

Veil 1.14.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 22:57
4bb7ae1

Added

  • Request as for each subscription (Sources page, and the Add sheet).
    Panels decide what to send by the client asking: Veil introduced itself as
    Veil/…, which no panel's rules know, so it got a bare list of share links
    while Happ got the same subscription as a full Xray config with balancers.
    Pick Xray config or sing-box config to get the servers and balancer
    groups those clients get, or type a custom User-Agent. Changing it refetches
    at once, and diagnostics show the choice.
  • The panel's per-host Server Description is shown in the server list in
    place of the protocol name, as Happ shows it. It is read from a share link's
    #Name?serverDescription=<base64> — which used to end up in the name — and
    from an Xray config's meta.serverDescription.
  • Balancer setting (Settings → Connection): how a server with several
    nodes picks one when Xray runs it — Fastest (the default), Most stable,
    Round robin or Random. Xray used to pick a random node for every
    connection, where providers set their profiles up to use the fastest.

Fixed

  • A subscription that answers with a list of Xray configs — Remnawave's
    answer to clients it serves Xray JSON — is read instead of reported as
    unrecognised. Each config is listed as one entry named by its remarks,
    as Happ lists it — "Europe | Auto", not the panel's internal outbound tags —
    and balances over the nodes its own balancer picks from.

What's Changed

  • Ask panels for Xray or sing-box configs and list each Xray profile as one entry by @faustyu1 in #30
  • Release 1.14.0 by @faustyu1 in #31

Full Changelog: v1.13.0...v1.14.0

Veil 1.13.0

Choose a tag to compare

@github-actions github-actions released this 05 Nov 19:44
a5c4b28

Added

  • Veil mcp: the app binary is now an MCP server on stdio. Point Claude,
    Cursor or any MCP client at /Applications/Veil.app/Contents/MacOS/Veil
    with the argument mcp (Settings → Advanced → Copy MCP config). It starts
    Veil in the background if it is not running.
  • No AI switch in Settings → Advanced. When on, Veil does not open the
    socket assistants talk to, and every MCP call is refused with that reason.

Changed

  • New app icon: the split Veil shield on graphite, made in Icon Composer
    (Resources/AppIcon.icon). macOS 26 draws it as a Liquid Glass icon with
    its dark, clear and tinted looks; older systems get the same artwork.

Removed

  • The HTTP control API on 127.0.0.1:9091, its bearer token, port setting
    and "Let other programs configure Veil" switch. The same endpoints are now
    served over a 0600 Unix socket only the user's account can open, and only
    Veil mcp needs to know about it. The old token is deleted from the
    Keychain on launch.
  • The website. It moved, with its history, to
    The-Veil-Foundation/veil-site
    and is still served at https://veil.faustyu.xyz. docs/ keeps the control
    API contract (agents.md) and the design specs. The README links point at
    the site's own domain instead of the old github.io address.

What's Changed

  • New app icon: graphite shield, Liquid Glass on macOS 26 by @faustyu1 in #26
  • Replace the token-guarded HTTP control API with a Veil mcp stdio server and a No AI switch by @faustyu1 in #27
  • Release 1.13.0 by @faustyu1 in #28

Full Changelog: v1.12.0...v1.13.0

Veil 1.12.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 20:59
5be3e53

Added

  • Four ping modes, chosen in the list's menu or in Settings → Server list:
    TCP (a connection to the server, a QUIC handshake for Hysteria2 and TUIC),
    ICMP, and Proxy HEAD / Proxy GET, which send a request through
    each server to a test URL and time the answer. The proxy modes also catch a
    node that accepts connections but carries nothing. Proxy GET is the default;
    the test URL can be changed.
  • The main window can be made narrow, down to 360 pt, for the side of the
    screen. Below about 560 pt it switches layout by itself: the connect button
    moves under the status, the toolbar shows icons only and the filter chips
    move into the view menu.
  • Sorting, grouping, the alive filter, country and tag filters and the ping
    mode now live in one menu beside the search field. Its icon fills in while a
    filter is narrowing the list.
  • Servers can be grouped by protocol. Country, tag and protocol sections fold
    like subscriptions do, and their header shows the fastest ping in the group.
  • The iOS app catches up with the desktop. The server list now has subscription
    sections with notes, traffic and expiry, grouping, tag and protocol filters,
    sort by ping, pins, custom names and tags, and an arrange mode.
  • New Sources tab on iOS. It shows what each subscription returned, what was
    skipped and why, and the groups the panel declared. Every node opens in an
    inspector as Xray JSON or a share link, and manual nodes can be edited there.
  • Fastest-node and manual groups on iOS, your own or the panel's. Rules can send
    traffic to a single server or a group, not only to proxy, direct or block.
  • Community rule lists, the full DNS editor (servers, detours, fake IP, DNS
    rules) and the geo database screen on iOS.
  • iOS shows Apply now while connected when routing, DNS or groups changed.
    It reloads the core without dropping the VPN.
  • iOS settings gain list options, the subscription User-Agent, device ID
    management and a diagnostics report that is redacted before it is shared.
  • iOS long-press menus keep the everyday actions on top. Advanced swaps the
    open menu for the rarer ones, with Back to return, and the app behind is
    blurred while a menu is up.
  • Grouping, sort by ping and every filter live in one menu in the iOS
    navigation bar.
  • The iOS QR code is drawn with rounded dots and the app's mark, opens at once,
    and has proper Copy and Share buttons.

Fixed

  • Refreshing a subscription returns what the panel serves now. Responses went
    through the shared HTTP cache, so a panel or CDN that sent Cache-Control
    kept handing back the old node list and its old hosts. Subscriptions are now
    fetched without any cache, and what earlier builds cached is deleted at
    launch. A refresh that fails writes the reason to the log.
  • Ping no longer reads 1–2 ms on every server while TUN is on. The probes
    followed the default route into the tunnel and were answered by its own
    network stack on this Mac. They are now pinned to the physical interface, and
    with fake-IP DNS the server's real address is looked up off the tunnel.
  • In TUN mode, apps that use the system resolver are proxied properly when the
    DNS server is the router. The router sits on the LAN the tunnel leaves out, so
    every system lookup went to the router and the provider behind it instead of
    the core, and those apps got the provider's answers. Its address is now routed
    into the tunnel and its queries are handled by the core's DNS. This is one
    cause of "TUN does not proxy some apps"; if an app still bypasses the tunnel,
    please report which one.

Changed

  • The iOS app moved to its own repository,
    veil-ios, with its history.
    It still builds the shared Models and Core from here as a submodule.

  • iOS still runs only Xray. A fastest-node group runs as an Xray leastPing
    balancer, and a manual group routes to its chosen member. Some things Xray
    cannot do are left out of the config instead of failing it: per-app and
    inverted rules, rule sets, and DNS-over-TLS servers.

  • iOS traffic counters now include every server in a group, and servers given
    by IP are routed outside the tunnel so their ping is real.

  • On iOS, presets that bypass the LAN now keep private networks off the VPN
    entirely, instead of sending them through the tunnel to be routed direct.
    Printers, NAS boxes and the router stay reachable at full speed. Switching
    presets while connected re-applies the routes without dropping the VPN.

  • WireGuard servers from Xray JSON subscriptions are imported, and an IPv6
    WireGuard endpoint is written with brackets.

What's Changed

  • Redesign the website in monochrome by @faustyu1 in #19
  • Write routing port ranges as a:b so sing-box accepts them by @faustyu1 in #21
  • Bring the iOS app up to the desktop feature set on the Xray core by @faustyu1 in #20
  • Link the Android app from the README and point links at the org repository by @faustyu1 in #22
  • Release 1.12.0 by @faustyu1 in #23
  • Move the website to the veil-site repository by @faustyu1 in #24
  • Skip the live ping test when the cores are not fetched by @faustyu1 in #25

Full Changelog: v1.11.0...v1.12.0

Veil 1.11.0

Choose a tag to compare

@github-actions github-actions released this 10 Oct 22:34
7318800

Fixed

  • Reopening the window from the menu bar no longer tears down a running TUN
    connection. The start-up work — crash cleanup, auto-connect, login-item
    registration — ran again on every reopen, and the crash cleanup stopped the
    live core while the app went on showing "Connected".
  • The window no longer redraws its whole server list once a second while
    connected. The uptime clock is drawn by the system from the connection's
    start time; the app timer that drove it is gone.
  • In TUN mode the helper reads only the last 32 KB of the core's log instead of
    the whole file, and the app asks for it only while the log pane is open. The
    log was fetched every two seconds for as long as the tunnel was up, window
    or no window.
  • The helper's logs are capped at 4 MB while a tunnel runs, not only when it
    starts.
  • Disconnecting, recovering after sleep and re-applying the system proxy no
    longer freeze the window: networksetup and the helper's XPC calls run on a
    serial queue off the main thread, in the order they were asked for.
  • App Nap no longer throttles Veil and the cores it runs while a connection is
    up and the window is closed to the menu bar.
  • Subscriptions, community lists and the update check are refreshed in the
    background while Veil sits in the menu bar, not only at launch.
  • The temporary core configuration, which holds the node's credentials, is
    written owner-only and removed when the core stops. Every server switch used
    to leave one behind in the temp folder.
  • The log pane is an AppKit text view: new output is appended, a selection
    survives the next line, and it follows the end only when already there.

Changed

  • The Clash-compatible API (port 9090) is off by default. Its secret was random
    per launch and never shown, so nothing outside Veil could use it — it was a
    listening port for nothing. It stays on for anyone whose rules use
    clash_mode.
  • Xray bridges open a SOCKS port only, not an unused HTTP one beside it.
  • The control API binds 127.0.0.1 itself rather than the wildcard address
    restricted to the loopback interface.
  • The connection health check runs once a minute instead of every 30 seconds,
    re-checking 10 seconds after a miss, so a dead link is still caught in about
    70 seconds.
  • Helper protocol version 7: reinstall the helper after updating.

What's Changed

  • Release 1.11.0: stop draining the battery, keep TUN alive from the menu bar, close unused ports by @faustyu1 in #18

Full Changelog: v1.10.0...v1.11.0

Veil 1.10.0

Choose a tag to compare

@github-actions github-actions released this 22 Sep 14:52
7980e68

Added

  • A "Hide the Dock icon" setting under Settings › General › Window. Veil then
    runs from the menu bar alone — no Dock tile, no ⌘-Tab entry — and keeps
    running when the window is closed, whatever close-to-tray says, since the
    menu bar item is the only way back to it. The switch takes effect at once,
    without a relaunch.

Fixed

  • Credentials in a share link are percent-decoded once, not twice. A password
    containing %40 arrived as one containing @, and one ending in a bare %
    decoded to nothing and was dropped — in both cases the node authenticated as
    somebody else, or not at all. Applies to VLESS, Trojan, Hysteria2, TUIC,
    AnyTLS and WireGuard.
  • The builder percent-encodes : and @ inside a credential itself. Leaving
    that to URLComponents produced a link that split in a different place on
    macOS 26 than on 15, so an exported password containing either delimiter came
    back truncated.
  • A Hysteria2 link that carries its auth string in the query — auth,
    auth_str, auth-str or password — is read instead of being treated as a
    node with no password.
  • A node with no credential is named as such when it is checked, instead of
    being handed to the core. A Hysteria2 server answers an empty password with
    its masquerade page, which sing-box reports as "authentication failed, status
    code: 404" — a message about the far end for a link that never carried a
    password.

What's Changed

  • Hide the Dock icon on request, and read link credentials correctly by @faustyu1 in #17

Full Changelog: v1.9.0...v1.10.0

Veil 1.9.0

Choose a tag to compare

@github-actions github-actions released this 20 Sep 14:19

Added

  • WireGuard nodes keep their own AllowedIPs. The config editor wrote
    0.0.0.0/0, ::/0 over whatever the peer was handed out with, so a peer that
    only reaches one private network became a full tunnel every time its config
    was opened. The list is parsed from a wg-quick paste, a wireguard://
    link and an outbound JSON block, shown as it stands, and passed to the core.

Fixed

  • A rule that names its own addresses or domains now outranks the preset's LAN
    bypass. The bypass exists so that a rule about an application does not drag
    that application's LAN traffic through the tunnel; it was also outranking
    "send 172.16.4.10 through this peer", which is a sentence about the LAN and
    nothing else, and which therefore did nothing at all.
  • The TUN interface no longer routes around a private range a rule claims.
    route_exclude_address kept those packets off the tunnel entirely, so the
    core was never asked where they should go. The covering block opens up when a
    rule sends part of it somewhere other than direct; the rest of the block
    still goes straight out.
  • A WireGuard endpoint pasted or shown as outbound JSON is read back. The
    1.11+ shape states the remote in its peer rather than at the top level, so
    the editor refused its own output.
  • "Changes apply on the next connect or reconnect" is shown only when the
    routing actually differs from what the running core was started with, not
    whenever the panes are opened while connected.

Full Changelog: v1.8.0...v1.9.0

Veil 1.8.0

Choose a tag to compare

@github-actions github-actions released this 19 Sep 18:28
5b35522

Added

  • A Sources page, the second mode of the main window. It lists every source
    behind the server list and, for each one, what the last fetch actually
    returned: the format recognised, how many servers and panel-declared groups
    came out of it, when it ran, and the traffic and expiry the panel reports.
    The subscription URL is never drawn — its path is the access token — so it
    stays in the Keychain, with a "Copy subscription link" command for when it
    is needed.
  • Sources now say what they could not use. Entries a body carries that Veil
    cannot connect to — an outbound type it has no support for, a share link
    with an unknown scheme, a Mihomo YAML body — were dropped in silence, which
    is why a WireGuard peer could simply fail to appear. Each one is now counted
    by reason and shown on the Sources page.
  • Any server can be read as its own configuration: the wg-quick file for a
    WireGuard peer, the outbound JSON its core will run, or the share link. A
    server Veil owns can be edited in that form, and "Check" runs the text past
    the core that will execute it — sing-box check or xray run -test — so a
    typo is named where it is typed. A subscription's server is read-only, with
    "Duplicate and edit" to take a copy into Manual.
  • Tags, renaming, pinning and hiding for individual servers. These are yours,
    kept separately from what the panel sends, and they survive a refresh.
  • The list can be grouped by subscription, by tag or by country, or left flat,
    and filtered by tag, by country and by search. Servers can be dragged into
    whatever order suits, with "Reset manual order" to go back.
  • Subscriptions can be pinned and reordered, so the list opens on the one in
    use.
  • Automatic groups. A group can state what it wants — this source, that
    country, that tag, that protocol, that fragment of a name — instead of
    naming its members, and the answer is worked out again whenever the list
    changes. A group over a subscription of fifty nodes stays right when the
    provider adds the fifty-first; a hand-picked one never did. "Fastest of
    everything" builds the group most people want in one click, and a source's
    own menu offers the same over just that source.
  • Your own groups now appear in the server list, at the top, and can be
    connected to like any server. They were configurable but unreachable
    outside the routing rules, and there was nowhere to delete one; a group's
    own row now offers that, and opening the editor from it lands on the groups.
  • A preset says what it actually installs: the rules it puts before your own
    and the ones it puts after, each with its target and its matchers.
  • Settings are one window with a sidebar. Routing used to be a second window
    of its own, reached by a button inside a settings tab whose only content was
    that button; its five pages are now panes in the same list, each with an
    icon, and the Routing menu command opens them directly.
  • Settings that are not self-explanatory carry an "i" beside their name, with
    the explanation a click away instead of a paragraph under every row: what
    each tunnel mode really routes, what the TUN stack setting can break, what
    the ports and the log level are for, what auto-updating sources does, and
    what blocking ads and trackers matches.
  • Tags read out of a server's own name — the country, the protocol, a
    provider's own words like Premium or Trial — with a switch in Settings →
    General. Off by default: they are guesses about someone else's naming, and
    the country chips follow the same switch.
  • The Sources tab can be hidden once subscriptions are set up.
  • The log pane can be dragged to whatever height suits and remembers it, and
    it can be narrowed: a search box, a severity floor that understands both
    cores' spellings, and a count of how much is on screen against how much the
    core wrote. Copy takes what is shown rather than everything.
  • The control API reaches the rest of the app. It can now list the sources and
    what each fetch skipped, refresh them, read and write the labels, pins and
    renames on individual nodes, read the redacted log and diagnostics, and push
    an edit into a connection that is already up. Subscription URLs and the
    device identifier remain out of reach by design, and docs/agents.md is the
    written contract for whoever is driving it.

Changed

  • A refresh keeps the identity of servers that are still there. Every fetch
    used to mint new ids, which silently broke group membership, routing rules
    naming a server, and the record of which server was last selected. Servers
    are now matched on address, port, protocol and key, falling back to name.

Fixed

  • The control API no longer escapes the slashes in every path it prints, which
    made the schema it hands an assistant read as GET \/v1\/state.
  • A rule that sends a domain through a particular server or group now works
    in System Proxy mode. Turning the native sing-box inbound off — a TUN
    setting — also dropped that mode onto the single-server path, where there is
    one proxy outbound and every node- and group-specific target silently
    collapses onto it. System Proxy has no tunnel interface to own, so it now
    always builds the full profile. Where the collapse is still real, in TUN
    mode with the native inbound off, the rules editor says so instead of
    looking configured.
  • Groups a panel declared can be named by a rule. The target picker only
    offered your own groups, although the profile has always been able to build
    a panel's.
  • A routing rule naming a group with no members no longer breaks the profile.
    The group produces no outbound, so the rule named a tag the core had never
    heard of and sing-box refused to start. Such a rule now falls back to the
    default proxy, which is what it asked for.
  • The update download now reports how far it has got. The progress bar was
    wired to URLSession's task-specific delegate, which never delivers the
    byte counts for an async download, so it read Zero KB of 73.7 MB for the
    whole transfer and then jumped to the end. It now shows bytes, speed and
    time remaining as the file arrives.
  • An update that cannot be installed says so instead of quitting. Veil
    replaces the bundle it is running from, and when that bundle is read-only —
    a copy macOS made because it was launched from a quarantined archive, or a
    folder the account cannot write to — the swap was impossible and the app
    simply closed. Both cases are now checked before anything is unpacked, and
    the window explains what to move where.
  • An install that fails after Veil has quit is reported on the next launch.
    The swap runs from a detached script, which used to abort silently at the
    first error; it now rolls back to the working version, verifies the version
    it installed, and writes what happened to ~/Library/Logs/Veil/update.log.

What's Changed

  • Release 1.8.0: rework sources, tags, groups, routing, settings and the agent API by @faustyu1 in #16

Full Changelog: v1.7.0...v1.8.0

Veil 1.7.0

Choose a tag to compare

@github-actions github-actions released this 19 Sep 11:22

Added

  • Balancer groups a panel declares are now used as declared. A subscription
    that answers with a sing-box or Xray config states its grouping outright —
    a urltest or selector outbound, a routing.balancers entry — and Veil
    reads that instead of re-deriving one from the node names. Each group shows
    up in the list as a single entry you can connect to, with its members
    underneath.
  • An Intel build, Veil-x86_64.app.zip. Releases used to ship only the Apple
    Silicon archive, which Intel Macs refuse to open with "this application is
    not supported on this Mac". The updater now fetches the archive matching the
    Mac it runs on.
  • CONTRIBUTING.md, a Contributor Covenant CODE_OF_CONDUCT.md, and a
    CLAUDE.md recording the rules that are easy to get wrong — the helper's
    cdhash pin, the TUN stack, the localization table, the build SDK.

Changed

  • The name heuristic that merges NL - 1 and NL - 2 into one balancer now
    runs only for subscriptions that are a list of share links. Those carry no
    grouping at all, so a guess is all there is; a config document does carry
    one, and guessing over it replaced the provider's intent with whatever their
    node names happened to look like.
  • Veil is now licensed under the GNU Affero General Public License v3.0
    instead of MIT. The bundled cores keep their own licences and nothing in the
    app is paywalled; the change only requires that anyone who distributes a
    modified Veil, or runs one over a network, offers the source for it.
  • The README is rewritten around what Veil actually does, with the protocol
    matrix, the two tunnel modes and the security model up front, and a Russian
    translation in README.ru.md.

Removed

  • docs/PLAN.md. The roadmap had outlived the work it described; the
    CHANGELOG and the issue tracker say what is done and what is next.

What's Changed

  • Release 1.6.3: settings fixes and a stale-helper warning by @faustyu1 in #11
  • Release 1.7.0: use the balancer groups a panel declares by @faustyu1 in #13
  • Rewrite the README, add the contributor docs, relicense under AGPLv3 by @faustyu1 in #14
  • Show an English window in the English README by @faustyu1 in #15

Full Changelog: v1.6.2...v1.7.0