Skip to main content
Glama

codex_parallel

Execute multiple codex tasks concurrently to accelerate processing, sharing workspace and permissions while saving results to a specified file with structured XML output.

Instructions

Run multiple codex tasks in parallel. All tasks share workspace/permission/save_file. Results are appended to save_file with XML wrappers (). Max 100 tasks. Model can be array: single element shared by all, or one per task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceYesProject root directory. Boundary for 'workspace-write'. Use absolute paths or relative paths.
permissionNoSecurity level: 'read-only' (analyze files), 'workspace-write' (modify inside workspace), 'unlimited' (full system access). Default: 'read-only'.read-only
save_fileYesPREFERRED when agent needs to write files or produce lengthy output. Output is written directly to this path, avoiding context overflow. This write is permitted even in read-only mode (server-handled). Essential for: code generation, detailed reports, documentation.
report_modeNoGenerate a standalone, document-style report (no chat filler) suitable for sharing.
context_pathsNoList of relevant files/dirs to preload as context hints.
modelNoModel override(s). If single element, all tasks use that model. If multiple elements, must match parallel_prompts length - each task uses corresponding model. Empty array uses CLI default.
imageNoAbsolute paths to image files for visual context. Use for: UI screenshots, error dialogs, design mockups. Example: ['/path/to/screenshot.png']
parallel_promptsYesComplete prompts for parallel execution. Each spawns an independent subprocess.
parallel_task_notesYesLabels for each task. Length MUST equal parallel_prompts.
parallel_max_concurrencyNoMax concurrent subprocesses.
parallel_fail_fastNoStop spawning new tasks when any fails (already running tasks continue).
debugNoEnable execution stats (tokens, duration) for this call.
Behavior4/5

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

With no annotations provided, the description carries full burden and does well at disclosing key behavioral traits: results are appended to save_file with XML wrappers, max 100 tasks, model can be array with sharing options, and tasks run as independent subprocesses. It doesn't mention error handling beyond fail_fast or performance characteristics, but covers the essential execution model.

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 appropriately sized with three sentences that each add value: first states core functionality, second describes output format and limits, third explains model configuration. It's front-loaded with the main purpose and avoids unnecessary repetition. Could be slightly more structured but efficiently conveys key information.

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

Completeness4/5

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

For a complex parallel execution tool with 12 parameters and no annotations/output_schema, the description provides good coverage of the execution model, output format, and constraints. It explains the parallel nature, resource sharing, and key limitations. Missing details about error responses or specific use cases, but covers the essential operational context given the complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 12 parameters thoroughly. The description adds minimal parameter-specific information beyond the schema, mentioning only the model array behavior and XML output format. It doesn't provide additional semantic context about how parameters interact or usage patterns.

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's purpose: 'Run multiple codex tasks in parallel' with specific details about shared workspace/permission/save_file and XML output formatting. It distinguishes from sibling tools like 'codex' (single task) and 'claude_parallel' (different model family) by specifying it's for codex tasks with parallel execution.

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?

The description provides clear context about when to use this tool: for running multiple codex tasks concurrently with shared resources. It mentions the 100-task limit and model configuration options. However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings like 'codex' for single tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shiharuharu/cli-agent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server