Add setting to automatically prevent pager output in AI agent commands

[johanhallberg]

Pre-submit Checks

• [x] I have searched Warp feature requests and there are no duplicates
• [x] I have searched Warp docs and my feature is not there

Describe the solution you'd like?

Proposed Solution: Add a user setting (e.g., "Prevent pager output in AI commands") that automatically modifies AI-generated commands to avoid pager interfaces by:

1. Adding --no-pager flags to commands that support it (like Git commands)
2. Piping output to cat for commands that don't have no-pager options
3. Setting appropriate environment variables (like PAGER=cat) for the AI command execution context

Examples: • git log → git log --no-pager • git diff → git diff --no-pager
• man some_command → man some_command | cat • less file.txt → cat file.txt

Implementation Notes: This should be a user-configurable setting since some users might prefer pager behavior in certain contexts, but it should probably default to "enabled" for the best AI interaction experience.

Is your feature request related to a problem? Please describe.

Problem: When using Warp's AI agent, commands that trigger pagers (like git log, git diff, less, man, etc.) cause the user to get stuck in a pager interface. When the user presses "q" to quit the pager, the AI agent doesn't receive the actual output, leading to a poor user experience where the AI appears to not have received any response.

Additional context

Benefits: • Seamless AI interaction without getting stuck in pagers • AI agent receives full command output for better context • Eliminates user frustration from pager interruptions • Maintains the full functionality while improving UX

Operating system (OS)

macOS

How important is this feature to you?

4

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

[markgilbert-git]

Agreed, I see this with various commands that trigger output through a pager, like any AWS CLI command that will have a long output, and while I can disable the pager manually, the AI agent doesn't always realise it needs to do this to be able to see the output. Subsequently I see the output in the pager but the agent doesn't and thinks the command ran, but just didn't return anything.

[quincysoul]

+1 super frustrating to just suddenly pause. Needs a universal rule or block for this.

[aaiordac]

I fully agree, this is really annoying. Especially since the agent doesn't see the results in the pager app, and then it thinks it did not get any results !

However I found a workaround: ask the AI agent to pause the pager. For example on Linux: PAGER=cat <cli command>

[dzienisz]

I was so confused when it happened to me. I was thinking, "Am I doing something wrong?" Maybe Warp could wait for the user to copy the file?

[ashishtyagi10]

I cancelled my subscription because we do not have this feature. This should be top priority of the team

[drowssaP]

It seems Agent 3.0 mode may have solved this issue via agent interaction with the terminal?