Improve Codex CLI input UX: multiline editor-style composer and voice-to-prompt workflow

Resolved 💬 2 comments Opened Apr 2, 2026 by cn3m0 Closed Apr 2, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

The main usability bottleneck in Codex CLI is no longer the terminal window itself, but the input field.

I tested terminal-side improvements such as WezTerm and zellij. They work technically, but they do not materially improve the actual prompt-writing experience. The core issue is prompt composition inside Codex CLI.

What is missing:

  • comfortable soft-enter / multiline writing
  • better editing of long prompts before sending
  • draft-style prompt composition
  • markdown-first writing experience
  • smoother image / clipboard insertion
  • a more editor-like interaction model instead of raw shell-style input

What would help:

  • soft-enter for newline, separate send shortcut
  • embedded multiline markdown composer
  • lightweight editor-like UX inside CLI/TUI
  • draft mode before sending
  • ability to revise larger prompts comfortably
  • support for inserting clipboard images or temporary image attachments before send

A useful direction would be a small markdown editor embedded into Codex CLI/TUI. Not a full IDE, but a real composition surface for human-AI collaboration.

The next level would be voice-to-prompt support.

A good reference is whis:
https://github.com/frankdierolf/whis

It supports terminal-oriented voice-to-text flows such as:

whis --as ai-prompt --print

That kind of pattern would be very valuable in Codex CLI:

  • speak
  • transcribe
  • optionally post-process into an AI prompt
  • insert into the Codex composer
  • review/edit before sending

That would improve both:

  • editor-like prompt composition
  • speech-to-text input for terminal AI workflows

In short: the biggest UX gain is likely not more terminal tooling, but a much better input/composer model inside Codex CLI itself.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #16404
  • #16111
  • #15682
  • #15612

Powered by Codex Action

etraut-openai contributor · 4 months ago

Thanks for the suggestions. I think that most of these are already captured in other feature requests, so I'm going to close this. Please upvote existing feature requests. If you see some aspect that's not captured elsewhere, feel free to open a new feature request, but don't combine multiple features or suggestions in a single request.