The story behind the shell, and the field tech who built it.
The maker
"At an MSP the day is not one big problem but a hundred small ones, each with a client waiting. Save a few seconds finding the right file on every ticket and by Friday you have bought back hours."
I'm Steve the Killer, a field technician and systems administrator at a large MSP, working in IT since 2018. I did not start there. I had been building websites since the 90s and spent roughly eight years as a full-stack developer before I moved into IT, so writing the tool I need comes as naturally to me as fixing the machine in front of me.
So much of the job is closing tickets while someone waits on the other end of the line, and a surprising number of them come down to one small thing: finding a file by name, or finding every file that contains a certain line. The built-in Windows search made you wait while it built an index, and the heavier tools wanted an install or a license before they would look inside a single folder. Neither respects the fact that a client is on hold.
I wanted something I could drop on any machine, point at a folder, and have the answer before the client finished their sentence. Every second it saves is a second handed back to the next ticket. So I built it, and KillerShell is the result.
The app
KillerShell is a native Windows file browser, terminal and text editor that ships as a single self-contained executable. Install it or run it portable. There is no service to register, no account, and no subscription. Hand someone the .exe and they can search a folder tree right away.
It is built for a field tech's reality. It matches filenames with wildcard patterns, searches inside files one line at a time so it never loads a whole file into memory, runs several search terms in a single pass, and streams matches as it finds them. Everything happens locally, with no index, no telemetry, and no ads.
It started as a search box and nothing else. But finding the file was never the end of the job: I would find it, then reach for Explorer to look at the folder, then for a terminal to run something against it, then for Notepad to read it, and every one of those was a different window with a different set of keys. So I kept pulling those tools in until the whole loop lived in one place. A tab is now a folder, a search, a PowerShell or CMD prompt opened where I was standing, or the file itself with syntax highlighting.
The rule I held to while it grew was that everything gets a key. Not a chord buried in a menu - a real binding, single keys where I could find one free, and Explorer's own conventions everywhere they already existed, so nothing has to be relearned. F7 opens the file, F8 opens a shell in it, F11 splits the window, F1 draws the whole map on a keyboard you can hold a modifier over. A tool you have to go looking for with the mouse is a tool that costs you the thing it was supposed to save.
Much of what it does was driven by the tickets it helped close. The GitHub issues page stays open to anyone, and your suggestions genuinely shape where it goes next. KillerShell is free software under the GPL-3.0 license. The How to page walks through everything it does, and the Technical page has the deep details.
Contact & links
Find me, file a bug, or just say hi:
