Thanks for helping improve Command Center.
Small fixes, documentation improvements, and focused feature proposals are welcome.
🏠 README · 📚 Docs · 🔐 Security · 🐛 Issues
Check existing issues first, then use the bug report or feature request template. For bugs, include:
- the app version, distribution, and installation method,
- steps to reproduce,
- expected versus actual behavior,
- whether the problem occurs in the desktop app or the browser preview.
Caution
Security vulnerabilities: don't open a public issue. Report them privately as described in SECURITY.md.
Warning
Remove secrets and personal information from screenshots and logs. Terminal transcripts and configuration files can contain credentials; include only the relevant, redacted excerpt.
- 🍴 Fork the repository and create a branch for your change.
- 📦 Follow the installation guide to set up the development environment.
- 🎯 Keep the change focused and update documentation when behavior changes.
- ✅ Run the relevant development checks. For interface changes, include a screenshot and verify the desktop behavior when applicable.
- 📬 Open a pull request explaining the problem, resulting behavior, and how you verified it.
Tip
For changes to installers or catalog scripts, start in Commander Toolbox. Command Center consumes a pinned revision of its shared core.
Keep the frontend and Rust responsibilities consistent with the existing architecture. Preserve command review, compatibility checks, cancellation, private local storage, and configuration conflict detection when editing execution paths. Use temporary fixtures for tests that involve Git, backups, or subprocesses.
Prefer clear code and a small dependency footprint. Explain any new dependency or change to platform requirements in the pull request.
Important
Report checks you could not run rather than marking them as passed.