Skip to content

v2.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 20 Aug 03:15
v2.0.0
543cc72

MuxLayer 2.0.0 — Brand migration with automatic legacy data adoption

MuxLayer is now the primary product identity: the local model control layer for coding agents.

Highlights / 重点

  • MuxLayer brand migration / 品牌迁移 — README, documentation, website, app title, GitHub metadata, and release presentation now use MuxLayer.
  • Automatic legacy data adoption / 老用户自动接管 — Existing desktop installations keep the legacy updater identity and application data directory so upgrades do not lose databases or tokens.
  • Headless data compatibility / 无界面模式兼容 — New CLI installations use ~/.muxlayer; an existing ~/.agentgate database or token is detected and reused automatically.
  • Environment aliases / 环境变量别名 — MUXLAYER_DB_PATH and MUXLAYER_TOKEN are preferred; AGENTGATE_DB_PATH and AGENTGATE_TOKEN remain supported.
  • Rollback-safe transition / 可回滚迁移 — No old directory is deleted, moved, or overwritten in this release.
  • Canonical brand surface / 正式品牌入口 — The MuxLayer logo, guide filenames, comparison URLs, sitemap, and SEO pages are now canonical; old AgentGate guide URLs redirect to their MuxLayer equivalents.
  • Official Homebrew cask / 正式 Homebrew 安装入口 — New installations use brew install --cask dengmengmian/tap/muxlayer; the legacy agentgate cask remains upgrade-compatible.
  • Native app icon refresh / 原生应用图标更新 — macOS, Windows, Linux, Android, and iOS package assets now use the MuxLayer icon.
  • Verified provider catalog / 已验证供应商目录 — Product surfaces consistently describe the built-in catalog as supporting 25+ model providers.

The legacy technical identifiers remain intentionally compatible for this release cycle: agentgate-serve, the agentgate virtual model, the updater bundle ID, and legacy data paths and environment variables. The agentgate Homebrew cask remains available as an upgrade-compatible alias while muxlayer is the primary cask.

Assets 19
Loading