Improve Markdown Preview and Document Editing Experience
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
codex app
What feature would you like to see?
I’d like to suggest several improvements to the file preview and editing experience in Codex:
-
Display images directly in Markdown preview
When a Markdown file contains image references, I would like the preview to render and display the actual images directly, instead of only showing the image path or link.
This would make Markdown preview much more useful, especially when working with documentation, reports, technical notes, and other files that contain screenshots or diagrams.
-
Support opening and editing DOCX files directly
Currently, DOCX files cannot be opened and edited directly in Codex.
It would be very helpful if Codex could support opening, viewing, and editing DOCX files directly, similar to working with Markdown or other document formats.
This would significantly improve workflows that involve business documents, reports, specifications, proposals, and other Microsoft Word files.
-
Consider the product experience of WorkBuddy
I would also suggest taking a look at WorkBuddy’s product features and overall user experience, especially its file handling, document preview, and editing workflows.
Some of its interaction patterns may be useful references for improving the document-related experience in Codex.
Overall, I hope Codex can provide a more complete document workspace experience, where users can preview rich content properly and directly open, edit, and work with commonly used document formats without having to switch between multiple applications.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the Markdown preview and document editing entry points, then split the request into image rendering, DOCX support, and product-experience research with separate acceptance criteria for each.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100