codex-command-center README

The project's README from github.com/sevensir888/codex-command-center. As one markdown file: README.md.

Codex Command Center

Turn Codex sessions into organized engineering work.

CI License Platform

Codex Command Center banner

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.

Codex does the reasoning, editing, commands, and tests. Codex Command Center keeps the surrounding engineering workflow understandable and resumable.

Overview

Heavy Codex usage can leave useful context spread across:

Codex Command Center connects those pieces into one focused workflow:

Project -> Task -> Codex Session -> File Changes -> Result

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.

Screenshots

Dashboard Projects and tasks
Dashboard Projects and tasks
Sessions Git changes
Sessions Git changes
Codex environment
Codex environment

Core features

Typical workflow

Add a repository
-> create or select an engineering task
-> launch or resume Codex work
-> review indexed sessions
-> inspect Git changes
-> continue, complete, or block the task

Local-first behavior

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.

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.

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.

Requirements

Installation

Windows binaries are available from GitHub Releases.

Windows release binaries are currently unsigned. Source-build instructions remain in the Development and Build sections below.

Development

Install dependencies:

npm ci

Run the browser development surface:

npm run dev

Run the desktop app:

npm run tauri:dev

Run the frontend production build:

npm run build

Run the lightweight tracked-file secret scan:

npm run check:secrets

Build

Build the desktop application:

npm run tauri:build

For native checks when Cargo is available:

cargo fmt --manifest-path src-tauri/Cargo.toml -- --check
cargo check --manifest-path src-tauri/Cargo.toml
cargo test --manifest-path src-tauri/Cargo.toml
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets --all-features -- -D warnings

Architecture

Relationship to CodMate

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.

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.

Contributing

See CONTRIBUTING.md.

Use Issues for bugs and focused feature requests, Discussions for questions, workflow ideas, and general feedback, and Security for private vulnerability reports.

Security

See SECURITY.md.

Roadmap

See ROADMAP.md.

Release notes

Release notes for v0.1.1 are available under docs/releases/v0.1.1.md. Earlier release notes remain under docs/releases/ and on the GitHub Releases page.

License

Codex Command Center is distributed under the Apache License 2.0.

Disclaimer

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.

codex-command-center (sevensir888/codex-command-center)

Searching Database…

What is this?Codex Command Center is a Windows-first, local-first desktop workspace that organizes Codex-based engineering work: projects, tasks, Codex sessions, Git changes, Skills, and MCP configuration, all in one place.
Is this a full IDE or something lighter?It's a focused organizing layer, not an IDE, terminal, chat client, or Git GUI replacement. It links to your local Codex CLI and Git rather than replacing them.
How do I install and run it?Download a Windows binary from GitHub Releases: the NSIS setup executable (recommended), an MSI installer, or a standalone executable that runs without installation. Note that current release binaries are unsigned.
What do I need on my machine for it to work?You need Git on PATH for Git review and the Codex CLI on PATH to launch and resume sessions. Building from source additionally requires Node.js 24 plus Rust and Cargo.
Any install pitfalls I should know about?Windows release binaries are currently unsigned, so you may see security warnings when installing. Windows 11 is the primary supported platform, so other OSes aren't officially covered.
Does it send my code or Codex sessions anywhere?No. It keeps everything local, doesn't upload source code, sessions, or diffs, and redacts anything that looks like a key, token, or secret in configuration previews.
What does the Git review feature actually let me do?It shows branch state, staged and unstaged files, and per-file diffs, and lets you stage, unstage, and commit changes directly from the app.
How does it discover my Codex sessions without messing them up?It indexes local Codex session metadata read-only, so you can link sessions to tasks and resume them through the Codex CLI without mutating the original session files.
Is this built from scratch?No, it evolved from the open-source CodMate project by Loocor and has been substantially reworked into a Windows-first, Codex-centric tool, with Apache-2.0 attribution preserved.
Where does the app store its data?As local JSON under the user's local application data directory; registered projects are stored only as path references, not copies of source code.
Size
12 MB
Stars
202
Age
2mo
Commits · 90 Days