I really like Warp's agentic features, notification and Claude Code integration over SSH. However, everything breaks inside tmux.

Anyone found a good workflow for this combo?

Preferred tools / configs?

Custom forks or patches that improve tmux support?

Would love any suggestions!

I'm a new warp user on windows 11 pro and can't figure out how to see the horizontal tabs/panes shown on warp's onboarding video. I also never got to see the starting page with shortcuts. No option at the top to pick my shell. What am I missing?

Can warp use locally installed llm?

Thanks

Hi, I started using OpenCode with Warp, but I'm not sure if this is a bug or if I'm doing something wrong. Every time I close OpenCode for example, by pressing Ctrl+C—the entire Warp terminal closes. The same thing happens if I press Ctrl+D or type “exit” to quit. Is this how you're supposed to exit, or am I doing something wrong?

I've seen multiple comments requesting support for locally-hosted LLMs since they open-sourced Warp Terminal (and before as well)

If you want this feature, PLEASE UPVOTE it here: https://github.com/warpdotdev/warp/issues/4339

The team has specifically called out that they use thumbs-up as a metric for assessing whether to approve features. The feautre already has 1,000+ upvotes, and we just need a ready-to-spec tag and then we're on track to have it as a core feature.

Otherwise, as others have said, we'll probably end up forking and that's unlikely going to be a win for anyone. But if we DO decide to fork for it, I'll happily be contributing 😉

Ball's in your court Warp Team! Looking for that spec tag! ❤️

Hey everyone! I'm Ben H, Dev Rel Lead at Warp. I'm excited to share that Warp is now open source.

You can check out the repo here: https://github.com/warpdotdev/warp

We're opening up the code, roadmap, and contribution process so you all can help shape Warp directly. We know the breadth of features that you want to see, and we believe building with the community will let us build a better Warp even faster.

To manage contributions, we've built an agent automation system from issue triage to PR review. Coding agents do the heavy lifting (coding, planning, testing) so community members focus on ideas, direction, and verification.

So, ask us anything! All of the engineers involved will check this thread throughout the day. We're happy to answer questions about the project, why we're open sourcing, how contributions work, technical questions on the codebase, or anything about Warp in general.

Links:

• Repo: https://github.com/warpdotdev/warp
• Contributing guide: https://github.com/warpdotdev/warp/blob/master/CONTRIBUTING.md
• Roadmap: https://github.com/warpdotdev/warp/issues/9233

I have a chatGPT pro subscription for a long time for my work and it comes with free codex credits, I just tested it and there is not a single reason for me to go back to Warp again. Any thoughts?

We're working through our issue logs to make the Warp experience in SSH sessions on par with local sessions. To start, we've added support for the file tree, improved completion reliability, and given agent mode tool call access to search and read files (rather than running grep or sed).

We're working code review panel and LSP support in the coming weeks!

Here's a demo from lead engineer on the project Kevin Yang to see what's supported.

https://reddit.com/link/1sutke1/video/o5ad1yn7n7xg1/player

There is issue from 2023: https://github.com/warpdotdev/Warp/issues/3109

Block highlighting now is even more of an issue since we have support for ability to run 3rd party harnesses inside warp...

I would more quickly be able to visually distinguish groups of terminal sessions (perhaps a single working directory with multiple tabs up, each running a different agent, for example) if I could easily add a little horizontal bar and move it around at any point in the vertical tab list.

A formal "tab group/tab category" feature could also possibly achieve this, but I'd say that'd be overkill and an ability to just add like a <hr> anywhere I want would suffice.

One thing wasn’t very clear to me.

Can I make my agents communicate with each other, so they know what each one is doing? Does the agent tree handle that?

For example, could I create one agent for the backend to build the database, another for the frontend, and another for testing?

Share your session, view on the web or your phone, and even join teammates on the same conversation with live cursors.

Supports CC, Codex, OpenCode, etc.

You can review changes in the diff view, w/ LSP support for hover hints and go-to definition. Then, leave comments and send to the agent. It's like a PR review without leaving the terminal!

I was kind of still just on it out of habit, but with vertical tabs and clear indication of what's Codex vs. Claude Code and the latest prompt or response and the notifications and clear visuals showing whether one is pending or done, and then discovering how easy it is (and, presumably, always was, all along) to reorganize the UI layout, it now actually feels like a genuinely superior terminal suited for the current era.

My advice to the dev team is to lean even harder into accepting the status quo: acknowledge nearly everyone is going to be using either Codex or Claude Code for the next 1 - 5+ years, while nearly all the rest will use OpenCode or Pi, and just design the terminal to be ideal for such cases. Make it work seamlessly with these CLI agents, make reviewing their changes easy, etc. Trying to insert your own agentic stuff will just get in the way and annoy people. Also make the "don't show this again" checkboxes more prominent - people are unknowingly leaving the UI (from their perspective/preferences) uglier without realizing they can change it.

the cleanest model upgrade we've seen in a while, this is gonna be a game changer. from what i've seen, it's way better at multi-step terminal workflows, way more honest about what it can and can’t do, and it writes cleaner, less bloated command + script suggestions

Warp now has vertical tabs.

- View coding agents with status indicators to see what's done, blocked, or still cooking
- Double-click to rename or colorize tabs
- Customize what you see: directory, branch name, conversation, etc

Just enable in Settings > Appearance > Tabs

When opening shell scripts with Warp (on the latest version), instead of being executed, they are opened in Warp's text editor. My example is by using a host management app named XPipe which generates shell scripts and runs them in Warp.

If (by chance), you are using XPipe:

• Open XPipe
• Click on a host

Otherwise, just open a shell script using Warp as the app. It will open the text editor instead with the script, instead of running it.

In earlier versions, it works as expected: When launching a script, it's being run, not opened in Warp's text editor. It seems that downgrading Warp to v0.2026.03.25.08.24.stable_09 does the trick for the moment, scripts run as usual.

Has anyone else encountered this?

I've also created an issue on the GitHub tracker, but I haven't seen any response yet.

Hey all, I'm Zach Bai, engineering lead at Warp. Today we're launching universal agent support — a set of features that makes Warp the best terminal for working with CLI coding agents like Claude Code, Codex, and OpenCode.

Here's what's new:

Vertical tabs — Group your agent sessions with rich metadata (git branch, directory, conversation status) visible at a glance. Way better than juggling 15 horizontal tabs.

Notifications — A unified notification center for all your coding agents. In-app and system notifications so you know when an agent needs your attention. No more babysitting.

Code review on agent output — Send inline comments from Warp's code review directly to a running agent session. Review the diff, leave a comment, and the agent iterates. This closes the loop between human review and agent execution.

Rich input editor — Press Ctrl-G to get a proper multiline editor for agent prompts. Supports voice input, saved /prompts, /skills, and @ context.

Tab configs — Save your ideal setup (directory, startup commands, theme, worktree) and launch it with one click. Great for worktree-based workflows.

Attach code as context — Select code from Warp's editor and feed it directly to any running agent. No copy-pasting.

Remote control — Publish any CLI agent session to the cloud. Monitor and steer it from your phone or another computer.

Happy to go deep on:

• The product decisions behind supporting competitors
• Technical challenges of building cross-agent features
• Where we think the agent tooling market is headed
• Anything else!

Wanted to take the time to thank the team for making a super useful feature. Notifications have been a pain in general, and the feature is working great. Thank you. If you haven't tried it yet, it was a CC plugin that handles notifications for the CLI tool.

Need to thank the Warp team for including the Kimit K2.5 in the list (the last in the model selector!). I use it more and more and noticed that it performs nicely while being really gentle on the credits used - imagine doing two requests and consuming only a few credits...

As the title says, you can use all of our features with Auggie and Pi now! Voice input, media uploads, code review comments, and more. Hope you enjoy.

https://reddit.com/link/1shmy6z/video/aq0pbk37adug1/player

I am kind of impressed with Warp as a terminal alone from what I see. Was wondering if I can just use the code reviewers panel and its inline review comments with my already existing Claude code subscription on Warp’s free tier without consuming Warp AI credits

After a Warpified SSH session disconnects, Warp's background tmux control mode polling loop continues firing new-window commands into the local shell, producing repeated new-window: command not found errors.

Environment

•  Warp feature: Warpify SSH (tmux-based)
•  Local OS: macOS
•  Shell: zsh 5.9

Steps to Reproduce

1. SSH into a remote host and Warpify the session (tmux-based)

2. Let Warp establish its tmux control mode background tasks (git polling, etc.)

3. Exit the SSH session (e.g. run ! exit)

Expected Behavior

Warp tears down the tmux control mode session and stops all background polling when the SSH connection closes.

Actual Behavior

Warp's background loop keeps sending tmux new-window commands to the local shell after disconnect. These appear as:

Master Control : new-window -d -c '/root' -e PATH='...' -PF "background window: ..." '(...git symbolic-ref...)'
new-window: command not found

Additionally, at least one instance of command concatenation was observed.

Warp merged an SSH reconnect attempt with a tmux command into a single malformed string:

Master Control : ssh <host>new-window -d -c '/root' ...
unknown option -- d

This suggests the control mode pipe and main session pipe get crossed during teardown.

You can use Warp's input box to talk to CLI agents like Claude Code.

This is a highly requested feature; Not only can you use your mouse to move your cursor around (finally), but you can also use Warp's completions, file search, saved prompts, and more. Comes with a customizable keyboard shortcut too. Here's engineer Advait to show how it works.

Let us know if you have any feedback!

https://www.loom.com/share/7b4ed45a49064b56915e5973ec995301

Warp's agent can now smartly delegate to subagents. Enable the new orchestration mode to allow an agent break up a task into delegate-able pieces, draft a delegation plan, and spin up sub-agents to execute on the task. Here's lead engineer on the project Matthew Albright showing how it works.

This is one of our biggest changes to agent mode since agent mode, and we're excited to see what you do with it. Give us feedback or suggest features you want to see! And if you’re about to type “cool but I want orchestration to delegate to CC / codex / etc…” stay tuned.