Pseudo-terminal will not be allocated because stdin is not a terminal.

[loud marten]

Hi @marsh sorrel. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Based on the information provided in the knowledge sources, it appears that you're encountering an issue related to SSH and pseudo-terminal allocation. This problem is not specific to Warp, but I can provide some insights and potential solutions based on the available information.

The error message "Pseudo-terminal will not be allocated because stdin is not a terminal" typically occurs when trying to run an SSH command without proper terminal allocation. This can happen in various scenarios, including when running SSH commands in scripts or when the input is not coming from an interactive terminal.

To address this issue, you can try the following:

1. Use the -t flag with your SSH command to force pseudo-terminal allocation. For example:

   ssh -t user@host
   

   This flag tells SSH to allocate a pseudo-terminal even if stdin is not a terminal Github Issue #2967 (https://github.com/warpdotdev/Warp/issues/2967).

2. If you're using Warp and encountering this issue specifically with GitHub SSH connections, you can try using the -T flag instead:

   ssh -T github.com
   

   This flag explicitly disables pseudo-terminal allocation and has been reported to work in some cases Github Issue #2967 (https://github.com/warpdotdev/Warp/issues/2967).

3. Check your SSH configuration and ensure that you haven't accidentally disabled PTY allocation in your ~/.ssh/config file.

4. Verify that your shell initialization scripts (like .zshrc) don't contain any commands that might be interfering with terminal allocation Blog post on shell initialization (https://www.warp.dev/blog/what-happens-when-you-open-a-terminal-and-enter-ls#opening-the-terminal-app).

If the problem persists, it might be helpful to:

• Check if the issue occurs in other terminal emulators or only in Warp.
• Review any recent changes to your shell configuration or SSH setup.
• Ensure that your Warp and shell versions are up to date.

If none of these solutions work, you may need to investigate further by examining your shell and SSH configurations in detail. The knowledge sources provided don't contain enough information to give a more specific answer to your particular situation.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

@marsh sorrel Kapa.ai is still learning and improving, please let me know how I did by reacting below.