Skip to content
Back to search

codex-command-center

A local desktop control center for organizing Codex projects, engineering tasks, sessions, Git changes, Skills, and MCP configuration.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/sevensir888/codex-command-center with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/sevensir888/codex-command-center'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sevensir888-codex-command-center/badge.svg)](/listings/sevensir888-codex-command-center)

HTML

<a href="/listings/sevensir888-codex-command-center"><img src="/api/listings/sevensir888-codex-command-center/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 182 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Codex Command Center
  2. **Turn Codex sessions into organized engineering work.**
  3. ![CI](https://github.com/sevensir888/codex-command-center/actions/workflows/ci.yml/badge.svg)
  4. ![License](https://img.shields.io/badge/license-Apache--2.0-blue)
  5. ![Platform](https://img.shields.io/badge/platform-Windows-0078d4)
  6. ![Codex Command Center banner](public/repository-banner.png)
  7. Codex Command Center is a Windows-first, local-first desktop workspace for organizing Codex-based engineering work across projects, tasks, sessions, Git changes, Skills, and MCP configuration.
  8. Codex does the reasoning, editing, commands, and tests. Codex Command Center keeps the surrounding engineering workflow understandable and resumable.
  9. ## Overview
  10. Heavy Codex usage can leave useful context spread across:
  11. - local repositories;
  12. - engineering objectives;
  13. - Codex session history;
  14. - staged and unstaged Git changes;
  15. - local Skills;
  16. - MCP configuration.
  17. Codex Command Center connects those pieces into one focused workflow:
  18. ```text
  19. Project -> Task -> Codex Session -> File Changes -> Result
  20. ```
  21. The app is intentionally smaller than an IDE, terminal emulator, chat client, or advanced Git GUI. It is an organizing layer for local Codex work.
  22. ## Screenshots
  23. | Dashboard | Projects and tasks |
  24. | --- | --- |
  25. | ![Dashboard](docs/screenshots/dashboard.png) | ![Projects and tasks](docs/screenshots/projects.png) |
  26. | Sessions | Git changes |
  27. | --- | --- |
  28. | ![Sessions](docs/screenshots/sessions.png) | ![Git changes](docs/screenshots/git-changes.png) |
  29. | Codex environment |
  30. | --- |
  31. | ![Codex environment](docs/screenshots/skills-mcp.png) |
  32. ## Core features
  33. - **Project organization**: register local development folders and see branch, Git state, task counts, and recent activity.
  34. - **Task tracking**: organize engineering objectives with Planned, Active, Completed, and Blocked statuses.
  35. - **Codex session discovery**: index local Codex session metadata without mutating Codex session files.
  36. - **Session workflows**: link sessions to tasks, launch Codex for a task, and resume selected sessions through the local Codex CLI.
  37. - **Git review**: inspect branch, staged files, unstaged files, working-tree state, and per-file diffs; stage, unstage, and commit focused changes.
  38. - **Codex environment visibility**: show detected Codex CLI path/version, redacted local configuration previews, discoverable Skills, and MCP server summaries.
  39. - **Local-first storage**: keep projects, tasks, session links, and settings on the local machine.
  40. ## Typical workflow
  41. ```text
  42. Add a repository
  43. -> create or select an engineering task
  44. -> launch or resume Codex work
  45. -> review indexed sessions
  46. -> inspect Git changes
  47. -> continue, complete, or block the task
  48. ```
  49. ## Local-first behavior
  50. The app stores its own state as local JSON under the user's local application data directory. Registered projects are path references; Codex Command Center does not copy project source code into application storage.
  51. The native layer reads local Codex session metadata, local Codex configuration files, local Skills folders, local MCP configuration, and Git status for registered projects. Configuration previews redact lines that appear to contain keys, tokens, secrets, or passwords.
  52. The project does not add telemetry, analytics, accounts, cloud synchronization, source-code upload, Codex-session upload, or Git-diff upload. The app can still invoke external local tools such as `codex` and `git`; those tools have their own behavior and configuration.
  53. ## Requirements
  54. - Windows 11 is the primary supported platform.
  55. - Git on `PATH` for Git review.
  56. - Codex CLI on `PATH` for launch and resume actions.
  57. - Node.js 24 is the validated source-development and production-build version; Rust and Cargo are also required for native builds.
  58. ## Installation
  59. Windows binaries are available from [GitHub Releases](https://github.com/sevensir888/codex-command-center/releases).
  60. - **NSIS setup executable**: recommended for most Windows users. This is the normal interactive installer.
  61. - **MSI installer**: useful for users or environments that prefer MSI-based installation or deployment.
  62. - **Standalone executable**: can run directly without a normal installer.
  63. Windows release binaries are currently unsigned. Source-build instructions remain in the Development and Build sections below.
  64. ## Development
  65. Install dependencies:
  66. ```bash
  67. npm ci
  68. ```
  69. Run the browser development surface:
  70. ```bash
  71. npm run dev
  72. ```
  73. Run the desktop app:
  74. ```bash
  75. npm run tauri:dev
  76. ```
  77. Run the frontend production build:
  78. ```bash
  79. npm run build
  80. ```
  81. Run the lightweight tracked-file secret scan:
  82. ```bash
  83. npm run check:secrets
  84. ```
  85. ## Build
  86. Build the desktop application:
  87. ```bash
  88. npm run tauri:build
  89. ```
  90. For native checks when Cargo is available:
  91. ```bash
  92. cargo fmt --manifest-path src-tauri/Cargo.toml -- --check
  93. cargo check --manifest-path src-tauri/Cargo.toml
  94. cargo test --manifest-path src-tauri/Cargo.toml
  95. cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets --all-features -- -D warnings
  96. ```
  97. ## Architecture
  98. - **Frontend**: React and TypeScript under `src/`.
  99. - **Desktop shell**: Tauri 2 configuration under `src-tauri/`.
  100. - **Native commands**: Rust commands for local filesystem, process launch, Git, Codex session indexing, Skills discovery, and MCP configuration summaries.
  101. - **Storage**: local JSON state under the user's local application data directory.
  102. - **Codex integration**: local Codex CLI detection plus launch/resume commands.
  103. - **Git integration**: local Git CLI calls for branch, status, diff, stage, unstage, and commit operations.
  104. ## Relationship to CodMate
  105. Codex Command Center evolved from the open-source CodMate project by Loocor. Upstream work is acknowledged, and applicable Apache-2.0 licensing and attribution are preserved in `LICENSE`, `NOTICE`, and `THIRD-PARTY-NOTICES.md`.
  106. This project has been substantially refocused and reworked around a Windows-first, Codex-centric workflow for projects, tasks, sessions, and Git changes. It should not be described as built entirely from scratch.
  107. ## Contributing
  108. See [CONTRIBUTING.md](CONTRIBUTING.md).
  109. Use [Issues](https://github.com/sevensir888/codex-command-center/issues) for bugs and focused feature requests, [Discussions](https://github.com/sevensir888/codex-command-center/discussions) for questions, workflow ideas, and general feedback, and [Security](https://github.com/sevensir888/codex-command-center/security) for private vulnerability reports.
  110. ## Security
  111. See [SECURITY.md](SECURITY.md).
  112. ## Roadmap
  113. See [ROADMAP.md](ROADMAP.md).
  114. ## Release notes
  115. Release notes for v0.1.1 are available under [docs/releases/v0.1.1.md](docs/releases/v0.1.1.md). Earlier release notes remain under [docs/releases/](docs/releases/) and on the [GitHub Releases page](https://github.com/sevensir888/codex-command-center/releases).
  116. ## License
  117. Codex Command Center is distributed under the [Apache License 2.0](LICENSE).
  118. ## Disclaimer
  119. Codex Command Center is an independent open-source project and is not an official OpenAI product. OpenAI, Codex, and related marks belong to their respective owners.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.