v1.0.0
Command Center 1.0.0
Release date: July 27, 2026
Command Center 1.0.0 is the first stable release of the local-first command
library. It keeps commands, scripts, snippets, references, tags, collections,
and search data on your machine, while keeping the optional OpenAI workflows
behind an explicit opt-in and review boundary.
Building the Windows workflow does not publish a GitHub release. Release assets
still have to be reviewed and attached manually before this version is
published.
Highlights
- Save commands, scripts, sequences, snippets, configuration fragments, and
reference notes in a local SQLite library. - Search content, notes, tags, collections, and current saved explanations with
SQLite FTS5. - Organize entries with collections, tags, favorites, recents, responsive card
and compact views, and four theme choices. - Keep the sidebar short while browsing complete collection and tag directories
on their own screens. - Select visible entries to add them to a collection without replacing their
existing memberships, or delete the selection after confirmation. - Fill temporary
{{named}}placeholders, copy the rendered command, and leave
the values out of the database. - Review offline Safe, Caution, and Destructive labels before copying a command.
- Import inconsistent documents with OpenAI after local likely-secret redaction
and a complete outbound disclosure. - Explain saved entries, ask the assistant, analyze pasted terminal output, and
convert entries between bash, fish, zsh, and PowerShell. - Export the complete library or one collection as readable Markdown, and create
a consistent, restorable SQLite backup. - Open the AI assistant with
Ctrl/Cmd + Shift + Kwhen AI is available. - Build Windows installers from a manually triggered GitHub Actions workflow
without creating or publishing a release.
AI and privacy
AI is off by default and is not required for the command library. The user
provides their own OpenAI API key, which Rust stores through the operating
system credential manager. The key is not written to SQLite, returned to the
frontend, or stored in plaintext as a fallback.
Requests use the Responses API with store: false. Command Center sends the
selected document, entry, question, or terminal paste needed for the action,
not the whole library. Import and terminal-error pastes show the exact outbound
size, model, and local likely-secret replacements before sending. The detector
cannot guarantee that every secret will be recognized, so the disclosure still
needs a human check.
Model suggestions are checked again by the local risk rules. Nothing is run or
saved automatically. Assistant conversations remain in memory, saved
explanations can be cleared from Settings, and conversions only become library
entries after Review and save.
Fixes and improvements
- Kept the local risk verdict authoritative across imports, explanations,
assistant proposals, terminal analysis, and shell conversion. - Added real cancellation for assistant, diagnosis, and conversion requests.
- Added guarded recovery for an unreadable library while preserving the
original SQLite file and sidecars. - Added an AppImage-only GIO compatibility guard for affected CachyOS systems
without changing normal Linux development or other package types. - Added responsive layouts, keyboard navigation, visible focus states, and
touch-sized controls across the main workflows. - Expanded the in-app Help guide to cover the optional AI workflows and their
privacy boundaries. - Kept launch at startup and close to tray opt-in.
Installation
After the release assets have been attached:
- Open the
Command Center Releases page. - Open version 1.0.0 and expand Assets.
- Download the installer for your operating system.
- Close any running copy of Command Center, then open the installer.
Windows users can choose the .msi or setup .exe when both are present.
Linux users can choose the .AppImage, .deb, or .rpm that matches their
system.
To run an AppImage:
chmod +x ./*.AppImage
./"Command Center_"*.AppImageSource installation instructions are in the
README.
Upgrading
No manual database migration is required. Command Center applies its SQLite
migrations when it opens the library.
Backing up the library before an application upgrade is still sensible. Use
Settings → Back up database so pending WAL data is checkpointed into the
copy.