OMXTerm 0.22.0

OMXTerm 0.22.0

What's new

• Split panes: run independent shells within a tab, navigate with the keyboard, drag dividers and equalize pane sizes. A thin top marker identifies the focused pane. New panes can start in the local directory reported by your shell.
• Find: search the focused pane's scrollback and visible screen, with live highlighting and next/previous matches.
• Settings: edit common preferences in the app, or use the Config File page to edit config.json, with validation and protection against conflicting external edits.
• English and Brazilian Portuguese: explicitly choose English (United States) or Português (Brasil); interface labels update across open windows without restarting sessions.
• Safer snippet choices: preview text before inserting or running it, with explicit action labels and a captured terminal target. The Snippets panel is resizable and keyboard accessible; YAML loading is bounded and validated.
• Improve links wrapping beside wide characters, preserve configured ANSI colors on palette reset, and tighten focus/input handling around dialogs and previews.
• Refresh the compact About dialog and contributor credits; update Electron to 43.8.1.

Configuration, theme and snippet schemas remain version 1. Interface language defaults to English and is not inferred from your OS. Settings writes changes to config.json; font family and line-height changes apply to new terminal surfaces, with a restart needed for existing ones. Shortcuts, transparency, blur and snippets remain file-edited; there is no new shortcut editor or export feature.

Downloads and SHA-256

Linux x64 AppImage downloads are new. Windows x64 remains available alongside macOS ARM64, Linux ARM64 and Windows ARM64. Both x64 packages have BUILD-ONLY qualification, detailed below—not desktop, installer or GPU qualification.

Each payload has a matching .sha256 asset: twelve assets total, including one shared Linux helper/checksum pair. Verify checksums before opening an installer or running the helper. Use -arm64 files for ARM64 and -x64 files for Intel/AMD systems. On Linux, make the verified AppImage/helper executable with chmod +x as needed.

File	Bytes	SHA-256
OMXTerm-0.22.0-arm64.dmg	129523317	24f111af8a92a154176975febb4788024e1330419d56bcb7f3aa55638d001eb6
OMXTerm-0.22.0-arm64.AppImage	127988539	8dc3342540388f3ec0652eb928c0da584f640a58eb20242e1b9aab1b5633023d
OMXTerm-0.22.0-x64.AppImage	127830882	150ad9a0ca834137574bfde9009df20cf6baba724c8bc76b224d29fc2f2ba927
linux_install.sh	12245	8fd28b00d2854325dae7f5cc988c8a44e9d77157382f1a79f989bd0115d834c4
OMXTerm-0.22.0-arm64.exe	156513630	1f70a9242dd0d0a1bdd2578444fc4f9a1e42f52550d107050309edf5113e4706
OMXTerm-0.22.0-x64.exe	158243752	f92a9ebbaf27c29ccfd273e9bbb142aacfe2f9c74f259ef8aa3f065be9564cb2

Verification and limits

Target	Evidence for these exact preserved packages
macOS ARM64	Maintainer-reported full portable gate and package build; hdiutil verify passed on the preserved DMG. The maintainer installed that DMG and reports successful manual daily use. This is not automated exact-DMG mounted-app verification.
Windows ARM64	Corrected native Windows 11 ARM64 verification passed for the exact NSIS: installed payload comparison, installed startup/PTY output and owned uninstall/cache cleanup. The earlier observer-induced failure is retained, not counted as a pass.
Linux ARM64	Full exact-AppImage verification passed with the corrected verifier (#683/#689), including isolated helper installation, direct/FUSE and extract-and-run startup, real PTY output and clean shutdown. Direct main and propagation-checked wrapper each returned 0/no signal; no new cores or owned process/mount leftovers. The earlier verifier-induced failure remains recorded separately.
Windows x64	Native Windows Server 2025 x64 hosted build, headless checks, unpacked content/architecture inspection and packaged Electron Run-as-Node/addon load. No real ConPTY spawn, NSIS execution, or proof that NSIS payload equals the inspected unpacked tree.
Linux x64	Native Ubuntu 22.04 x64 hosted build; exact AppImage extraction/content/architecture inspection and packaged Electron/addon checks, including real headless PTY output, exit and resize, invalid-FD handling, and missing-executable failure distinguished from successful exit 1. No desktop, FUSE launch or helper installation.

Both x64 jobs passed locked install, formatting, lint, typecheck, headless unit tests, build, packaging and checksums. Windows run: 2661 tests passed, 53 skipped. Linux run: 2715 tests passed. Actual packaged runtime evidence records Electron 43.8.1 / Chromium 150.0.7871.250 / Node 24.22.0 on each x64 target—not merely the locked dependency version.

Build-only does not establish desktop startup, GPU/rendering, ordinary-user OS integration, installation or upgrade compatibility. Windows 11 and SmartScreen/UAC were not qualified by the Windows x64 Server run; administrator symlink checks do not establish ordinary-user Developer Mode behavior. Linux x64 was checked on a glibc 2.35 runner; this is an observed environment, not a minimum-version or broad distribution compatibility guarantee. Do not infer its requirements from the ARM64 package.

Windows ARM64 packaged metadata was verified as 0.22.0; its production PTY probe checks that TERM_PROGRAM_VERSION is nonempty, not exact equality. No new full behavioral-suite pass is claimed for the Windows packages.

First launch and graphics

• macOS: ad-hoc signed, without Apple Developer ID signing or notarization. After verifying the checksum and deciding to trust the download, use System Settings → Privacy & Security → Open Anyway if Gatekeeper blocks it.
• Windows: unsigned. After verifying the checksum and deciding to trust the download, choose More info → Run anyway if SmartScreen offers that option. Installer verification does not establish first-download UI behavior.
• Linux: Chromium's sandbox remains intentionally disabled (ADR 0024). Existing opt-in linux_install.sh install --compatibility <verified-AppImage> enables Mesa software graphics and ignores the GPU blocklist; use it only for graphics failures, with possible performance/stability costs. No automatic SwiftShader/WebGL fallback is included; that work is deferred to #686.

Source provenance

These are preserved 0.22.0 builds, not renamed older binaries. They were built from different commits:

• macOS ARM64: ba6deecba0d8c70a0b8e36f3c9d6d239311d3f13.
• Windows ARM64, Windows x64 and Linux ARM64: a96dccbe5935a1fe53bfa7ba377cdeb48dd17300.
• Linux x64: 2327043305e7101e45fb572727a8994d3fbf15c3 (Linux artifact-name normalization, #684).
• Final release/tag source: 933156e929aa890cf3853aa52d2c52aafd8c7c0e. Source-input comparison confirms equivalent platform build inputs for these preserved packages. The final #683/#689 changes affect verification tooling, external test fixtures and documentation, not packaged application inputs. Equivalent inputs do not mean identical build commits or reproducible binary bytes.

Full changelog: v0.21.0...v0.22.0