Command Center CLI

Binary distribution of UpToSpeed Command Center, a desktop-friendly interface for reviewing repositories and generating walkthroughs. This package installs a thin Node.js wrapper that launches the precompiled Command Center binary for your platform via platform-specific optional dependencies.

Supported Platforms

• macOS arm64
• macOS x64
• Linux arm64
• Linux x64
• Windows x64

If your platform is missing, please open an issue so we can add another target.

Installation

npm install -g @command-center/command-center

This command places a command-center executable on your $PATH. During installation npm/yarn/pnpm automatically adds the matching optional dependency:

• @command-center/command-center-macos-arm64
• @command-center/command-center-macos-x64
• @command-center/command-center-linux-arm64
• @command-center/command-center-linux-x64
• @command-center/command-center-win-x64

Each optional package ships exactly one prebuilt binary. The wrapper resolves the right package at runtime and forwards all CLI arguments to its binary.

Usage

command-center [flags]

Common flags:

• --debug – print embedded asset information after startup
• --help – show runtime help from the bundled binary

The application starts an HTTP server (defaults to port 9000). Open the printed URL in your browser to launch the UI. Environment variables are loaded from .env in the directory where you run the command; create that file to provide API keys or override the port.

Upgrade

npm update -g @command-center/command-center

After updating, run command-center --version to verify the new binary.

Maintainer Utilities

If you are working from the repository and want to validate the packaged artifacts before publishing, run:

npm run build-and-install

This command rebuilds the binaries, generates platform-specific packages under artifacts/platform-packages/, and installs both the matching platform binary package and the CLI in a temporary directory. Finish by running command-center --version (the script does this for you) or launching the app directly from the printed path.

Troubleshooting

• “Unsupported platform” – The wrapper could not map your process.platform/process.arch combination. Please file an issue with your OS and architecture.
• “Expected binary … was not found” – Reinstall the package. If you are developing locally, run npm run prepare:dist from the repository root to refresh the optional binary packages.
• Permission errors – On POSIX systems, ensure the binaries remain executable (chmod +x node_modules/@command-center/command-center-*/dist/command-center-*).