codex-cube

name	codex-cube
description	Use Codex Cube bridge commands for deterministic provider routing, JSONL batch execution, and trajectory capture. Use when the user asks for Codex Cube, Hermes-like routing, OpenAI-compatible batch runs, or trajectory JSONL generation.

Codex Cube

Procedure

Use the shell wrapper at plugins/codex-cube/scripts/codex-cube from the repository root. Do not reimplement provider calls inline.

For one prompt:

plugins/codex-cube/scripts/codex-cube route \
  --base-url "$BASE_URL" \
  --api-key-env "$API_KEY_ENV" \
  --model "$MODEL" \
  --input prompt.md \
  --out response.md

For a batch:

plugins/codex-cube/scripts/codex-cube batch run \
  --manifest batch.jsonl \
  --base-url "$BASE_URL" \
  --api-key-env "$API_KEY_ENV" \
  --model "$MODEL" \
  --out trajectories.jsonl

After a batch run, inspect the trajectory JSONL before summarizing results.

Failure Contract

Codex Cube has one deterministic execution path. If a bridge command fails, report the failure plainly. Do not try alternate providers, retries, fallback models, or automatic memory writes unless the user explicitly asks for a later feature that adds those behaviors.

Manifest Contract

Each JSONL manifest line must be one object with either a prompt or input file:

{"id":"task-1","prompt":"Summarize this idea."}
{"id":"task-2","input_file":"prompts/task-2.md"}

IDs must be unique.