Make it compatible with Codex CLI

[arita37]

Thanks
If you can make it compatible with Codex CLI,
it would be nice.

[stephenleo]

Thanks for the request! I looked into this and unfortunately it's not feasible yet — and the blocker is on Codex CLI's side, not cship's.

How cship works: Claude Code spawns cship as an external command, pipes session state as JSON to stdin, and renders cship's stdout into the statusline. cship needs the same contract from any host.

Where Codex CLI stands: Codex has a built-in statusline (/statusline + tui.status_line config), but it only lets you toggle/reorder a fixed set of built-in items — it does not support an external command-backed statusline (pipe JSON to your program, render its output), which is exactly what cship requires.

The feature is requested upstream but unshipped. All the "command-backed statusline like Claude Code" requests were closed as duplicates of one still-open tracking issue:

• 🟢 Open tracking issue: openai/codex#16921 — Allow custom status line plugins
• 🔴 openai/codex#20043 — Support external command-based status line with ANSI colors, similar to Claude Code (closed as duplicate)
• 🔴 openai/codex#20140 — command-backed/custom statusline rendering (closed as duplicate)
• 🔴 openai/codex#20244 — Custom command-backed TUI status line or colored status banner (closed as duplicate)

There's no merged or open PR implementing it yet.

Good news: cship's architecture (JSON-in → ANSI-out) is provider-agnostic, and Codex's proposed payload (model, cwd, session_id, context stats, rate limits) overlaps heavily with cship's existing context struct. So once openai/codex#16921 ships, adding Codex support should be a small data-mapping layer rather than a rewrite.

I'll keep this issue open and revisit when Codex enables command-backed statuslines. 👍