right now it seems that command output from tools is also formatted as markdown, but that makes no sense, as tools probably read outside files or run outside commands, so they shiould just be rendered as they come with fixed line breaks and a fixed font, so they look as if from the terminal. only agent output is rendered as markdown.
right now it seems that command output from tools is also formatted as markdown, but that makes no sense, as tools probably read outside files or run outside commands, so they shiould just be rendered as they come with fixed line breaks and a fixed font, so they look as if from the terminal. only agent output is rendered as markdown.
hugo
added the bug label 2026-07-27 18:47:36 +00:00
Fixed in d371d9d. Tool results now preserve their original line breaks and render in a monospace font in both tool cards and standalone tool messages; assistant responses remain Markdown-rendered. Verified with rustfmt, Clippy, make bundle, and the full 153-test suite.
Fixed in d371d9d. Tool results now preserve their original line breaks and render in a monospace font in both tool cards and standalone tool messages; assistant responses remain Markdown-rendered. Verified with rustfmt, Clippy, make bundle, and the full 153-test suite.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
right now it seems that command output from tools is also formatted as markdown, but that makes no sense, as tools probably read outside files or run outside commands, so they shiould just be rendered as they come with fixed line breaks and a fixed font, so they look as if from the terminal. only agent output is rendered as markdown.
Fixed in
d371d9d. Tool results now preserve their original line breaks and render in a monospace font in both tool cards and standalone tool messages; assistant responses remain Markdown-rendered. Verified with rustfmt, Clippy, make bundle, and the full 153-test suite.