Feature Request: Markdown formatting in chat input
Use Case
As a developer using Dive as a primary work interface, I frequently need to
mix narrative text with console output, code snippets, and command results
in my chat messages. I use the chat history as a running work log, so
capturing this content inline is important.
Current Behavior
The chat input box is a plain text field. Triple backticks and other markdown
formatting syntax are sent as literal characters with no visual distinction
between narrative text and code/console output.
Expected Behavior
The chat input box should render markdown formatting, specifically:
- Triple backtick code blocks rendered in monospace font
- Inline backtick code rendered in monospace font
- Visual distinction between narrative text and code/console output
Suggested Implementation
Consider replacing the current plain text input with a lightweight markdown
editor such as Monaco Editor or CodeMirror, similar to what other developer
tools use. Even a simple toggle between "plain text" and "markdown" input
modes would be sufficient.
Why This Matters
Developers copying console output from terminals (e.g. MobaXterm, iTerm)
into Dive need visual confirmation that their formatting is correct before
sending. Without this, the chat log becomes difficult to read when mixing
narrative context with technical output.
Feature Request: Markdown formatting in chat input
Use Case
As a developer using Dive as a primary work interface, I frequently need to
mix narrative text with console output, code snippets, and command results
in my chat messages. I use the chat history as a running work log, so
capturing this content inline is important.
Current Behavior
The chat input box is a plain text field. Triple backticks and other markdown
formatting syntax are sent as literal characters with no visual distinction
between narrative text and code/console output.
Expected Behavior
The chat input box should render markdown formatting, specifically:
Suggested Implementation
Consider replacing the current plain text input with a lightweight markdown
editor such as Monaco Editor or CodeMirror, similar to what other developer
tools use. Even a simple toggle between "plain text" and "markdown" input
modes would be sufficient.
Why This Matters
Developers copying console output from terminals (e.g. MobaXterm, iTerm)
into Dive need visual confirmation that their formatting is correct before
sending. Without this, the chat log becomes difficult to read when mixing
narrative context with technical output.