vCmd
A command prompt that behaves like every other window on the machine.
The problem
cmd.exe is a window from 1993. One command at a time, one shell per window, no tabs, selecting text is a rectangle, and the command you ran last Tuesday is gone. Every serious operating system solved this a decade ago; Windows left it where it was.
So the commands that keep a business running — the one that restarts the service, the one that rebuilds the site, the one with the seven flags — live in a text file on somebody desktop, or in somebody head, and get worked out again each time.
What it does
1A real console, not a pipe
vCmd runs the shell through the same console interface Windows Terminal uses, so a program that asks a question gets an answer, a progress bar draws properly, and Ctrl+C stops what is running rather than closing the window.
2Every shell you have, in tabs
Command Prompt, PowerShell, PowerShell 7, Git Bash and each installed WSL distribution — found automatically, each in its own tab, all in one window.
3It remembers what you ran
A searchable history kept per shell, so the PowerShell tab does not offer you a bash command. It survives closing the window.
4Passwords stay out of it
A command that carries a password, a token or an API key is recognised and never written to the history file. Not masked afterwards — never written.
5Saved commands with blanks
Keep the long one once as "deploy {{site}} to {{server}}". vCmd asks for the blanks, fills them in and runs it. Six useful ones are there to start with.
6Find what scrolled past
Ctrl+F searches what is on screen and in the scrollback, with the matches counted — instead of scrolling back by hand looking for the error.
7Copy and paste like everywhere else
Select and it is copied, right-click pastes, Ctrl+C stops. A pasted block containing a line break is shown to you first, because a line break runs the command.
8Open a prompt here
Right-click any folder, or the background of any folder window, and open a prompt already in it. Drag a folder onto a tab to change to it.
Why it is worth it
It opens with your shells already found and sensible behaviour already on. There is no settings file to write before it stops being annoying.
Tabs, so a build in one and a log in another do not fill the taskbar.
The history refuses commands with secrets in them, and what is on screen is never sent anywhere. vCmd has no network side at all.
Installs into a user profile with no administrator prompt, so it goes on a locked-down workstation and on a server the same way.
How you use it
From the Start menu, or "Open a prompt here" on any folder — it starts in that folder.
The arrow beside it picks a different shell: PowerShell, Git Bash, a WSL distribution.
Type a few letters of it. Ctrl+K for the commands you saved.
Rather than scrolling back through a thousand lines of build output.
What it needs
| Windows | 10 or 11, 64-bit |
|---|---|
| Installs to | Your user profile — no administrator prompt |
| Shells | Whatever is on the machine; Command Prompt and PowerShell are always there |
| Network | None — vCmd never connects to anything |
| Settings | Kept with your profile, so a roaming profile carries them |
See vCmd on your own machine
A short screen-share is usually enough — we open it on your PC, with your files.
Or write to info@issmart.in.
vTouch
vPress
vPDF
vScreen
vBack
vNote
vFTP
vName
vLog
vLogServer
vSys
vCom
vShot
vTag
vAudio
vBooks
vOrg
vSize
vPort
vScan
vCon
vCopy
vAuto
vClean
vShow