Codex Work Window MCP
Related Servers
Alternatives to Codex Work Window MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables coding agents to run persistent, budgeted work sessions with dependency graphs, human decision queues, required validation, and clean handoffs for autonomous or human-in-the-loop execution.16MIT
- AlicenseAqualityAmaintenanceCoordinates concurrent Codex tasks around a shared ChatGPT quota snapshot, deferring expensive work near exhaustion and storing resumable checkpoints.58MIT
- AlicenseNot gradedqualityBmaintenanceEnables host agents to launch and supervise durable, long-horizon AI jobs—starting, running, resuming, checking budgets, and inspecting assembled context—so tasks can survive restarts and outlive the conversation with verified completion.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to drive Codex Desktop and codex-app-server as a durable async worker for long-running tasks: submit work and get an operation or workflow ID immediately, then poll status, handle approvals and Plan Mode, and read final reports, diagnostics, and history. It adds retry-safe submission, duplicate prompt protection, restart recovery, and worker/queue concurrency management so orchestration never requires holding a single MCP call open for hours.-
- AlicenseNot gradedqualityBmaintenancePersistently connects Codex to Reasonix Studio so Codex can plan and verify while Reasonix executes, delegating tasks across shared multi-client sessions. Keeps tasks, sessions, approvals, results, and artifact fingerprints durable, with idempotent submission, workspace queuing, session reuse and recovery, manual adjudication of unknown outcomes, explicit retries, cancellation, and bounded shutdown.GPL 3.0
- AlicenseAqualityBmaintenanceEnables agents to monitor token/usage limits and persist work checkpoints, allowing them to pause, resume, and track progress across sessions.5MIT
TDQS
Scored across 3 tools
Each tool targets a distinct phase of the work-window lifecycle: planning rules, saving state, and preparing a resume contract. There is no functional overlap or ambiguity about which tool to call.
All names use a two-word underscore convention and clearly describe their action, but the pattern is mixed: window_plan and checkpoint_save are noun-verb while resume_contract is verb-noun. This is a minor deviation from a strictly consistent verb_noun scheme.
Three tools is well-scoped for a focused workflow around planning, saving, and resuming work windows. Each tool earns a clear place; nothing feels redundant or missing at the surface level.
The set covers the core lifecycle of a work window: planning, checkpointing, and resuming. Minor gaps exist such as an explicit finalize/cancel action, but agents can work around those by planning a new window or not resuming.