What

ollama run <model> "<prompt>" > out.txt writes terminal escape sequences into out.txt. The file ends up with cursor-control codes (\x1b[<n>D, \x1b[K) instead of clean text.

Fixes #16785

Cause

displayResponse asks for the terminal width and, when term.GetSize fails (which is what happens when stdout is a file or pipe, not a TTY), falls back to an 80-column width:

termWidth, _, _ := term.GetSize(int(os.Stdout.Fd()))
if termWidth == 0 {
    termWidth = 80
}
if wordWrap && termWidth >= 10 {
    // ... emits \x1b[..D / \x1b[K cursor-control sequences for wrapping

So even with no real terminal, the word-wrap branch was taken and its cursor-control sequences were written into the redirected output.

Fix

Word-wrapping only makes sense on a real terminal, so only take that branch when term.GetSize succeeds. When stdout is redirected, fall through to the existing plain-text branch — no escape sequences.

termWidth, _, err := term.GetSize(int(os.Stdout.Fd()))
if wordWrap && err == nil && termWidth >= 10 {

Interactive terminal behavior is unchanged (GetSize succeeds there and returns the real width).

Test

TestDisplayResponseNoEscapesWhenNotATTY redirects stdout to a pipe (not a TTY), renders content that would wrap on a terminal, and asserts the output is the plain text with no escape sequences. It fails before this change and passes after.