Pulsar 1.133 code editor improves terminal integration, file watching, and Electron 32 upgrade

The community-maintained Pulsar code editor, which continues development of the former Atom editor, has released version 1.133 after an extended development cycle. This release focuses on three areas: deeper terminal integration with clickable OSC 8 hyperlinks, working-directory tracking across Bash/Zsh/Fish/PowerShell, and clickable file paths in terminal output; performance fixes for a syntax-highlighting regression that caused editing pauses on large files; and a redesigned file-watching system that can run in a separate process using either the existing nsfw backend or the VS Code-compatible @parcel/watcher library.

The editor also upgrades its underlying platform to Electron 32.3.3, incorporating newer Chromium and Node.js components. This release marks the final version to support macOS 10.15 Catalina, with Pulsar 1.134 planned to move to Electron 37 and add native Wayland support on Linux without requiring command-line flags. Additional changes include improved syntax highlighting for Python template strings, Perl class syntax, and C#, plus updates to the Package Manager's Node.js runtime.

Terminal, performance, and architecture changes in Pulsar 1.133

• Integrated terminal enhancements: The terminal now supports OSC 8 hyperlinks with hover previews, working-directory tracking through shell integration with Bash, Zsh, Fish, and PowerShell, and clickable absolute/relative file paths in command output including linter reports; Ctrl+Shift+C/V copy-paste shortcuts now work on Linux and Windows.
• File-watching architecture redesign: A new out-of-process file-watching implementation runs monitoring outside Electron's renderer process, reducing crash risk; users can choose between the default nsfw backend and @parcel/watcher (used by VS Code), with improved handling of ignored files and complex filesystem scenarios, switchable without restart.
• Large-file performance fix: A syntax-highlighting regression introduced in Pulsar 1.127 that caused noticeable pauses during large-file editing has been resolved.
• Electron and platform upgrade: The editor moves to Electron 32.3.3 with updated Chromium and Node.js; this is the final release supporting macOS 10.15 Catalina, and Pulsar 1.134 will upgrade to Electron 37 with native Wayland support on Linux.
• Deleted file handling and package manager: Files deleted externally now have a distinct editor state separate from modified files, with an optional setting to suppress confirmation prompts when closing deleted files without unsaved changes; the Pulsar Package Manager updates to Node.js 20.18.1 with bug and security fixes.

Why it matters

For developers who preferred Atom's extensible architecture before GitHub discontinued it, Pulsar's continued maintenance provides a viable community-driven alternative with modern platform updates. The redesigned file-watching architecture directly addresses Electron applications' historical instability with filesystem monitoring, while the upcoming native Wayland support in 1.134 removes a friction point for Linux users on modern compositors. The terminal improvements, particularly OSC 8 hyperlink support and shell integration, narrow the feature gap with VS Code's terminal experience for users committed to the Pulsar ecosystem.