openai / openai/codex

[IDE Extension] Add plain-text modes for messages and the composer

Open
#41,451 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement extension
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

IDE Extension

What feature would you like to see?
Feature request

Please add options to:

  1. Display assistant messages as raw Markdown source instead of rendered Markdown.
  2. Use a plain-text composer that does not apply live Markdown formatting while typing.

Ideally, these behaviors could be configured independently.

Motivation

For programming-heavy workflows, raw Markdown is often easier to read and inspect than rendered output. It preserves the exact structure of lists, indentation, links, and code fences, and makes copying or editing the content more predictable.

Likewise, live Markdown formatting in the composer can be distracting when writing technical prompts. A plain-text input mode would provide a simpler, editor-like experience.

Possible configuration

The exact setting names are only illustrative:

{
  "chatgpt.messageDisplayMode": "markdownSource",
  "chatgpt.composerMode": "plainText"
}

The current rendered Markdown and rich composer behavior could remain the default. This request is only for an opt-in plain-text workflow.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the IDE Extension settings plus the message-rendering and composer entry points. Define two independently configurable opt-in modes, then verify that raw Markdown messages and plain-text composing work separately while the current rendered and rich behaviors remain the defaults.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.