Skip to content

TermDock v1.5.2

Choose a tag to compare

@HCYT HCYT released this 04 Mar 09:19

Downloads (macOS Only)

macOS

  • Termdock-1.5.2.dmg - Intel Mac installer
  • Termdock-1.5.2-arm64.dmg - Apple Silicon (M) installer

💡 Other Platforms

Windows and Linux versions are planned for future releases. Stay tuned!

What's New

English

  • Session Restore — Automatically restores terminal sessions after app restart, with serialization safeguards and per-session error isolation
  • PTY Process Isolation — Injects isolation at the PtySession level via WorkerPtyProxy, running each PTY in a dedicated utilityProcess
  • Unified TermdockPaths Management — Consolidates all ‎.termdock paths into a single TermdockPaths source, including workspace migration
  • Git Changes Badge — UI shows a badge with the number of git changes
  • Terminal Shift+Enter Newline — Terminal now supports inserting a new line with Shift+Enter Refactor
  • AST IPC V2 Facade — Consolidates AST IPC into a unified V2 facade with a type-safe interface Bug Fixes
  • Bind AST API to 127.0.0.1 — Changes AST API listen address from ‎localhost to ‎127.0.0.1 to avoid DNS resolution issues
  • Memory Skill Script Path Resolution — Fixes incorrect skill script path resolution

繁體中文

  • Session Restore — 應用重啟後自動恢復終端 session,包含序列化保護與 per-session 錯誤隔離
  • PTY Process Isolation — 透過 WorkerPtyProxy 在 PtySession 層級注入隔離,PTY 運行於獨立 utilityProcess
  • TermdockPaths 統一路徑管理 — 將所有 .termdock 路徑收斂至 TermdockPaths 單一來源,含 workspace migration
  • Git Changes Badge — UI 顯示 git 變更數量標記
  • Terminal Shift+Enter 換行 — 終端支援 Shift+Enter 插入新行
  • AST IPC V2 Facade — 整合 AST IPC 為統一的 V2 facade,type-safe interface
  • AST API 綁定 127.0.0.1 — 修正 AST API 監聽位址從 localhost 改為 127.0.0.1,避免 DNS 解析問題
  • Memory skill 腳本路徑解析 — 修正 skill script 路徑錯誤

Installation Instructions

  1. Download the appropriate DMG file for your Mac
  2. Open the DMG and drag Termdock to Applications folder
  3. First launch may require allowing the app in System Preferences > Security & Privacy

Report Issues

Found a bug? Please report it in our Issues section.