Desktop App
Codex sessions
Codex sessions route through local Codex CLI, using a separate CLI event/approval path from the default Spatial harness.
Prerequisites
- Install Codex CLI and ensure the `codex` command is available on PATH.
- Select OpenAI Codex in the model picker.
- Keep your CLI authenticated and usable from terminal before troubleshooting in-app.
Supported modes
- Agentic (YOLO), Plan, and Build are supported.
- If your workflow depends on exact mode behavior, validate it in a Codex session before broad rollout.
Harness differences and limits
Codex sessions use Codex CLI transport/events rather than the default Spatial execution harness. This can affect feature parity across advanced runtime behaviors.
- Local CLI sessions may not expose every default harness feature in exactly the same way.
- Hooks and some app-level behavior that depend on internal tool control can be reduced in local CLI sessions.
- CLI protocol/event changes can require app-side adapter updates for full compatibility.