codex-cli-runtime skill should instruct agents to use --prompt-file for shell-safe prompt passing
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- documentation
Research direction
Read skills/codex-cli-runtime/skill.md and the existing --prompt-file handling in codex-companion.mjs, including readTaskPrompt and readStdinIfPiped. Update the skill instructions to use a temporary prompt file rather than positional prompt arguments, and confirm the documented invocation avoids shell metacharacter expansion.
Written by the indexing model from the issue text.
Description
Problem
The codex-cli-runtime skill instructs the codex:codex-rescue subagent to pass task prompts as positional arguments:
node "$CODEX_COMPANION" task "<raw arguments>"
When the prompt contains shell metacharacters (backticks, ${}, (), file paths), zsh interprets them before node receives the argument. This causes the Codex task to fail silently.
Observed errors
(eval):1: permission denied: app/services/results/serial_codes/destroy_service.rb
(eval):1: command not found: find_serial_code
(eval):1: no matches found: .record_limit(count)
(eval):1: parse error near `}'
(eval):1: parse error in command substitution
Root cause
The skill definition (skills/codex-cli-runtime/skill.md) only mentions positional argument passing. However, codex-companion.mjs already supports --prompt-file (line 614, readTaskPrompt function) and piped stdin (readStdinIfPiped).
Suggested fix
Update skills/codex-cli-runtime/skill.md to instruct agents to:
- Write the prompt to a temp file
- Pass it via
--prompt-file /path/to/fileinstead of as a positional argument
This avoids shell metacharacter expansion entirely.
Environment
- Claude Code 2.1.185
- codex plugin 1.0.4
- macOS (zsh)
- Dominant language
- JavaScript
- Stars
- 33.4k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex-plugin-cc
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openai/codex-plugin-cc#766 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openai/codex-plugin-cc#751 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
openai/codex-plugin-cc#704 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
openai/codex-plugin-cc#687 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openai/codex-plugin-cc#676 ·
All issues in openai/codex-plugin-cc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·