clawdex

Clawdex

Claude Code plans and reviews. OpenAI Codex executes fast. Browser Use handles the web. Upstash Boxes isolate the compute.

Install

# Codex CLI (bux installs this automatically)
npm install -g @openai/codex

# Or from a Clawdbot session:
/plugin install codex@openai-codex

Verify:

codex --version
claude --version
browser-harness-js --version 2>/dev/null || echo "browser-harness via BUX"

---

Architecture

User prompt
    │
    ▼
Claude Code (claude-sonnet-4-6)   ← you are here: reason, plan, review
    │
    ├── codex exec "..."           ← fast code gen / repetitive tasks
    │
    ├── browser-harness-js         ← web research, UI testing (BUX browser box)
    │
    └── box.exec.command(...)      ← run in Upstash compute sandbox

Each Clawdex run lives in an Upstash Box — ephemeral, isolated, with a box-local Solana wallet and the OpenClawd framework pre-seeded at /work/openclawd-framework.

---

Quick Start

One-shot task (box run)

# Via the box API
POST /api/box/run
{
  "boxId": "your-box-id",
  "prompt": "Build a TypeScript CLI that fetches SOL price from Birdeye",
  "agentHarness": "clawdex",
  "agentModel": "anthropic/claude-sonnet-4-6"
}

Streaming task (SSE)

POST /api/box/stream
{
  "boxId": "your-box-id",
  "prompt": "Audit the pump SDK for rug pull vectors",
  "agentHarness": "clawdex"
}

Shell (PTY mode, bux box)

# Claude Code as the harness, Codex available as a tool
bash pty:true workdir:~/project command:"claude 'Build a DeFi dashboard, use codex for boilerplate'"

# Or dispatch directly to Codex for speed
bash pty:true workdir:~/project command:"codex exec --full-auto 'Generate Jupiter swap wrapper with error handling'"

---

Dual-Engine Dispatch Pattern

Claude Code is the orchestrator. Codex is the executor. Use this pattern:

1. Claude: plan + architecture
2. Claude → codex exec "implement <component>"
3. Claude: review Codex output
4. Claude → codex exec "write tests for <component>"
5. Claude: final review + integration