Denshin for Codex

Keep Codex in motion from your phone.

Read exposed agent output, inspect patches and child runs, then use native controls when Denshin owns the App Server thread.

Codex work represented in the Denshin agent view
CodexPassive rollout plus managed App Server mode
Raw terminal always available

What the adapter can actually show.

Each primitive states where its fidelity comes from. Denshin does not fill gaps with invented provider data.

Mode dependent

Conversation

Passive sessions derive exposed history from rollout data. App Server sessions stream native messages.

Mode dependent

Work

Native thread plans and todos are available only in managed App Server mode.

Mode dependent

Changes

Passive mode derives patch results. Managed mode receives native change events.

Native

Runs

Child-agent delegation retains provider identity in both supported Codex paths.

One run. Three moments.

  1. Choose the ownership modelAttach to an existing rollout, or let Denshin create and control an App Server thread.
  2. See only real capabilityEvery surface reflects the active mode instead of presenting false parity.
  3. Keep the escape hatchOpen the raw PTY whenever the provider surface is incomplete or you want direct control.

Let Codex work while you move.

Join the pilot