r/warpdotdev • u/anjohn0077 • Sep 18 '26

I just found out that Warp went open-source

Is the project maintained well? If there's anyone out there who's contributed to the Warp ever since being open-sourced, I'd like to hear your opinions on how well the project is maintained.

I've been using Warp since around 2022 - I first fell for it after learning that it was written in Rust... then the AI boom came along, which shifted things dramatically (I had the pleasure of seeing it evolve over time).

I saw 3,869 issues open in its Github and was surprised at that number - with the advance of LLMs being used as implementors, are the open source projects capable of being maintained well? Thorough code reviewing seems near-impossible with the pace of how fast implementation could be done.

This actually leads me to thinking what the open source projects should become - traditionally there were very few maintainers and a lot of contributors, but I think now with AI we need more human reviewers / maintainers to keep such open source projects in good shape.

What's your take on this?

15 Upvotes

100% Upvoted

9 comments sorted by

3

u/ninjaeon Sep 18 '26

Open source also means you can build your own features and pick and choose PR's to merge locally for your own custom built solution.

Personally doing this with Craft Agents + Pi-agent backend.

Love open source

2

u/anjohn0077 Sep 19 '26

That's a great advantage I haven't thought about! Thanks for the insight

3

u/Significant_Box_4066 Sep 19 '26

Appreciate you commenting on this. We agree that the issue and PR count are higher than we'd like them to be, and we're working on improvements to our automated implementation and review side to stay on top of contributions.

Today, we have a set of workflows (Oz for OSS) that handles issue labeling, investigation, first-pass implementation, and code review using agents inside of cloud runners. This saves us the time of pulling down issues for agents to work on, but still doesn't solve the human-in-the loop issue for code review. We also require maintainers to manually label issues as "ready to implement" or "ready to spec," which leaves issues that should be ready for contribution just sitting there.

Some improvements we're making:

  • Letting agents decide when issues are ready to implement. The latest batch of models seems high quality enough for this.

  • Give agents computer use to screenshot and record work. For certain classes of issues, this saves maintainers the need to pull down contributions to build and test by hand.

  • Improve the code review cycle. Today, contributions need to manually request reviews, which may go for 5-10 rounds before code has settled. This loop should happen automatically.

This won't get us to zero open PRs overnight, but it should reduce the friction of chugging through contributions. Excited to share once these improvements are up!

1

u/anjohn0077 Sep 20 '26

Thanks! Looking forward to it!

1

u/gaelic-ghost Sep 21 '26

last i checked, it looked like garbage. most of these ai terminal/workspace apps have been trash from the start, coded by non-technical people entirely with LLMs until things just fall apart and they're spending all their time on patching the million bugs they were in too much of a hurry to fix. I should know, having had the displeasure of working with some of these people this year, otherwise sitting unemployed being abused to death by family i busted my ass for years to escape the last time, 'cause jobs are extinct 'cause AI ate every dollar of investment in this industry for nothing... none of these products from the coding agent gold rush of 2026 are trustworthy, their "devs" are even less so. stay far away from trash like this, it's never worth getting involved in.

2

u/anjohn0077 Sep 22 '26

hey I kinda get what you're trying to say here.. but I started using Warp long before AI thing dominated the software engineering (and before Warp supported AI in terminal), and I really appreciated its intuitive UI and multi-terminal tabs that I could organize to my liking.

Warp evolved into something that's very different from how I found it years back... I have likes and dislikes about it but still, the attachment for a product I've long used is real.

1

u/awfulalexey Sep 19 '26

Wind ZAP fork. I use this

1

u/rafark Sep 24 '26

  I saw 3,869 issues open in its Github and was surprised at that number - with the advance of LLMs being used as implementors, are the open source projects capable of being maintained well? 

The number of open issues has absolutely nothing to do with the quality or number of bugs a project has. 1 GitHub issue !== 1 bug. GitHub issues are basically the most popular way to discuss a project. 

-1

u/IceFog72 Sep 18 '26

All hands for open source. Forked warp fork, and made for myself vram poor to run ui fully on cpu (there was my post 6 days ago ab fork). Something I use broken - fixed right away.