I frequently want to pipe text through forge -p in shell pipelines and editors. The problem is that forge -p outputs ANSI codes, reasoning blocks, status indicators, and syntax highlighting — all designed for human reading in a terminal. This makes it difficult to use forge as a composable shell tool where only the raw model response is desired.
Use cases this would unlock:
- Shell pipelines:
echo "data" | forge -p "transform this" | jq/awk/sed ...
- Editor integration: Pipe selected text through forge, replace selection with result (Helix, Vim, VS Code, etc.)
- Scripting: Use forge in automated workflows where the output feeds into another program
- Clipboard workflows: Pipe clipboard content through forge, pipe result to clipboard
The forge suggest command already demonstrates this pattern — it outputs clean, pipeable shell commands. Something similar for forge -p would make forge a general-purpose composable tool rather than something that only works well interactively.
I frequently want to pipe text through
forge -pin shell pipelines and editors. The problem is thatforge -poutputs ANSI codes, reasoning blocks, status indicators, and syntax highlighting — all designed for human reading in a terminal. This makes it difficult to use forge as a composable shell tool where only the raw model response is desired.Use cases this would unlock:
echo "data" | forge -p "transform this" | jq/awk/sed ...The
forge suggestcommand already demonstrates this pattern — it outputs clean, pipeable shell commands. Something similar forforge -pwould make forge a general-purpose composable tool rather than something that only works well interactively.