-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Turn Codex sessions into organized engineering work.
Codex Command Center is a local-first desktop control center designed specifically for developers who use Codex across real software projects.
Codex is excellent at executing engineering work. But as projects grow, individual sessions quickly become difficult to organize: one repository may contain multiple objectives, several Codex sessions, Git changes, Skills, MCP configuration, and unfinished work spread across different points in time.
Codex Command Center adds an organizational layer above Codex.
Instead of treating every Codex session as an isolated conversation, it organizes engineering activity around a simple workflow:
Project → Task → Codex Session → File Changes → Result
A Codex session tells you what happened during one interaction.
A real engineering project needs more context:
- Which project does this work belong to?
- What engineering task was Codex working on?
- Which sessions belong to the same objective?
- What files changed?
- Can an earlier session be resumed?
- Is the repository clean or modified?
- Which Codex Skills are available?
- Which MCP servers are configured?
Codex Command Center brings these pieces together in one local workspace.
The goal is not to replace Codex.
Codex executes the work. Codex Command Center organizes it.
A local development repository or workspace.
Projects provide the top-level context for engineering work, including:
- local path
- Git branch
- working-tree state
- tasks
- Codex sessions
- recent activity
A concrete engineering objective inside a project.
Examples:
- Implement authentication
- Refactor the API layer
- Add email notifications
- Investigate a regression
- Review a feature implementation
Tasks provide the missing organizational layer between a project and individual Codex sessions.
A local Codex execution history associated with engineering work.
Codex Command Center can organize discovered sessions, associate them with projects and tasks, inspect useful metadata, and resume existing work.
Git changes provide the code-level result of engineering activity.
The application surfaces useful repository state such as:
- branch
- modified files
- staged files
- unstaged files
- diff information
- working-tree status
The final state of an engineering task: what was completed, what changed, and which Codex sessions contributed to the work.
Organize local repositories as engineering workspaces instead of browsing disconnected Codex sessions.
Group related Codex activity around real development objectives.
Task states remain intentionally simple:
- Planned
- Active
- Completed
- Blocked
Discover and organize local Codex sessions while preserving Codex's original session data.
Return to earlier Codex work from the correct project context without building a competing chat interface.
Inspect the repository state directly from the project workspace, including staged and unstaged changes and readable diffs.
View the local Codex environment in one place:
- Codex CLI
- configuration
- Skills
- MCP servers
Sensitive credentials are not intended to be exposed through the interface.
Codex Command Center is designed around local developer workflows.
Project paths, session data, Git changes, and local configuration remain on the user's machine.
The project does not add telemetry or cloud synchronization.
Codex Command Center intentionally avoids becoming another full IDE.
It does not aim to replace:
- Codex
- VS Code
- terminal applications
- Git clients
- AI chat interfaces
Instead, it focuses on the layer that sits between the developer and Codex:
engineering organization.
This keeps the product smaller, easier to understand, and focused on one problem.
A compact overview of:
- Codex availability
- active tasks
- projects
- recent sessions
- repository status
Manage local development workspaces and inspect their tasks, sessions, and Git state.
Browse and search local Codex history and connect sessions to meaningful engineering work.
Inspect the local Codex CLI, configuration, Skills, and MCP environment.
Application-specific configuration without unnecessary provider or account complexity.
Codex Command Center uses a compact Windows-first desktop architecture:
- React
- TypeScript
- Vite
- Tauri 2
- Rust
- local filesystem and process integration
- Codex CLI/session integration
- Git CLI integration
- local application state
The architecture deliberately avoids cloud infrastructure, external databases, microservices, and unnecessary platform complexity.
Traditional session managers center the product around conversations.
Codex Command Center takes a different approach.
The primary object is not the conversation.
The primary object is the engineering task.
Sessions become execution history attached to that task.
This changes the mental model from:
Session → Session → Session
to:
Project → Task → Sessions → Changes → Result
That distinction is the central idea behind the project.
Codex Command Center evolved from ideas and selected foundations in the open-source CodMate project.
CodMate explored session management across multiple AI coding tools and providers.
Codex Command Center intentionally narrows that scope and reorganizes the product around Codex-specific engineering workflows, project context, tasks, sessions, Git changes, Skills, and MCP visibility.
Upstream attribution and applicable license notices are preserved in the repository.
Codex Command Center follows a local-first philosophy.
It does not intentionally upload:
- source code
- project paths
- Codex session history
- Git diffs
- local Codex configuration
to an external service.
No telemetry or analytics platform is included.
Source code, documentation, contribution information, and project updates are available in the main repository:
https://github.com/sevensir888/codex-command-center
If the project is useful to you, consider starring the repository or opening an issue with feedback.
Codex Command Center is an independent open-source project and is not affiliated with or endorsed by OpenAI.
OpenAI and Codex are trademarks or product names of their respective owner(s).