Support other harnesses (codex, etc.), not just claude

[repalash]

The container is a generic sandbox, but the CLI's conveniences are claude-shaped. Any harness already runs via aibox shell codex (installed durably through ~/.aibox/Dockerfile.extra, with its auth persisting in the aibox-home volume), but:

• The default command, the auto-installer (_ensure_claude_bin), and the --yolo permission-flag logic hardcode the claude binary.
• --copy (disposable snapshot container) only exists on the claude path — no copy sandbox for other harnesses.
• Only ANTHROPIC_* host env vars are forwarded; e.g. OPENAI_* is not.

Proposed direction (from discussion, not final)

A generic escape hatch rather than per-harness commands:

• aibox run <program> [args...] sharing the container/mode plumbing, so aibox run codex --copy works.
• Widen env forwarding beyond ANTHROPIC_* (e.g. OPENAI_*, or a configurable prefix list in ~/.aibox/config).
• Keep --yolo claude-specific — approval flags differ per harness (codex uses --dangerously-bypass-approvals-and-sandbox).
• Possibly a harness=codex config key to change what bare aibox runs.

Deferred for now; capturing so it isn't lost.

[repalash]

First piece landed on claude/lib-revamp-requirements-qm0fh4 (4662e32): generic aibox run [--copy] <program> [args...], with aibox/aibox claude now a thin alias for run claude. So aibox run codex --copy already works.

Still open from this issue: widened env forwarding beyond ANTHROPIC_*, optional ensure-install for other harnesses, and a possible harness= config key for what bare aibox runs.

---

Generated by Claude Code