codex-cli-runtime

Deterministic rescue tasks are executed through the codex-rescue helper, invoking the codex-companion runtime to perform single, auditable operations. The runtime processes tasks in a restricted context, returning output unchanged to the caller without requiring user interaction.

A codex rescue workflow is a controlled process for diagnosing, planning, or applying fixes during system crises. You need a single-task runtime invocation when a crisis requires a deterministic, reproducible step executed safely within a restricted rescue environment.

Yes, executing rescue runtime tasks requires the node-based codex-companion helper and access to the rescue environment. The helper interfaces with the designated task interface to invoke the codex runtime and return the output unchanged.

Instruct the rescue system to issue a single task invocation through the rescue helper. The helper calls the codex-companion runtime, which executes the specified diagnosis, planning, or fix task and returns the unchanged output to the caller.

Yes, the rescue runtime executes tasks in a restricted, isolated context to minimize side effects during rescue sessions. This ensures that deterministic runtime invocations remain safe and auditable when performing crisis operations.

The best approach is invoking the codex-companion runtime via the rescue helper to apply fixes with a single, reproducible step. This deterministic method isolates the operation in a restricted context, ensuring auditable and safe crisis resolution.