Noureddine RAMDI / Neon Vision Editor: A Minimalist Native Swift Editor with Sandbox-Friendly CLI Integration

Created Sat, 23 May 2026 20:41:14 +0000 Modified Sat, 23 May 2026 20:41:27 +0000
932 Words
github-stars swift macos sandboxing cli swiftui apple

h3pdesign/Neon-Vision-Editor

Neon Vision Editor takes a different approach to native Apple platform code editors by prioritizing minimalism and speed over the complexity of a full IDE. What stands out is its optional command-line helper that respects macOS sandboxing rules by routing file open requests through Launch Services rather than accessing files directly. This architectural choice offers a practical way to integrate terminal workflows without compromising sandbox security.

What Neon Vision Editor offers and how it’s built

Neon Vision Editor is a native Swift editor targeting macOS 26 (Tahoe), iOS, and iPadOS, with a focus on Apple Silicon. It’s built using Swift and SwiftUI, leveraging the latest Apple platform capabilities to deliver a lightweight but functional editing experience.

The app features syntax highlighting, a scroll-synced code minimap that provides an overview of the source code alongside the editor, and an integrated sidebar terminal for quick command-line access within the app. It also supports Markdown preview with themed rendering and a project sidebar that includes a table of contents (TOC) for easier navigation.

Distribution is versatile, with releases available through GitHub, the Mac App Store, and TestFlight. Installation options include a curl script for direct installs, Homebrew cask formulas, or building from source.

Architecturally, the editor is designed to respect macOS sandboxing constraints. This means it handles file access with user consent and uses security-scoped bookmarks to maintain sandbox compliance, avoiding full disk access or elevated permissions.

The sandbox-respecting CLI helper as a distinctive design

A key strength of Neon Vision Editor is its optional nve command-line helper. Unlike traditional CLI helpers that might directly read or write files, nve delegates all file operations to the GUI app by invoking macOS Launch Services through the standard /usr/bin/open command. This means nve never accesses file contents on its own, which avoids sandbox violations.

This design is clever because macOS sandbox rules restrict direct file access for apps distributed via the Mac App Store. By routing through Launch Services, the nve helper can open files within the sandboxed app environment, where the user has granted appropriate permissions.

The helper is user-installed and linked in the user’s shell environment on demand, so it doesn’t require admin rights or background daemons. This lowers the security and permission footprint, sidestepping common pitfalls of CLI integration for sandboxed apps.

Tradeoffs include added complexity in the CLI helper design, and potentially some latency or user experience quirks compared to native CLI tools that have direct file access. However, for users prioritizing security and compliance on macOS, this approach is a practical middle ground.

On the code quality side, the project has focused recent releases (v0.7.x) on UI polish, fixing scroll synchronization issues in the minimap, and improving performance with large files across all supported Apple platforms. The codebase is modern Swift with SwiftUI, which means it should be approachable and maintainable for Swift developers.

Quick start with Neon Vision Editor

The repository provides multiple straightforward installation methods:

Quick install with curl

curl -fsSL https://raw.githubusercontent.com/h3pdesign/Neon-Vision-Editor/main/scripts/install.sh | sh

For user-local install without admin password prompts:

curl -fsSL https://raw.githubusercontent.com/h3pdesign/Neon-Vision-Editor/main/scripts/install.sh | sh -s -- --appdir "$HOME/Applications"

Install via Homebrew

brew tap h3pdesign/tap
brew install --cask neon-vision-editor

To avoid admin password prompts by installing to user Applications folder:

brew install --cask --appdir="$HOME/Applications" neon-vision-editor

Installing the command line helper

The nve CLI helper is optional and installed separately:

  1. Open the app’s Settings > Support panel.
  2. Copy the provided command line install command.
  3. Run it in your terminal to link the bundled nve helper in your $HOME/bin.

Example usage:

nve README.md
nve --wait --new-window "Neon Vision Editor/UI/ContentView.swift"
nve --line 42 "Neon Vision Editor/UI/ContentView.swift"

Development builds can link the helper script from the repo directly:

ln -sf "$PWD/scripts/nve" "$HOME/.local/bin/nve"

Handling macOS Gatekeeper

If macOS blocks the app on first launch (common on macOS 26 Tahoe), go to System Settings > Privacy & Security, find the blocked app message, and click Open Anyway.

Verdict

Neon Vision Editor is a solid choice if you want a minimalist native Swift editor that respects macOS sandboxing and integrates cleanly with terminal workflows via its unique CLI helper. It’s especially relevant for developers on Apple Silicon using macOS 26 or later who want a lightweight editing experience without full IDE overhead.

The tradeoff is that it won’t replace heavyweight IDEs or editors with extensive plugin ecosystems. Its sandbox-friendly CLI helper design adds complexity but is a pragmatic solution for Mac App Store distribution and security compliance.

If you value sandbox compliance, minimal permissions, and native Apple platform integration, Neon Vision Editor is worth exploring. The provided installation paths and the well-thought-out CLI helper make it accessible and practical for real-world use.

→ GitHub Repo: h3pdesign/Neon-Vision-Editor ⭐ 266 · Swift