A Windows desktop product built by Robert
CommandDeck
A Windows desktop product built by Robert to make common command-line and development workflows easier to manage while retaining terminal capability.
Project facts
- Relationship
- A Windows desktop product built by Robert
- Status
- Signed Windows beta build produced
- Platform type
- Windows desktop application
- Technologies
- Electron, React, TypeScript, Vite, node-pty, xterm.js
- Current stage
- Signed Windows beta build produced using Microsoft Azure Trusted Signing
- Capability
- Desktop application and local tooling
Selected capabilities
CommandDeck turns repeated command-line work into a focused Windows desktop experience. These capabilities show the product's local workflow design, command review, project context and careful beta release foundations.
Windows Command Workbench
CommandDeck brings real terminal sessions into a focused Windows desktop workspace while keeping shell execution inside the desktop app.
- - Embedded terminal sessions
- - Windows shell profiles
- - Project-specific working directories
Project-Aware Command Cockpit
Users can save reusable commands per project, pin frequent actions and choose whether commands are inserted for review or run directly.
- - Per-project command buttons
- - Pinned, searched and filtered command library
- - Insert and run modes
Safer Command Review
CommandDeck adds friction around risky terminal actions through risk labels and explicit confirmation for high-risk commands.
- - Command risk classification
- - Warning review before execution
- - Typed confirmation for high-risk actions
Guided Project Setup with Starter Packs
First-run setup detects common local project signals and recommends starter command packs without running anything automatically.
- - Local stack detection
- - Recommended starter packs
- - Explicit import decisions
Project Files Path Navigator
CommandDeck helps users find and use project paths from inside the terminal workflow without indexing file contents.
- - Browse and search project paths
- - Copy or insert relative paths
- - Open or reveal files with local tools
Portable Command Decks
Command libraries can be exported and imported as versioned JSON, with preview checks before anything is added.
- - Command deck JSON export
- - Import preview and validation
- - Duplicate, invalid and high-risk summaries
Privacy-Conscious Diagnostics and Feedback
Testers can preview local diagnostics and feedback packages before deciding what to share.
- - Opt-in local diagnostics
- - Sanitised preview before sharing
- - Feedback package preview with size controls
Secure Windows Update and Release Pipeline
The beta includes a careful Windows update and release foundation with manifest checks, signed installer verification and release provenance work.
- - Update manifest validation
- - Signed installer verification
- - Windows signing and release scripts
The problem
Command-line work is powerful, but it can be awkward for repeated development tasks. People may need to remember commands, working directories, project context and shell differences before they can do the task they actually care about.
CommandDeck was built to make those workflows easier to manage on Windows while retaining genuine terminal capability. It is not an attempt to hide the terminal completely. It gives common commands a clearer, project-aware interface.
What was built
The product uses Electron, React, TypeScript and Vite. Terminal functionality uses node-pty and xterm.js. It supports PowerShell profiles, project profiles, reusable command decks and project-oriented workflow features.
Command decks can be imported and exported, so useful command sets can be moved between contexts. The design also pays attention to shell choice, working directory and local project configuration.
Desktop release considerations
Releasing desktop software requires more than building the interface. Packaging, signing, local process boundaries and update expectations all matter because the application runs with responsibility on a user's machine.
A Windows beta has been produced, and production artefacts have been code-signed using Microsoft Azure Trusted Signing. That is stated as a build and distribution fact, not as a claim of public adoption.
Current status
CommandDeck has a signed Windows beta build. No tester numbers, sales, public adoption or final production status are claimed.
What this work demonstrates
- - desktop application development on Windows
- - balancing accessibility with genuine terminal power
- - working with shell, process and project boundaries
- - understanding packaging and signing responsibilities
Have a workflow that needs careful improvement?
If a process in your business needs clearer systems, a focused tool or a better way of working, start with the operational problem.