Codex Control Plane MCP

Overview Schema Source Related Servers Discussions Admin

codex_repair_issue

Run allowlisted repair actions with dry-run first, following diagnostics or agent guidance.

Instructions

Run an allowlisted repair action with dry-run first by default. Use this only when diagnostics or agentGuidance recommends a specific action. Stop when loopGuard.allowed is false.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes
`diagnosis_id`	No
`thread_id`	No
`turn_id`	No
`operation_id`	No
`workflow_id`	No
`client_request_id`	No
`reason`	No
`sandbox`	No
`approval_policy`	No
`dry_run`	No
`force`	No
`stale_after_minutes`	No
`older_than_days`	No
`timeout_seconds`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`agentGuidance`	No
`agentGuidanceText`	No
`recoveryAttemptState`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedJun 19, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "recover_stale_operations",
-  "refresh_catalog_and_history",
-  "refresh_catalog_and_kb",
-  "mark_orphaned_after_exit",
-  "restart_app_server_idle",
-  "force_restart_app_server",
-  "mark_stale_turns_orphaned",
-  "expire_stale_pending_interactions",
-  "refresh_catalog",
-  "rebuild_search_index",
-  "validate_paths_and_config",
-  "interrupt_turn",
-  "cleanup_prompt_submissions"
-]New value: +[
+  "recover_stale_operations",
+  "refresh_catalog_and_history",
+  "reconcile_workflow_from_thread",
+  "retry_workflow_with_runtime_policy",
+  "refresh_catalog_and_kb",
+  "mark_orphaned_after_exit",
+  "restart_app_server_idle",
+  "force_restart_app_server",
+  "mark_stale_turns_orphaned",
+  "expire_stale_pending_interactions",
+  "refresh_catalog",
+  "rebuild_search_index",
+  "validate_paths_and_config",
+  "interrupt_turn",
+  "cleanup_prompt_submissions"
+]

addedInput schema / properties / approval_policy

Added value: +{
+  "default": null,
+  "enum": [
+    "never",
+    "on-request",
+    "on-failure",
+    "untrusted",
+    "ask_openclaw",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / client_request_id

Added value: +{
+  "default": null,
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / reason

Added value: +{
+  "default": null,
+  "maxLength": 4000,
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / sandbox

Added value: +{
+  "default": null,
+  "enum": [
+    "read-only",
+    "workspace-write",
+    "danger-full-access",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / agentGuidance

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

addedOutput schema / properties / agentGuidanceText
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / recoveryAttemptState

Added value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv0.1.2Jun 18, 2026

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description must disclose all behavioral traits. It mentions dry-run by default and a stopping condition, but fails to warn about potentially destructive actions (e.g., force_restart_app_server) or explain what allowlisted means. More detail is needed for safe use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loading the core purpose and usage condition. It could be slightly more structured but is efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema (making return value documentation unnecessary), the tool has 15 parameters and the description is too brief to be complete. It does not explain how different actions relate to parameters or provide sufficient context for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to any of the 15 parameters. Parameters like diagnosis_id, thread_id, etc., are not explained, leaving the agent without guidance on how to set them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool runs an allowlisted repair action with dry-run first by default. It distinguishes from sibling tools like codex_collect_diagnostics or codex_get_* status tools by specifying repair actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use only when diagnostics or agentGuidance recommends an action, and to stop when loopGuard.allowed is false. This provides clear conditions for use, though it doesn't explicitly name alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server