openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > Codex Bridge

Dispatch coding tasks to the local OpenAI Codex CLI with background execution, status polling, and answerable clarifying questions. Use when OpenClaw should...

开发与 DevOps

作者:Abraham Perl @abeperl

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v1.0.0

统计:⭐ 0 · 189 · 0 current installs · 0 all-time installs

0

安装量(当前) 0

🛡 VirusTotal :可疑 · OpenClaw :良性

Package:abeperl/codex-bridge

安全扫描(ClawHub)

  • VirusTotal :可疑
  • OpenClaw :良性

OpenClaw 评估

The skill's files, scripts, and runtime instructions are coherent with its stated purpose of driving a local 'codex' CLI from OpenClaw and do not request unrelated credentials or hidden network endpoints.

目的

Name/description match the code and scripts: the bundle dispatches tasks to a local 'codex' CLI, requires python3 and codex binaries, stores state under ~/.codex-bridge, and manipulates files only within the declared task/workdir scope.

说明范围

SKILL.md instructs the agent to dispatch, poll, ask/answer clarifying questions, and read results. The included bridge.py and helper scripts implement exactly those behaviors. The bridge reads/writes only under ~/.codex-bridge/tasks/<task-id>/ and launches the codex CLI in the specified workdir; it does not access unrelated system paths or external endpoints.

安装机制

No install spec is provided (instruction-only with included scripts). Nothing is downloaded or written outside the skill's own task directory; no unexpected install sources are used.

证书

No environment variables or external credentials are required by the skill. Declared binary requirements (python3, codex) are appropriate for the functionality. Note: the codex CLI itself may require user credentials/config which are outside this skill's scope.

持久

The skill does not request 'always: true', does not modify other skills or global agent settings, and keeps its state under ~/.codex-bridge. It runs background processes for dispatched tasks (normal for this purpose).

综合结论

This skill appears to do what it claims: run the local 'codex' CLI on a project directory and mediate clarifying Q&A via files under ~/.codex-bridge. Before installing, consider: 1) Ensure you trust the local 'codex' CLI and its configuration/credentials (the bridge will invoke it in the chosen workdir and the CLI could read or modify files there). 2) Run the bridge only against project directories you are willing to let the Codex CLI access; …

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Codex Bridge」。简介:Dispatch coding tasks to the local OpenAI Codex CLI with background execution, …。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/abeperl/codex-bridge/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: codex-bridge
description: Dispatch coding tasks to the local OpenAI Codex CLI with background execution, status polling, and answerable clarifying questions. Use when OpenClaw should delegate script building, code edits, refactors, or multi-step coding work to Codex from the command line.
metadata:
  openclaw:
    emoji: "🧰"
    requires:
      bins: ["python3", "codex"]
---

# Codex Bridge

Delegate coding tasks from OpenClaw to the local `codex` CLI and manage them asynchronously.
This skill provides a file-based bridge so OpenClaw can:

- dispatch tasks
- poll status and recent output
- relay clarifying questions
- send answers
- collect final results

## When to Use

- Build scripts (Python, Bash, etc.)
- Implement or refactor code in an existing project
- Run larger multi-file coding tasks in the background
- Delegate coding work while keeping OpenClaw responsive
- Handle tasks that may require clarifying questions mid-run

## When NOT to Use

- Quick factual questions or explanations
- Small code snippets that OpenClaw can write directly
- Non-coding tasks
- Tasks that should not invoke a local coding agent/CLI

## Dispatch a Task

```bash
~/.openclaw/skills/codex-bridge/codex-bridge-dispatch.sh 
  --task-id <descriptive-name> 
  --workdir <project-directory> 
  --prompt "<detailed coding task>"
```

### Prompt Writing

Include:

- what to build/fix
- file paths if known
- expected behavior/output
- language/framework preferences
- constraints (tests, style, no new deps, etc.)

Example:

```bash
~/.openclaw/skills/codex-bridge/codex-bridge-dispatch.sh 
  --task-id scripts-csv-parser 
  --workdir ~/projects/data-tools 
  --prompt "Create parse_orders.py. Read orders CSV, keep shipped rows, group by customer_id, and write summary CSV with columns customer_id, order_count, total_amount. Use pandas. Add basic CLI args and error handling."
```

## Check Status

```bash
~/.openclaw/skills/codex-bridge/codex-bridge-status.sh --task-id <id>
```

Common status commands:

```bash
~/.openclaw/skills/codex-bridge/codex-bridge-status.sh --list
~/.openclaw/skills/codex-bridge/codex-bridge-status.sh --task-id <id> --output
~/.openclaw/skills/codex-bridge/codex-bridge-status.sh --task-id <id> --question
~/.openclaw/skills/codex-bridge/codex-bridge-status.sh --task-id <id> --result
~/.openclaw/skills/codex-bridge/codex-bridge-status.sh --task-id <id> --log
```

## Answer Clarifying Questions

When status is `waiting_for_answer`, read the pending question and send a response:

```bash
~/.openclaw/skills/codex-bridge/codex-bridge-status.sh --task-id <id> --question
~/.openclaw/skills/codex-bridge/codex-bridge-answer.sh --task-id <id> --answer "<answer text>"
```

The bridge resumes the same Codex session after the answer is written.

## Workflow

1. Dispatch task with a clear prompt.
2. Report the task ID.
3. Poll status/output periodically.
4. If status becomes `waiting_for_answer`, read `--question`, relay to user, then write answer with `--answer`.
5. When status is `complete`, read `--result` and summarize outcomes.
6. If status is `error`, inspect `--log` and `--output`.

## Notes and Limits

- Uses the local `codex` CLI (`codex exec` and `codex exec resume`).
- Clarifying questions are implemented via a lightweight text marker protocol in the prompt wrapper.
- Bridge state is stored in `~/.codex-bridge/tasks/<task-id>/`.
- Commands run via Codex in the specified `--workdir`.
- For unattended runs, the bridge times out after 10 minutes waiting for an answer and resumes with a default/sensible fallback.