Voltius is at the point where I've run out of things to add — so I'm asking you

[kipavy]

Hey everyone,

Short version: Voltius isn't going anywhere, but it's slowing down, and I'd like your help deciding what comes next.

Where things stand

v0.32.1 just shipped. Since the first release the app has grown SSH/SFTP/Serial, team vaults with end-to-end encryption, real-time sync, live session sharing, port forwarding, snippets, plugins, an MCP server, Android, and translations — and for the last few weeks I've hit a wall I didn't expect: I use Voltius every day as my only terminal client, and I no longer run into anything missing, and I no longer run into bugs.

That's a good problem, but it's also a blind spot. I'm one person with one machine, one OS, one set of servers and one way of working. "It's enough for me" says nothing about whether it's enough for you.

What "slowing down" means, concretely

• Releases will be less frequent — features when there's something worth building, not on a schedule.
• Bugs still get fixed. Security updates still ship. Issues and PRs still get read and answered.
• I'm not abandoning this. I'm just not going to invent features nobody asked for to keep the commit graph green.

What I'm asking for

Please reply with anything from this list — one line is fine, no formatting required:

1. What still makes you open another client instead of Voltius? This is the single most useful answer. Whatever it is — a missing protocol, a keybinding, an import path, a feeling — I want to hear it.
2. What do you do every day that takes too many clicks? Slow workflows are worth more to me than missing features.
3. What did you try and give up on? If something confused you and you closed it instead of reporting it, that's a bug in my design, not in you.
4. Bug amnesty. Anything broken you shrugged off and never reported? Now's the time. Small, weird, hard to reproduce — all welcome.
5. What's your setup? OS, how many hosts, self-hosted sync server or the hosted one, solo or team, phone or desktop. I only see my own.
6. Coming from another client? Termius, MobaXterm, ZOC, PuTTY, Windows Terminal, iTerm, Warp — tell me what it does that you miss. (Import from ZOC is already open as Feature request: Import from ZOC Terminal #15.)

If you want to help beyond feedback

• Translations — the app ships English, French, Russian and Simplified Chinese, all at full key coverage. Two things I can't do alone: any other language, and a native-speaker pass over the three I have — coverage means every string exists, not that every string reads well. If Russian, French or Chinese is your first language and something in the UI sounds wrong, tell me and I'll fix it.
• Testing on hardware I don't have — macOS, Windows, Android phones, actual serial devices.
• Packaging — distro packages, Flathub, AUR, anything that gets Voltius into a package manager I don't maintain.
• Docs and screenshots — the app has more features than the README explains.
• Code — the two biggest open design issues are Team administration & offboarding — roles, pending-invite status, seats, leave/remove #72 (team administration & offboarding) and Explicit "Share" verb for vaults — a real share sheet, and unify the two invite panels #68 (a real vault share sheet).

Where to put things

• Ideas and feature requests → the Ideas category.
• Bugs → Issues, with your OS and version.
• Everything else, including replies to this post → right here.

Thanks for the 500+ stars and for every issue anyone has taken the time to file. This project got a lot further than I expected it to, and it'd be a shame to let it stall out purely because one guy's own itch is fully scratched.

— kipavy

[im-nazmul]

First of all, thank you for all the work you've put into Voltius. It's impressive how much the project has grown, and I really appreciate that you're continuing to maintain and improve it.

There are two features I'd really love to see: autocompletion and an option for saved password input on both mobile and desktop, similar to how Termius handles them.

Thanks again for your work on the project!

[kipavy]

Thank you — this is the kind of answer I was hoping for.

On saved passwords: saving a connection's password already works (the auth prompt has a save option, or store it as an Identity in the Keychain and attach it to as many hosts as you like), so I assume you mean passwords typed inside a session — sudo, su, mysql, a script that prompts. Termius can push a saved password into those; Voltius can't. That's a fair gap.

If that's it, tell me how you'd want to reach it:

• A button on the mobile key row / a shortcut on desktop, or should it offer itself when a password prompt is detected?
• The host's own saved password, or a picker over any identity in the vault?
• Desktop, mobile, or both — and which hurts more day to day?

On autocompletion: my honest position is that the inline kind — greyed-out completion as you type, fish-style — belongs to the shell rather than to me. Voltius only sees keystrokes going out and bytes coming back; it never knows what your shell thinks the current line is. A client-side version is guesswork, and it breaks where you'd notice: inside vim, less, tmux, at password prompts, on multi-line prompts. zsh-autosuggestions and fish get it right because they are the shell. I'd rather not ship a worse copy.

The one thing a shell can't do is history across hosts — yours is per-host, while Voltius already records every command you run on every host in one place, including boxes where you can't install anything. That's in the app today as the History panel in the terminal. If you haven't used it, try it and tell me whether it's close to what you're missing, or what would have to change for it to be.

So: is it specifically as-you-type suggestion you want, or getting at a command you've run before? And desktop, mobile, or both? I'm not promising either right now — I want to know which problem I'd be solving before I decide.

[im-nazmul]

Thanks for the detailed response!

Yes, for saved passwords I meant passwords typed inside an active session — sudo, su, database prompts, scripts, etc.

For how I’d like it to work, I think a button on the mobile key row and a keyboard shortcut/button on desktop would be the most useful. A picker that lets me choose from saved identities/passwords in the vault would be ideal rather than limiting it to the host’s own password. I’d prefer this on both desktop and mobile, but it would probably be most useful on mobile where manually entering passwords is more inconvenient.

For autocompletion, I was referring specifically to the as-you-type suggestions similar to Termius. I understand your point about the limitations of implementing that at the terminal-client level and why shell-native completion is more reliable.

I’ll also spend some more time with Voltius’s History panel. Cross-host history actually sounds very useful. One thing that could potentially make it closer to what I’m looking for would be a really quick way to search/filter previous commands and insert a selected command directly into the current prompt, especially on mobile.

Thanks again for taking the feedback seriously!

[ezhkov-ph]

I try to maintain the AUR repository as time allows. Thanks for Voltius — I don’t have any specific requests right now, because it’s already a great product, and you’re doing an excellent job as a developer.

There are a few AUR package variants:

• voltius-git — https://aur.archlinux.org/packages/voltius-git
• voltius-bin — https://aur.archlinux.org/packages/voltius-bin
• voltius — https://aur.archlinux.org/packages/voltius

[kipavy]

Thank you — and thank you for keeping voltius-bin, voltius, and voltius-git up to date. I checked, and voltius-bin is bang on the current release.

I want to flag something rather than let it slide: my release pipeline actually has an AUR-push job already built (generates the PKGBUILD, computes checksums, the works) — but it's never run, because I don't have an AUR account to hold the deploy key, and new registrations are closed right now. So every update to voltius-bin you've been doing has been fully manual on your end, and I'd rather know that openly than assume it's automated when it isn't.

Would you be open to us wiring it up properly — e.g. adding a key I generate as a second SSH key on your AUR account, or making the package co-maintained, so CI can push on release and it never depends on either of us remembering? Whatever's least friction on your side; you'd stay listed as maintainer either way. If AUR has no clean way to do that, no worries — I've added AUR to the README/docs either way, clearly marked as community-maintained so nobody's surprised if it ever lags.

Really appreciate you carrying this — it's exactly the kind of thing this project needs more of.