Developer Command Center
Control your local development environment from one place inside VS Code.
Developer Command Center (DCC) is a local-first VS Code extension for project discovery and common development workflows. It has no AI features, account requirement, or telemetry. Source code and secret values are not uploaded.
Features
- Project/framework and package manager detection, project scripts and a theme-aware dashboard
- Local listening port discovery, browser opening and confirmed process termination
- Git status, staging, commits, branch/stash actions, fetch, pull and push
- Environment variable name discovery and source usage checks; values are masked until an explicit reveal
- Dependency inventory and opt-in npm registry version/search lookups
- Docker container and Compose actions, image inventory and confirmed build-cache cleanup
- Prisma schema/model inspection and CLI commands
- Local TODO/FIXME scanning, project health checks, and common configuration secret checks
- Test/build script launching, VS Code Problems access, workspace bookmarks and generated-cache cleanup
- Database connection secrets stored in VS Code SecretStorage with local CLI adapters for PostgreSQL, MySQL, SQLite, Redis, and MongoDB
- Accessible VS Code theme variables, keyboard navigation, Activity Bar view, status bar, settings and Command Palette actions
Screenshots
Open the workspace in VS Code and press F5 to preview the dashboard in the Extension Development Host. Screenshots will be added after an Extension Host visual QA pass.
The extension only shows information that can be collected safely from the current workspace or local command-line tools. A missing executable or unsupported project shape is reported as unavailable.
Installation
Install the .vsix package from the VS Code Extensions view using Install from VSIX, or install the published extension after a Marketplace release. The package is not yet published by this repository.
Getting started
- Open a project folder or multi-root workspace in VS Code.
- Select the Developer Command Center icon in the Activity Bar.
- Choose Overview to inspect project information and available actions.
- Run scripts, Git actions, Docker operations, or cleanup actions explicitly from the dashboard.
The extension does not run project commands automatically at startup. Running a script executes the script already defined by the workspace's package.json in a VS Code terminal.
Privacy
- No AI, telemetry, account, or source upload.
- Environment values are excluded from dashboard snapshots. Revealing a value requires a click and confirmation.
- Database connection strings are stored using VS Code SecretStorage; profile and workspace state contain names and UI preferences only.
- Optional npm registry version/search requests are disabled by default. Enable
dcc.enableNetworkFeatures to use them. Requests contain package names only.
- Git, Docker, database, and package manager commands run on the local machine. Review commands before use; destructive operations ask for confirmation.
The extension targets Windows, macOS, and Linux. Project detection recognizes JavaScript/TypeScript frameworks and common Python, Go, Rust, Java, PHP, and Flutter manifests. Git and Docker features need their respective local CLIs. Port scanning uses PowerShell on Windows and lsof on macOS/Linux. Database connections currently use installed database CLI clients; table browsing and query execution depend on each client's output and installed features.
The React webview uses VS Code theme variables and bundles all UI assets locally; it does not load a CDN.
Configuration
| Setting |
Default |
Purpose |
dcc.refreshIntervalSeconds |
20 |
Dashboard refresh interval, minimum 5 seconds |
dcc.enableNetworkFeatures |
false |
Enables npm package metadata and search lookups |
dcc.ignoreFolders |
common generated folders |
Folders excluded from project scans |
dcc.todoTags |
TODO, FIXME, BUG, HACK, NOTE, XXX |
TODO tags to recognize |
dcc.maxScanFiles |
12000 |
Maximum local source files scanned |
dcc.showStatusBar |
true |
Shows the DCC status bar shortcut |
The optional .dcc.json schema is provided as .dcc.schema.json. A starter configuration is in .dcc.example.json.
Commands
Open the Command Palette and search for Developer Command Center. Main commands include opening or refreshing the dashboard, quick actions, running/stopping/restarting scripts, opening a localhost port, killing a process, Git pull/push, running tests, cleaning caches, opening Prisma Studio, and extension settings. High-value dashboard shortcuts are Ctrl+Alt+D / Cmd+Alt+D and Ctrl+Alt+Q / Cmd+Alt+Q.
Health score
The displayed health score is deterministic and local. Current project checks cover Git initialization, dependency installation, package manager lockfiles, environment variable use/presence, and Prisma model parsing. Each check contributes equally: pass = 100, issue = 50. It is a hygiene indicator, not a security certification.
Development
Requirements: Node.js 20.19 or newer and npm for development/building; VS Code 1.96 or newer to run the extension.
npm install
npm run build
npm run test
npm run lint
Open this folder in VS Code and press F5 to launch the Extension Development Host. npm run build compiles the React webview and type-checks/bundles the extension. Tests use Vitest. To package a Marketplace-installable .vsix, run npm run package after installing dependencies.
Troubleshooting
- If the dashboard reports no workspace, open a folder in VS Code.
- If a package script cannot run, inspect the package manager lockfiles and ensure there is only one active manager.
- If Docker, Git, ports, or database actions are unavailable, install the corresponding local CLI and ensure it is on the extension host's PATH.
- Network package lookup requires
dcc.enableNetworkFeatures.
- Database credentials remain stored in VS Code SecretStorage. Remove a connection from the Database section to delete its saved secret.
- See Developer Command Center in the Output panel for extension diagnostics; secret values are not logged.
Roadmap
The project brief describes additional goals such as richer database schema browsing, SQL result exports, full test-result parsing, build history, log aggregation, disk usage reports, custom command-chain editing, multi-project service orchestration, detailed dependency audits, and more. The current extension includes the local-first foundation and common action paths; these advanced workflows still need deeper implementation and runtime validation before the extension should be described as Marketplace production-ready.
Contributing
Keep scanners local, avoid sending source or secret values over the network, validate all Webview messages, use argument arrays for local commands, and require explicit user confirmation before destructive actions. Add or update focused tests for scanner, project detection, and message behavior.
License
MIT. See the LICENSE file included in the repository.