DEV Community

Daniel Hofman
Daniel Hofman

Posted on

Just shipped v2.11 of the CLI manager I've been building for Windows

I've been building TerminalNexus for a while now. It's a Windows terminal emulator that tries to solve the "I have 40 commands I run constantly and they live in 6 different places" problem. Sticky notes, Notepad files, .bat scripts scattered across the desktop, a OneNote with commands that stopped working six months ago.

The idea was simple: one place, organized by project, run anything with a click. It grew from there.

This week I shipped 2.11. Here's what's in it.

The Windows Terminal dependency is gone

This was the big one, honestly. Earlier versions depended on Windows Terminal being installed. That created a whole category of support headaches. Different WT versions behaved differently, some corporate machines had it blocked, and it added setup friction that shouldn't exist.

2.11 ships with its own built-in terminal engine. Nothing extra to install. It just works.

Variables Manager

This one's been on the list for a long time.

You can now define variables at global, project, or session scope and use them in any command with {{variable_name}} syntax. So instead of hardcoding a server IP or SSH key path everywhere, you set it once and reference it. When you're onboarding someone, you hand them a command set and they fill in the variables specific to their environment.

Secrets (API keys, passwords, tokens) are stored encrypted and masked in the UI. They don't show up in logs or exports unless you explicitly allow that.

It also supports multi-line values, which matters more than it sounds. SSH keys, certificates, JSON blobs. Paste them in once, reference them anywhere.

Shell Conversion

Right-click a command in the terminal, pick a target shell, and the AI converts it. Bash to PowerShell, PowerShell to CMD, whatever direction you need. The panel shows a confidence score and lets you re-run the conversion if the first result isn't right.

I stopped having to Google "PowerShell equivalent of chmod" three times a day.

Scheduled output panels

You can already schedule commands to run on a timer. What 2.11 adds is proper visibility into what happened.

Each scheduled command gets a panel in the assistant sidebar that shows the output history. The AI reads each run's output and classifies it as healthy, warning, or critical, so at a glance you can see whether your automated checks are passing without actually reading the output every time.

You can reorder the panels, set header colors to visually separate them, and the history persists across restarts.

The rest

Per-provider AI config is new. You can now set different API keys and models for each provider (OpenAI, Anthropic, OpenRouter, Ollama, LM Studio) independently instead of one global setting. Useful if you use different models for different tasks.

Quick Action Buttons on the toolbar for common AI commands. All dialogs got a visual refresh with a proper dark theme.

The product

TerminalNexus is Windows-only. There's a free version with 15 command buttons, one project, 400+ built-in command presets, SSH manager, and multi-shell tabs. It's a real tool, not a crippled demo.

If you outgrow that, there's a paid version with unlimited projects, AI features, scheduling, and shell conversion.

It supports PowerShell, CMD, Git Bash, WSL, and custom shells. The AI integration is bring-your-own-provider, including local models via Ollama or LM Studio. No telemetry, no usage data sent anywhere.

If you're on Windows and find yourself re-typing the same commands every day, it's worth a look.

https://safesoftwaresolutions.com (https://safesoftwaresolutions.com/)

Happy to answer questions in the comments.

Top comments (0)