| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| Terminay-Mac-2.5.0-Installer.dmg | 2026-08-05 | 185.8 MB | |
| Terminay-Mac-2.5.0-Installer.dmg.sha256 | 2026-08-05 | 99 Bytes | |
| Terminay-Linux-2.5.0.AppImage | 2026-08-05 | 210.7 MB | |
| Terminay-Linux-2.5.0.AppImage.sha256 | 2026-08-05 | 96 Bytes | |
| terminay-server-2.5.0.tgz | 2026-08-05 | 448.7 kB | |
| terminay-server-2.5.0.tgz.sha256 | 2026-08-05 | 92 Bytes | |
| terminay-server-2.5.0.tgz.sig | 2026-08-05 | 64 Bytes | |
| README.md | 2026-08-05 | 2.9 kB | |
| v2.5.0 source code.tar.gz | 2026-08-05 | 2.5 MB | |
| v2.5.0 source code.zip | 2026-08-05 | 3.3 MB | |
| Totals: 10 Items | 402.7 MB | 0 | |
Terminay v2.5.0 introduces local desktop diagnostics, modernizes agent tracking with journal-backed drivers, and resolves stability issues affecting WebRTC peer loading, git worktrees, and file viewing.
Local Desktop Diagnostics
Desktop now continuously records a bounded, local diagnostic history that persists across launches without requiring developer tools or terminal access. The 24-hour rolling log captures application lifecycle events, renderer stability, and failure classification.
Diagnostics Scope and Data Safety
- Logs record startup milestones, window events, renderer crashes, unresponsive transitions, and embedded server failures
- Diagnostic artifacts never include terminal content, credentials, or project data; only component failures and lifecycle transitions are captured
- Records are stored locally in the platform log directory and are never uploaded automatically
- A new launch marker distinguishes clean exits from interrupted sessions
Diagnostics Access and Management
- Diagnostics are readable from the application menu, accessible without launching from a terminal
- History uses UTF-8 JSON Lines so each entry is independently parseable and filterable
- Native crash dumps remain as opaque Crashpad artifacts; readable logs exclude them for security
- Diagnostics can be cleared from the UI without affecting future recording
Agent Status and Terminal Activity
Agent tracking shifted from managed hooks to journal-backed rollout drivers, establishing process-bound authoritative journals as the sole source of agent operational state.
Journal-Backed Agent Authority
- Recognized Codex sessions produce canonical agent events through process-bound provider journals
- Structured terminal signals and raw output remain fallback sources for uninstrumented shells and build tools
- Once a terminal has an authoritative agent entry, spinner frames and notification sequences do not alter the agent's canonical state
Fixes and Stability
Git Worktrees and File Viewing
- Stale worktree registrations are now removed automatically when worktrees are deleted or pruned
- Files opened from linked worktrees now resolve correctly through the file explorer
- File viewer now surfaces initial load failures with clear error messaging instead of silent hangs
WebRTC and Dependencies
- WebRTC peer load cleanup probes are stabilized to prevent flaky timeout behavior
- Secure Werift transitive dependency graph is now pinned to prevent vulnerability regressions
Release Assets
- macOS installer: https://github.com/markwylde/terminay/releases/download/v2.5.0/Terminay-Mac-2.5.0-Installer.dmg
- Linux AppImage: https://github.com/markwylde/terminay/releases/download/v2.5.0/Terminay-Linux-2.5.0.AppImage
- Standalone server: https://github.com/markwylde/terminay/releases/download/v2.5.0/terminay-server-2.5.0.tgz