Sign InOpen Brain
GitHubGitHub RepoNeeds Review

yynxxxxx/Codex-X

Codex-X puts provider switching, prompt injection, session history, Skills, MCP, and TOML settings behind one cross-platform UI for people juggling multiple Codex setups.

GitHub · Trending today
Open Source Open MarkdownOpen JSON
Source Summary

Codex-X is a cross-platform desktop manager for Codex Desktop and CLI. It centralizes providers, logins, prompt injection, sessions, Skills, MCP, config.toml, auth.json, and local token usage; it ships **5 offline prompt templates** and syncs **6 more** from GitHub.

Practical Implication

Use it when your Codex state is scattered across files or providers, but keep existing personal rules in append mode. Its backups, provider consistency checks, project-based session grouping, and attribution of subagent usage to parent sessions can make configuration changes easier to inspect.

Agent-Ready Context
Codex-X is a cross-platform desktop manager for Codex Desktop and CLI. It centralizes providers, logins, prompt injection, sessions, Skills, MCP, config.toml, auth.json, and local token usage; it ships **5 offline prompt templates** and syncs **6 more** from GitHub.

Use it when your Codex state is scattered across files or providers, but keep existing personal rules in append mode. Its backups, provider consistency checks, project-based session grouping, and attribution of subagent usage to parent sessions can make configuration changes easier to inspect.

The repository describes permanent session deletion as unrecoverable, and switching providers may expose API keys and authentication state to another desktop application. macOS packages may also be unsigned or unnotarized, so review the code, release provenance, backups, and requested filesystem access first.
Connected Context · Feed7 Judgment

Codex-X consolidates Codex configuration and history rather than introducing another agent runtime. Against broader multi-agent desktops, its distinct value is inspectability of providers, prompts, Skills, MCP, sessions, and usage in one manager. That convenience also concentrates credentials and destructive session controls, so backups, append-mode prompt changes, release provenance, and filesystem access become part of the adoption decision.

vastsa/PI-DesktopBoth centralize models, MCP, skills, permissions, and subagents in a desktop interface, but Codex-X manages existing Codex state whereas PI-Desktop presents its own agent workspace and operating modes.stablyai/orcaOrca emphasizes isolated parallel execution and supervision; Codex-X instead improves configuration, session grouping, and attribution inside the Codex ecosystem.Full Workshop: Setting Yourself Up for Success —Jason Liu, OpenAI CodexThe workshop’s reusable Skills and persistent Codex workflows are precisely the state Codex-X centralizes, while its warning about explicit boundaries reinforces caution around injected prompts and managed credentials.anthropics/claude-codeClaude Code illustrates the wider move toward plugin-enabled agents across terminal and IDE surfaces; Codex-X addresses the narrower management problem created by Codex’s comparable CLI, desktop, Skills, and configuration surfaces.
Context Map
toolscoding#coding-agents#dev-ux#skills
Uncertainty
The repository describes permanent session deletion as unrecoverable, and switching providers may expose API keys and authentication state to another desktop application. macOS packages may also be unsigned or unnotarized, so review the code, release provenance, backups, and requested filesystem access first.