winTerm 1.3.0

winTerm 1.3.0

This is the new stable release. GitHub Latest now points here, and
/releases/latest resolves to v1.3.0. The build is the field-tested
v1.3.0-beta3 promoted to the stable channel with stable version metadata;
no code changed between beta3 and this release.

winTerm 1.3.0 is the Command Timeline release: every pane gets a
trustworthy, in-memory list of the commands it has run, built exclusively
from OSC 133 shell integration — winTerm never guesses where a prompt or
output begins.

Command Timeline

Open it with Ctrl+Tab, or with the thin auto-hiding handle on the
terminal's left edge; click the terminal, press Escape, or press
Ctrl+Tab again to close it.

• Per-pane history. Each pane keeps its own list. cmd.exe — which
  does not report command boundaries — shows Command timeline unavailable rather than untrustworthy results.
• Works out of the box. A profile whose commandline is a bare
  powershell.exe or pwsh.exe (optionally with -NoLogo/-NoExit)
  automatically imports the packaged winTerm.Shell integration module at
  startup. Any customized commandline launches unchanged; the per-profile
  setting "shellIntegration.autoInject": false turns the rewrite off.
• Load without executing. Enter or a single click puts the selected
  command on the input line and stops there. No carriage return is ever
  sent, the clipboard is never read, and input broadcast never forwards
  the injected text.
• Search, copy, jump. Literal case-insensitive filtering over the
  pane's history, copy command or output, and jump-to-output that scrolls
  the buffer to where the command ran.
• Trustworthy status. ✓ Succeeded, ✕ Failed with the real exit code,
  or Running — never a guess. Commands without full shell integration show
  an explained ? Unknown instead of a fabricated result.
• Bounded by design. In-memory only, with a configurable bounded
  history; no persistent storage, no output cache, and no telemetry.

Visual Progress refinements

Three alphas and three betas of field testing hardened the v1.2.0 Visual
Progress system. The most visible fix: any command without a real progress
source — Alternate Screen TUIs (k9s, vim, top), development servers
(FastAPI/uvicorn, Spring Boot, Node.js), tail -f,
kubectl port-forward — now shows a single bounded launch traversal
instead of an endless rainbow animation, while explicit OSC 9;4 progress
and recognized CLI providers keep their full presentations.

Everything in v1.2.0 is included

Pane splitting and border-drag resizing with snap points, Balance Panes,
resize undo/redo, the winTerm dark shell, per-pane Visual Progress,
Workspaces, themes, private fonts, diagnostics, portable mode, and the
independent %LOCALAPPDATA%\winTerm data root all ship unchanged.

Downloads

• winTerm-1.3.0-setup-x64.exe — current-user or all-users installation.
• winTerm-1.3.0-portable-x64.zip — extract and run without installation
  (creates portable.marker alongside the executable).
• SHA256SUMS.txt — checksums for both application assets; verify before
  running.

Upgrading from v1.2.0 or any v1.3.0 prerelease installs over the existing
installation and keeps settings, themes, workspaces, and snapshots under
%LOCALAPPDATA%\winTerm (or the adjacent data directory in portable
mode).

Requires Windows 11 x64. winTerm is an independent open-source project
based on Microsoft Terminal source code; it is not a Microsoft product and
is not affiliated with or endorsed by Microsoft.

Signing

The Setup EXE is not Authenticode-signed. Windows may display Unknown Publisher or a SmartScreen warning; verify the downloaded file against SHA256SUMS.txt before running it.

Policies

• Code signing policy
• Privacy policy