Yeah I became a fan of Warp when they offered a terminal that treated the input as a normal text input field so I could use my normal keyboard text editing shortcuts.

But I understand that's not a viable business model. I'm back on iTerm2 now cause Warp isn't approved for use at my job (and never would be with all their AI pushing), and I've managed to pound iTerm 2 into something usable enough but I wish every terminal would copy Warp's text input style.

The writing was on the wall from the very start of Warp. I can't remember precisely what happened, but years ago when it was first announced there was something that required internet, or telemetry, or an account to use Warp. I noped out right there before I even tried further. It was always going to be bloatware.

I also felt this way and after staring at the 900MB app package in disbelief started tearing out features using Claude with minimal supervision over the weekend.

It was also a bit of an experiment with a larger Rust codebase, which is outside my usual areas. I did pull out powershell since this was just for personal use on macOS. Been using it today and enjoying it in place of Ghostty, but merely an experiment and learning project:

https://github.com/dxmachina/warp-nine

> Why is every company seemingly trying to re-implement agents themselves rather than making their product work with the existing ones?

Well, i'm trying to do the later, and it is very hard to position the product and differentiate without vertical integration. When Warp owns both agent and the terminal, they can a) give terminal for free and charge on the agent, and b) lock the user in, so it is a good business but poor user experience.

on the other hand, i have to make sure every agent is working which more surface area to maintain, and i'm also limited to the common subset of features. Also it is much harder to convince folks to switch.

Lets try: I support Wezterm (and ghostty, and others) with 40+ different agents (Claude, Codex, etc) in agentastic.dev, would you give it a try?

> Why is every company seemingly trying to re-implement agents themselves rather than making their product work with the existing ones?

You can't raise a $50 million series b on making a nice terminal. we already have lots of nice terminals for free

Warp was so promising to begin with - super clean and polished UI, AI features that actually made sense, really good dev outreach & PR. Over time, they started cramming more and more AI in everywhere, took over half the input area and you could just see there was no coming back. This is why VC backed software will always stink in the end. I use ghostty now.

100% agree. I've ended up building my own [1][2] mostly because I got annoyed the agent cli's are building remote control into the agents, instead of into the terminal. I really want the agent cli's to focus on being the best autonomous agents, then let me choose a great terminal that does all the extra.

Another great option (not mine) is Orca [3] and it's a lot more mature. Really nice to use.

1. https://github.com/markwylde/terminay

2. https://terminay.com

3. https://www.onorca.dev

when i open a new tab in warp now it defaults to their agent and not my actual terminal. i'm going to have to switch back to something else, do you like wezterm?

> Why is every company seemingly trying to re-implement agents themselves rather than making their product work with the existing ones?

Why does any company do anything? Money, of course.

FWIW I use ZSH in Warp daily and never had this problem with ls. Although I have experienced the the agent prediction doing a false positive auto-switch thing a few times.

i keep getting the opposite problem:

> please implement the fix

$ please: command not found

The codex and many other subscriptions can be used with other harnesses like OpenCode and pi. It's officially supported most of the time. Using my Codex and MiniMax sub just fine in pi.

I suspect most developers don’t care too much about cost because they’re just using what their company is just paying for whatever enterprise subscription/billing.

I find it a bit strange that none of the mainstream harnesses have dedicated support for using an agent on another machine/VM on. I understand there is security and permissions limitations, but if I have 30 different VMs, it becomes unmanagable pretty quickly.

Open source fork?

> think of our CLI agent as a built-in mux’er across agent sessions. This allows more natural interactions, like being able to switch directories in agent sessions, have the agent drive full-screen terminal commands (e.g. sqlite and mysql), and even run across ssh sessions with no remote binary install.

Looks like they let you use your LLM of choice on anything your terminal can SSH into using their TUI without having to install Claude Code or their agent on a remote system. Also, you are able to have multiple shell instances as you would on tmux in one session, all with the LLM fully aware of each one (not sure if its a model per session, or multiple, or what).

No guy, this is the one, this is the coding agent that everyone is going to use now, instead of the one that is in the editor or part of their existing ai providers offering.

Docker has an ARR of ~$200mm. They did that by pivoting to a strong focus on developer tooling in 2019 after they nearly went under due to focusing too much on their enterprise infrastructure product.

I would be fine being a business “failure” by that definition.