[ v4.1.0 Wishlist ] share your enhancement suggestions ✨

[axpnet]

Welcome to the rolling wishlist for v4.1.0. This thread collects enhancement suggestions from the AeroFTP community and triages them into the v4.1.0 release window.

Closing v4.0.9, opening v4.1.0

🟢 v4.0.9 is released (release notes), so this same thread rolls forward and opens to v4.1.0 rather than starting a fresh one.

The v4.0.9 headline was the AeroVault / AeroMount pass for unlocked vaults: a unified Compressor-style modal with a .aerozip Zip lane, plus read-only mounting and one-shot Save all... of an unlocked Cryptomator vault / .aerovault / .aerozip. Alongside it shipped the interactive aeroftp groups and aeroftp users CLI sections, rclone export expanded to the cloud providers (Filen, Google Drive, Dropbox, OneDrive, Box, pCloud, Yandex, OpenDrive, B2, Jottacloud), the provider catalog free/paid rework with a "Free + card" tier, and a consistent password-create UX. The full list with commits and refs is in the 4.0.9 tracker (#349).

The two ideas raised here last cycle (systematic provider determinism tests, and a single pre-release smoke entrypoint) did not make the v4.0.9 cut and are carried into the v4.1.0 tracker (#361) for triage. Items already shipped are done and do not need to be re-raised here.

---

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 earlier wishlists (#339, #335, #270)

Items raised in the previous wishlists 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.9 tracker (#349) list what landed.

Triage

Before cutting the v4.1.0 tag we will:

• Mark the comments included in the release
• Mark the ones deferred to a later milestone
• Keep the release tracker updated with what shipped (v4.0.9 is tracked in #349; the v4.1.0 tracker is #361)

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]

What: Systematic deterministic (offline) tests for the storage providers that currently have unit coverage only. For each such provider, pin (a) the directory listing and stat parser against a captured real response, and (b) the HTTP-status-to-error mapping (401/403/404/409/429/5xx) with the correct retryable flag.

Why: A change on a provider's side or in a third-party dependency (response shape, a new status code, a WAF quirk) should be caught by a failing test rather than by a user. This is already the pattern on the freshest fixes; the ask is to make it systematic across the long tail.

Where: providers (backend), reflected in the Testing & Verification matrix.

Legend: 🟢 pattern already applied · 🟡 pending (this request).

Already applied as examples: WebDAV 404/409 upload mapping 🟢, OpenDrive size-limit error 🟢.

Providers in scope (currently unit-only):

Provider	Status
Azure Blob	🟡
OpenStack Swift	🟡
Koofr	🟡
Yandex Disk	🟡
kDrive	🟡
Zoho WorkDrive	🟡
Jottacloud	🟡
Internxt	🟡
4shared	🟡
Drime	🟡
GitHub	🟡
GitLab	🟡
Immich	🟡
Uploadcare	🟡
Cloudinary	🟡
Filen	🟡

Context: came up in #322 while documenting test coverage.

[axpnet]

Done for v4.1.0: the deterministic offline test net now covers all 16 unit-only providers (one reviewable, behaviour-preserving commit each; Swift skipped, its only profile Blomp is inactive). Details and commits on the tracker: #361 (comment)

The sibling idea (a single pre-release smoke entrypoint) stays open as a separate tracker item.

[axpnet]

What: A single pre-release smoke entrypoint. One command/script that runs the deterministic suite (Rust plus frontend) and the lab-backed integration tests, skips cleanly when credentials or Docker fixtures are absent, and prints a pass/skip matrix. Wire it into the release checklist as a pre-tag step.

Why: Makes "run the tests before every release" a single reproducible action and makes coverage gaps visible at release time. It also lets a contributor run the deterministic core with one command without needing any lab credentials.

Where: CLI / dev tooling, the release checklist, reflected in the Testing & Verification matrix.

Legend: 🟢 exists · 🟡 pending (this request).

Component	Status
Deterministic Rust + frontend suite	🟢
Lab-backed integration tests	🟢
Single entrypoint running both, clean skip when creds/Docker absent	🟡
Pass/skip matrix output	🟡
Wired into the release checklist as a pre-tag step	🟡

Context: came up in #322 alongside the published test matrix.

[axpnet]

🟢 Rolled forward to v4.1.0. v4.0.9 is out (release notes), so this thread now opens to the v4.1.0 window instead of starting fresh; the title and intro are updated to match.

On what was raised here: the two suggestions in the thread (systematic provider determinism tests, and a single pre-release smoke entrypoint) did not land in v4.0.9 and are carried into the v4.1.0 tracker (#361) for triage, so nothing is lost. Everything that shipped in v4.0.9 is in the 4.0.9 tracker (#349).

New enhancement ideas for v4.1.0 are welcome, one per comment.

[axpnet]

What: A New(N) verb in the interactive profiles, groups and users sections (rclone config's n) New remote model), so a new entry can be created from inside the -i loop on the shared engine instead of dropping out to a separate add command.

Why: Creation is the one common action still missing from the interactive loop; surfacing it as N keeps the whole create/rename/copy/delete cycle in one place and reads the same across all three sections. The reporter also ranks New(N), an eager-evaluation preview and a single-vs-multi-target placeholder ahead of Edit(E) and the 2-letter semantics.

Where: CLI (aeroftp profiles -i / groups -i / users -i).

🟢 Planned for v4.1.0 (tracked in #361).

originally from #311 (comment) (@EhudKirsh)

[axpnet]

What: Reorder the interactive -i action bar so the safe, read-only verbs lead with Help(H) first and re-index(#) moves out of the front position. Letters and dispatch stay identical, so no scripted automation breaks.

Why: Help is where users get started and is the most common starting point in any tool, while re-index(#) is slightly more consequential than the read-only verbs and reads oddly as the first option. Keys being stable means the bar can be organised for clarity freely.

Where: CLI (aeroftp profiles -i / groups -i / users -i).

🟢 Planned for v4.1.0 (tracked in #361).

originally from #311 (comment) (@EhudKirsh)