Codex support

[muddlebee]

Problem or use case

Integrate Codex CLI

Desired behavior

Proposed solution

No response

Alternatives or workarounds

No response

[evanlhatch]

Can we get opencode too

[evanlhatch]

Can we get opencode too

[rajeevrajeshuni]

Can i pickup this one? @khaong

[akshan-main]

I can take a first pass at Codex support. From my research, Codex already emits a JSONL event stream (thread/turn/item/error events), which seems like the cleanest integration surface to start with.

Proposed scope for an initial PR: support non-interactive runs via codex exec --json.

If we can ingest that stream and write it into the existing session/checkpoint format, we get real value without needing interactive hook support. (Codex stores local state under CODEX_HOME if we ever need to reference per-session artifacts.)

Concrete shape:

• Add entire codex exec -- <codex args/prompt> that runs codex exec --json ...
• Stream-parse JSONL, ignore unknown event types, and persist:
  1. normalized session/checkpoint data (same place/branch as other agents)
  2. raw JSONL as an artifact for debugging and future mapping improvements

Will include tests

Can I take this? @khaong

[akshan-main]

I tried using the wrapper command (entire codex exec) rather than hooks. The wrapper runs codex exec --json, tees the JSONL event stream to capture it, then creates a checkpoint through the existing strategy.SaveChanges() pipeline.

What I did:
Registers a codexcli agent package following the same pattern as claudecode and geminicli (self-registration via init(), full Agent interface, TranscriptAnalyzer, TranscriptChunker)
Streaming JSONL parser that extracts thread ID, messages, commands, file changes, and token usage, made it tolerant of unknown event types, so it won't break when Codex adds new ones
entire codex exec [flags] -- with --model and --sandbox flags
Uses the shared DetectFileChanges, FilterAndNormalizePaths, cleanPromptForCommit, and GetGitAuthor, no new abstractions

Caveat: This is for non-interactive codex exec flow only (not interactive TUI hooks).

Can open a PR immediately if this scope aligns with maintainers’ expectations.
Do you want me to push a PR so you can review? @khaong @Soph @gtrrz-victor

[jaxondk]

Can we get opencode too

#266

[khaong]

Hi, thanks for raising this - we currently have an issue open to make new agent integrations easier #281 - this one would need to come after 🙏

[khaong]

@akshan-main thanks so much for looking into this and motoring ahead! The truth is that we're playing a little bit of catchup on all of this, the interest has been incredible.

Give us a little bit of time to clean up the construction site 😅 - we will get back to you soon 🙏