Skip to content

Multi-AI Terminal v0.2.6

Choose a tag to compare

View all tags
@github-actions github-actions released this 23 Jul 00:11
v0.2.6
cd9b1c3

Multi-AI Terminal v0.2.6

English

Managed runtimes go live (BAT-aligned)

The runtime foundation from v0.2.5 is now wired end-to-end. Installing Claude Code or Codex from Provider Setup performs a pinned, hash-verified managed install into MAT's own data directory instead of touching your system — and from then on the adapters launch that managed binary (an explicit env override still wins, and platforms without a catalog entry keep the existing PATH discovery). The setup dialog shows the live runtime state (managed / external / missing / broken) plus the pinned version, fed by new /api/runtimes endpoints and runtime:changed events. Installs and removals run in the background behind a single mutation lock, so a concurrent request gets an honest 409 naming the operation in flight instead of a race; removal only ever deletes MAT's own <dataDir>/runtimes/ tree and stays available even on platforms that can't install. Grok and Antigravity keep their existing setup recipes for now — they join the managed model in an upcoming release.

Desktop first-run auto-install

The desktop app quietly provisions the pinned runtimes (Codex, then Claude Code — only the ones that are missing and installable) shortly after first launch, so a fresh machine is ready to run without a manual install step. This is gated behind an environment flag that only the desktop shell sets: server-only and agent-lane usage never installs anything on its own.

Under the hood

  • Managed Codex children get MAT's isolated helper directory prepended to their PATH and the bundled Node appended — appended, never prepended, so it can't shadow whichever binary the resolver actually picked.
  • The runtime catalog ships beside the bundled server with candidate-path loading, so the desktop build resolves it without a repo checkout.
  • Three-way accepted as usual: codex implemented, the gatekeeper caught a child-PATH shadowing regression and an install/clear dedupe join before review, grok 4.5 found three more (all fixed with regression tests). 30 runtime/API tests; full suite, agent integration, and browser smoke green.

繁體中文

受管 Runtime 正式上線(對齊 BAT)

v0.2.5 打好的 runtime 地基這版全線接通。在 Provider Setup 安裝 Claude Code 或 Codex,現在是釘版、雜湊驗證的受管安裝,裝進 MAT 自己的資料目錄、完全不動你的系統——此後 adapters 一律啟動這份受管執行檔(明確的環境變數覆寫仍優先;catalog 未涵蓋的平台維持既有 PATH 探索)。設定視窗會顯示即時 runtime 狀態(受管/外部/未安裝/損壞)與釘定版本,由新的 /api/runtimes 端點與 runtime:changed 事件驅動。安裝與移除都在背景執行、由單一互斥鎖序列化——併發請求會收到誠實的 409 並指名進行中的操作,而不是彼此競速;移除永遠只刪 MAT 自己的 <dataDir>/runtimes/ 樹,且在無法安裝的平台上仍然可用。Grok 與 Antigravity 暫時維持既有安裝方式,之後的版本再納入受管模型。

桌面版首次啟動自動安裝

桌面版會在首次啟動後不久,靜靜地把釘版 runtimes 裝好(先 Codex、後 Claude Code——只裝「缺少且可安裝」的),新機器不需手動安裝就能直接開跑。這個行為由只有桌面殼層會設定的環境旗標把關:純伺服器與 agent 工作流永遠不會自行安裝任何東西。

底層細節

  • 受管 Codex 子行程的 PATH:MAT 的隔離 helper 目錄放最前面、內建 Node 附加在最後面——只附加、絕不前置,才不會遮蔽 resolver 實際選中的那個執行檔。
  • Runtime catalog 隨打包後的伺服器一起出貨,以候選路徑載入,桌面版不需要 repo checkout 也能解析。
  • 照例三方驗收:codex 實作;守門人在送審前先抓到子行程 PATH 遮蔽回歸與 install/clear 去重合流缺陷;grok 4.5 再找出三條(全數修正並補回歸測試)。30 條 runtime/API 測試;完整測試套件、agent 整合測試、瀏覽器 smoke 全綠。
Assets 11
Loading