casp

What problem does it solve?

This Skill provides a deterministic JSONL proxy that spawns codex app-server and exposes an orchestration-friendly event stream. It enables programmatic control of Codex workflows, auto-handling approvals, forwarding tool calls, and mining sessions across multiple threads.

Core Features & Use Cases

• Spawns and manages codex app-server as a subprocess, with a handshake (initialize -> initialized) and an experimentalApi: true flag.
• Reads and writes JSONL messages over stdin/stdout to drive Codex and stream events in a structured, routeable form.
• Auto-accepts approvals and forwards server-initiated tool requests to the orchestrator, returning responses deterministically.
• Useful for orchestrating multi-threaded Codex experiments, automating tool calls, and building reproducible sessions via thread/turn metadata.

Quick Start

Use the casp skill to start the proxy and drive Codex:

• Start: node scripts/casp_proxy.mjs from the casp skill directory (example: node ~/.dotfiles/codex/skills/casp/scripts/casp_proxy.mjs).
• Optional: pass --cwd /path/to/workspace to control where codex app-server runs and where .casp/state.json is written.
• Wait for a casp/ready event.