[ v4.0.7 Wishlist ] share your enhancement suggestions ✨

[axpnet]

Welcome to the rolling wishlist for v4.0.7 and the v4.x releases that follow. This thread collects enhancement suggestions from the AeroFTP community and triages them into the upcoming v4.x tags.

The previous wishlist (#335) covered the v4.0.6 cycle, a small consolidation release: the AEROVAULT3 vault engine and its Reed-Solomon error correction moved into the published aerovault crate so the app, the CLI and any third-party Rust project share one audited implementation, alongside CLI benchmark polish and an SFTP profile-edit crash fix. With v4.0.6 out, we close that thread and open this one.

---

How to contribute

Please post one suggestion per comment so each one can be reacted to and discussed independently. A good suggestion includes:

• What: a short description of the enhancement
• Why: the use case or problem it solves
• Where (optional): which area of the app, for example IntroHub, file manager, AeroVault, AeroCrypt, AeroSync, AeroAgent, AeroFile, CLI, MCP, mobile, providers, docs

Reactions on individual comments are welcome and count as "I want this too" signals. Free-form replies discussing trade-offs are also welcome under the same comment.

Scope

In scope:

• UI/UX improvements, small features, provider polish, CLI/MCP flag additions, accessibility, performance tweaks, anything that fits comfortably in a release window
• Documentation gaps and improvements (docs.aeroftp.app, README, in-app help)
• Workflow ergonomics that surface during real use

Out of scope:

• Bug reports: please open a dedicated Issue using the bug template instead
• Large new modules, multi-day architectural changes and paid integrations: those are planned separately and are not triaged from this thread

Carry-over from #335 and #270

Items raised in the previous wishlists (#335, #270) that did not make a tag and are still open are eligible for triage here. The rule:

• If your earlier suggestion was acknowledged but never shipped, please post it again as a fresh comment here with a one-line originally from <link> trailer. That keeps reactions per item meaningful in this cycle and avoids carrying stale assumptions over.
• Items already shipped are considered done and do not need to be re-raised. The previous wishlist threads and the 4.0.x tracker list what landed.

Triage

Before cutting each v4.x tag we will:

• Mark the comments included in the upcoming release
• Mark the ones deferred to a later milestone
• Keep the 4.0.x tracker updated with what shipped

Reactions on comments inform priority. Tie-breaks favor items that improve daily-driver ergonomics for tester profiles (existing community testers, documentation drilldown, error message clarity).

Thanks in advance for the input.

[axpnet]

🟢 v4.0.7 is out (2026-06-18).

Honest note: we are updating this thread late. v4.0.7 already shipped and we are already deep into v4.0.8, so this is housekeeping catching up rather than a same-day wrap.

The v4.0.7 headline was an AeroVault security pass. An independent dual blind audit (Claude Opus 4.8 and Codex GPT-5), full remediation and a two-round adversarial controaudit closed every finding at grade A (1 High, 1 Medium, 3 Low, 4 Info, 0 Critical, 0 open). In the same pass the error-correction engine converged onto a single audited implementation in the published aerovault crate (0.6.2), so the desktop app, the CLI and any third-party Rust project share one engine instead of forked copies. Alongside it: AeroVault hardening (no leftover temp or lock after an interrupted seal, a reparse-point escape fix on extract, an --expect-sha256 authenticity anchor for repair, and a forged-extension-directory rejection at open), and an IntroHub My Servers layout pass. Full list in the 4.0.x tracker.

This thread did not collect open suggestions of its own. With v4.0.8 already near release, we are opening a combined v4.0.8 - v4.0.9 wishlist for the next cycle: #347

Carry-overs from #270, #335 and #339 are eligible there: re-post as a fresh comment with an originally from <link> trailer. Closing this one, see you in the new thread.