Skip to main content
OpenAI Codex is OpenAI’s coding-agent CLI. Like Claude Code, it operates on a real filesystem and doesn’t expose a pluggable backend, so Mirage integrates by FUSE-mounting a workspace and letting you point codex at the mountpoint.

​
Install

uv add 'mirage-ai[fuse]'
Then install OpenAI Codex separately.

​
Usage

from mirage import MountMode, Workspace
from mirage.resource.ram import RAMResource

with Workspace({"/": RAMResource()}, mode=MountMode.WRITE,
               fuse_mounts={"/": True}) as ws:
    print(f"cd {ws.fuse_mountpoints['/']} && codex")
    input("Press Enter when done...")
The mountpoint behaves like a regular directory. Codex’s read_file, write_file, and run_shell tools all dispatch through Mirage’s ops layer.

​
Why FUSE instead of an SDK integration?

The Codex CLI’s tool surface isn’t pluggable, it expects host file operations. FUSE makes those host operations be Mirage operations. You lose per-tool customization and Mirage’s op-record telemetry; you gain zero integration effort and compatibility with every Codex feature. Same trade-off as Claude Code.