Skip to content

[FEATURE] Desktop app: make the rendered Markdown preview editable in place #98103

Description

@kat-andres

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

In the desktop app (Code tab), opening a .md file gives a rendered preview that is read-only. To change anything I have to switch to source mode or right-click and "Open in" an external editor.

For a workspace that is Markdown for majority of files (notes, plans, specs, briefs) this is a massive friction point. I would start reading in the preview, and when I have to edit something I need to switch, find the paragraph I was looking at (because switching mode will always bring you back to the top), change it there and then try to not get annoyed by reading in source version. Or I open it in another app right away. Whichever I go for: the flow of reading a doc Claude just wrote and updating it on the spot is impossible.

Other tools in this space (Open AI's desktop app including Codex, Nimbalyst, Notion etc.) treat an editable MD preview view as the baseline. I really enjoy a lot about the Claude desktop app, but still consider switching back to another option like CLI in Nimbalyst to avoid this problem.

macOS, desktop app 2.9939.4.

Proposed Solution

Let the rendered Markdown preview accept text edits directly (WYSIWYG-style, the way the OpenAI desktop app and Codex do), writing back to the file on save with the same Save button / shortcut the source view has today.

Minimum useful version: plain text editing inside paragraphs, list items, headings and table cells, with the Markdown syntax kept on write-back. Rich formatting controls are not needed - MD formatting would work just fine.

Alternative Solutions

  • Source mode with Save. Works, but it is a raw text box, and it is what you switch away from the moment you want to read.
  • "Open in" external editor. Works, but every edit leaves the app, and the request to add custom apps to that menu (Desktop app: allow custom applications in the file-link "Open in" menu (e.g. Typora) #82251) exists mostly because of this gap.
  • Split view (source left, preview right, scroll-synced). Better than today, still two panes for one document.

Priority

High

Feature Category

Desktop app (Code tab) file viewer

Use Case Example

Claude drafts a project brief as brief.md. I open it, read it in the preview, and spot a wrong date in the third paragraph and a bullet that should go. Today: toggle to source, find the paragraph again (position is not kept, see #89155), edit, save, toggle back to read on. Wanted: click into the paragraph, fix the date, delete the bullet, save, keep reading.

Additional Context

Related open issues, none of which is this request:

Activity

  1. jesseparot commented on Sep 29, 2026

    @jesseparot

    @bcherny please can you guys address this 🙏

  2. gjgarryuan commented on Oct 6, 2026

    @gjgarryuan

    Other than the rendered view being read-only, it also lacks the ability to make comments like the raw markdown view supports. It will be great if this can be added along with this feature request.

  3. paragpandyareal commented on Oct 10, 2026

    @paragpandyareal

    Luckily, they came up with a fix for the CLI. Well, sort of a fix. I use the CLI a lot, and jumping back and forth all the time was driving me crazy. I was at my limit, and then mods came along. Yayy

    Mods made it much easier for me to edit the files Claude creates without leaving the CLI. It’s not direct editing though. You click the part you want changed, type what you want different, and Claude makes the edit for you. Then the pane shows you exactly what changed. If your workspace is mostly Markdown, it saves you from switching over to source mode every time.

    Here’s the mod I built to fix my problem.
    https://github.com/paragpandyareal/lazy-panda-panel

  4. kat-andres commented on Oct 10, 2026

    @kat-andres
    Author

    Luckily, they came up with a fix for the CLI. Well, sort of a fix. I use the CLI a lot, and jumping back and forth all the time was driving me crazy. I was at my limit, and then mods came along. Yayy

    Mods made it much easier for me to edit the files Claude creates without leaving the CLI. It’s not direct editing though. You click the part you want changed, type what you want different, and Claude makes the edit for you. Then the pane shows you exactly what changed. If your workspace is mostly Markdown, it saves you from switching over to source mode every time.

    Here’s the mod I built to fix my problem.
    https://github.com/paragpandyareal/lazy-panda-panel

    Appreciate it, but that's not solving the problem for me at all. I am not an Engineer.
    I am absolutely capable of using the CLI and did so for month, but I appreciate a nice looking GUI with good UX. It just feels better to m and I would appreciate this functionality.

    Unfortunately, OpenAI invested a lot more into this side of the story, making the Claude Desktop app feel a little behind - and to me this is the biggest pain point. There are others I'd love adjustmen for - but this one specifically is highest in my list.

  5. kat-andres commented on Oct 10, 2026

    @kat-andres
    Author

    Other than the rendered view being read-only, it also lacks the ability to make comments like the raw markdown view supports. It will be great if this can be added along with this feature request.

    I couldn't agree more - that would be amazing! It sometimes feels weird to being able to do this in the chat, but not in the document that is being worked on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions