Congrats to Can on the pre-seed funding. genuinely wishing you all the best.
The terminal multiplexer / multi-agent coding space is getting very crowded. YC alone has funded many competing startups in this space: herdr, Superset, cmux, Emdash, Orca, Bullet, Conductor (Conductor was in YC before pivoting from chat->coding). I’m probably missing a few, and that’s before counting companies outside YC such as Superlogical and Agentastic.dev (by yours truly).
One thing I find particularly interesting is the role of open source in this market.
A lot of these products started open source (i assume as a tactical way to gain traction and build a community). But after the early traction phase or raise funding, the incentives seem to change.
Being open source by itself is not a product differentiator in this market. The features required for string positioning (orchestration, cloud, custom agents, enterprise features, hosted infrastructure, etc.) often end up either closed source or available only through the hosted product.
That makes me wonder how much developers actually value OSS for this category. How much does it matter to you whether your IDE or coding environment is open source?
Is OSS important because you want to inspect the code, fork it, self-host it, avoid vendor lock-in, or simply because you trust open-source developer tools more? Or, for desktop software like IDEs is open source mostly a nice-to-have rather than a requirement? So I’m curious where HN lands on this
There exist also competitors not funded by YC, like me. I won't be on any of the lists because I'm not courting agents, I'm courting humans.
For me OSS is a weapon to be wielded. By making perfect software that cannot be improved upon, and making known my ownership of it, I'm am defending "embrace extend extinguish" attacks that would otherwise be damaging to me. Those attacks rely on being to undercut a product's position in the market with a similarly positioned product that can be just slightly better and/or cheaper.
Indeed and once the funding comes in with more chefs in the kitchen the startups start losing touch and focus on funneling users to a platform instead of just improving the core product.
The copyleft licenses are toxic for adoption. Companies default away from them because there are a lot of murky unknowns (e.g. if you run a copyleft service and connect to it via API, is that extending it? Does that service’s source have to be shared?) that simply aren’t worth the hassle.
If you want your library to get traction with many real world use cases, you need to have a permissive license. If you want to stick to the principles, you’re going to sacrifice adoption.
Not saying one is better than the other, but there’s a tradeoff.
I'm not sure why you're being downvoted, you're right. Using software that has requires people to contribute back is a huge liability, and hurts adoption, which is the most important metric for herdr right now.
You can totally make profits by selling services based on AGPL code btw, it's completely fine. As long as you redistribute your derivative work as AGPL too.
There's nothing toxic in the AGPL for you as long as you don't want to make that code proprietary (even without making profits)
No. There's no restriction of usage in the (A)GPL. Anyone, including big corps, can use AGPL software. Preventing them to use the software is not the point neither. The point is trying to ensure end user freedom.
They just choose avoid agpl software. Their loss. Unfortunately they also spread FUD on this and many commenters here happily convey it.
AGREED! Its sheer insanity to call the AGPL toxic. The license is actually quite simple if a little wordy. They should have accompanied it with a preamble that was super clear and to the point.So here it is in our 170 words for you to read, share, and use:[28]
Copyright (c) [year] [copyright holders]
Permission is hereby granted to any person obtaining a copy of this software and associated documentation files, to use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software, including for commercial purposes, subject to the following conditions:
If you distribute this software, or any work derived from it, you must release the complete source code under this same licence. If you modify this software and users interact with your version over a network — as a web application, an API, or a hosted service — you must offer those users the complete source code of your version, at no charge. All copies must include this copyright notice and this licence. You may not impose additional licence restrictions beyond this.
These permissions are irrevocable and royalty-free for the term of copyright. THE SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND. This is a plain-language summary. The full legal text of the GNU Affero General Public License, version 3, governs all use for you.
Same rights. Same freedoms only a little more opiniated delivery. Same business card. The only difference: when someone takes your code, tweakes it and builds a service on it, the tweaks, the improvements must come back.
Seems like the path is to use LLMs to launder code from VC funded efforts and their public codebases into codebases with a copyleft license. Otherwise you have to wait for the rug pull before taking action (Terraform and Vault->OpenTofu and OpenBao). It is fair use to train and create derivative works after all, as courts have ruled so far.
You can just take someone else's permissively licensed code and relicense it AGPL, or even proprietary if you want to. Corporations want it proprietary but the same trick works for copyleft.
For bonus points make sure your fork has better SEO than the original, so when someone who heard it's permissive embeds it in a proprietary product, you can sue them.
I don’t know that this qualifies as enshitification… on one hand, the author created something that scratched his own itch, shared it, and now it’s become a tool that he wishes to steward into a way where he can make money.
I don’t know that these are terrible things inherently, it kind of depends if he wishes to extract as money as possible from his users by any means necessary or if he’s truly trying to scale it so it can help people. All we have is this article and infinite speculation.
I personally didn’t find herdr useful, so I have no stake in the direction of what the author decides to do with herdr.
In my cynical view, herder now seems to be an attempt to commercialize tmux by adding superficial polish. I am wary of VC backed developer tools that seek to innovate in well established open source niches. Herdr by default is mouse focused, has very friendly UI interactions, and has some niche UI support for agents running in panes. Great. Now it also has a profit motive and ROI pressures. I don't see this ending well.
If he wants to make money he needs to sell licenses, not give them away for free. To that end, making the free version AGPL is generally a good move. It ensures people can get hooked on your product and when they start working at corporations they have to pay to keep using it.
This extends way beyond the superficial toxic license stuff. There is a lot of legal ambiguity around copyleft licenses and most companies just don't want to deal with it unless it's absolutely unavoidable.
No, of course not, they're your friends. They even have a ping pong table and a smoothie bar. It's like in the Soviet Union, everyone's a comrade, nobody's a boss
Congrats to Can! I am using Herdr and i think its a great tool. A modern solo dev success story , very inspirational.
I see some negative comments here that I could understand why funding scares them when it comes to their open source tool but like.. atleast congratulate the guy.
Yeah I was using cmux but it was Mac only and now I run herdr on my wsl and tunnel in from Mac and it’s awesome that it just mirrors everything. I like it and congrats to the founder
As a relatively recent herdr user, I’ll say (1) congratulations and (2) the thing that was most attractive was the seeming orthogonality of the tool. It sits apart, interfaces with subordinate programs in a few clearly delineated ways, and integrates them only as much as the user desires. Critically, “no integration just show me the terminal output of my program” is an option, and a useful one!
I appreciate that discipline and respect for your user in the current tool, and hope to be a paying customer of a similarly values-aligned business you’ll build on top of it!
I started noticing problems with MCP auth state failing inside herdr, but working in a normal terminal session or with tmux, so I switched back to using tmux and it's been flawless. I also noticed that herdr was causing errors/warnings in ordinary terminal sessions so it's more trouble than it's worth at the moment (at least for me). It's a shame though, since I otherwise think it's a good tool.
Over the last year I ended up duct taping a lot of functionality onto tmux to get what these new age multiplexers set out to do (session launch, live agent status, etc). And it works, but it definitely feels like duct tape.
I'm not sure the tmux project wants to evolve to support this natively so for now herdr seems like one of the best open and forkable options available. Considering how little I've had to really touch my tmux setup after getting it going I don't think it's necessarily the worst thing in the world if the FOSS community maintains a deshittified fork of herdr, should it come to that.
I am going to be PRing herdr to stagex as it is my daily driver. This will give it a totally independent release process with multiple parties bootstrapping, reproducing, and signing deterministic binaries for it alongside our tmux releases.
We (the stagex team) will naturally patch out any corpo tracking bullshit that may or may not happen in the future, and follow the dominant community fork should it be needed, as we did with terraform -> opentofu.
As long as herdr does not enshittify though, we will be happy to provide very high supply chain integrity releases for it as-is starting with probably next months stagex release.
Absolutely no problem with FOSS developers finding revenue streams to give themselves more resources to make their projects better.
My own company is 100% FOSS with nothing held back and will stay that way, even though we are in the current YC batch with more customers signing every week. Admittedly this is atypical, but it can be done.
I've been using Herdr for a while now, but I'd like a multiplexer that's also a meta-harness that I can connect to remotely. I know others have setups that work, I just haven't quite figured it out yet.
I switched from tmux to Herdr about six weeks ago. It's a great bit of software, the UI is focused on switching between multiple agents quickly. I run Herdr to keep my opencode instances well managed, and it also works great for having a few terminals opens next to your agent. I find myself keeping opencode sessions open for longer like what happens with Codex and Claude code, which is great if I need to revisit a context to do some follow up work. I'm genuinely excited to see if the creators can bring even more value to the application.
If you're worried about enshittification I wouldn't be. It's relatively basic open source software that runs locally. A perfect candidate for a fork if the base app starts degrading.
I am a HUGE herdr fan - discovered it a few months ago and it's exactly what I need for my workflow. Thousands of others have discovered it as well, which is awesome.
I have such mixed feelings about this - YC means VC means commercialization means enshitification. I really wish that weren't the case, but it so very often is.
Here's hoping this one's different...
(PS I am a big YC fan in general! I don't mean to sound anti-YC or anti-VC or anti-capitalism. But when it comes to low-level essential development tools, I'll never forget what happened to Warp, which started out as such a nice clean terminal project and turned into an absolute money-chasing mess.)
It’s literally the VC playbook, the whole point of the funding is to undermine competitors with subsidized/free products and then raise prices/enshittify. Anyone who thinks it’ll be different this time is fooling themselves.
> YC means VC means commercialization means enshitification
It doesn't have to be that way. YC partners are supportive if you just want to take the YC funding and nothing more, keeping the team small and just focusing on making the product better for customers. Indeed YC advises against taking VC if you don't need it.
I can't tell if this is sarcasm but in case its not, being capable of doing something and having the desire and resources to do it are not the same thing
Wow, congrats! Can you discuss how you got YCombinator to select your open source project? I know they sometimes fund open source… I’ve been building several large platforms since 2011 but I have never considered applying like that.
Quick question: Would you have actually donated to Herdr if they were asking for donations? I don't think any of you would have, unless stated otherwise.
So this is another reason why developers do not pay for their tools and instead the developers of these tools go to VCs anyway. It's not the fault of the author, but most of the users (developers themselves) always want their tools for free at $0.
You have to pay and support the tools you use or else the VCs will do it for you so you can't complain when scenarios like this keep happening.
I don't love this framing among software developers. This framing is very transactional, when many of the authors are explicitly trying to make their work free. The best thing a software dev can do is donate some of their time to do more open source development, and in that way we all benefit from having more and better open source tools. If someone wants to exchange code for money there are plenty of avenues to do that. Starting an open source project and using it to attract VC funding is one path.
> I don't love this framing among software developers. This framing is very transactional, when many of the authors are explicitly trying to make their work free.
This software was "free" (as in libre) and costed $0 and until now, it was licensed under AGPL 3. But contrary to one common misbelief in open source and free software, the maintenance is not free at all.
> The best thing a software dev can do is donate some of their time to do more open source development, and in that way we all benefit from having more and better open source tools. If someone wants to exchange code for money there are plenty of avenues to do that.
In the case of this project which took off, why would you expect the maintainer to work on the project for free?
When I moved to herdr I specifically looked for a donate / purchase button on their website and it wasn't anywhere to be found (at least in a prominent location).
I gladly donate / pay subscriptions to software I use regularly... but the company has a responsibility to make it obvious on how to do so
> Are you lamenting the death of proprietary UNIX and paid compilers, too?
You are straw-manning a point no-one made. Herdr is open source and if the users would like to see it maintained for a long time, they would donate $$$. Clearly the donations were no-where enough and raising money was.
The point is maintaining open source projects for free is NOT sustainable and most HNers in this thread clearly struggle with not understanding that.
> This status quo is fine.
Seems like you would want him to work for free, then wait until the author becomes demotivated and then he abandons the project entirely and we'll see a new post about why Herdr got abandoned.
Yep. It's funny how much open source maximalists harm their own cause. Everything must be "free", ergo everything must be VC or big tech backed because free doesn't put bread on the table, so in the end devs just put more power in the hands of corporations and less power in the hands of themselves and other independent devs/small businesses, and then have the gall to complain when everything gets enshittified.
The terminal multiplexer / multi-agent coding space is getting very crowded. YC alone has funded many competing startups in this space: herdr, Superset, cmux, Emdash, Orca, Bullet, Conductor (Conductor was in YC before pivoting from chat->coding). I’m probably missing a few, and that’s before counting companies outside YC such as Superlogical and Agentastic.dev (by yours truly).
One thing I find particularly interesting is the role of open source in this market.
A lot of these products started open source (i assume as a tactical way to gain traction and build a community). But after the early traction phase or raise funding, the incentives seem to change.
Being open source by itself is not a product differentiator in this market. The features required for string positioning (orchestration, cloud, custom agents, enterprise features, hosted infrastructure, etc.) often end up either closed source or available only through the hosted product.
That makes me wonder how much developers actually value OSS for this category. How much does it matter to you whether your IDE or coding environment is open source?
Is OSS important because you want to inspect the code, fork it, self-host it, avoid vendor lock-in, or simply because you trust open-source developer tools more? Or, for desktop software like IDEs is open source mostly a nice-to-have rather than a requirement? So I’m curious where HN lands on this
For me OSS is a weapon to be wielded. By making perfect software that cannot be improved upon, and making known my ownership of it, I'm am defending "embrace extend extinguish" attacks that would otherwise be damaging to me. Those attacks rely on being to undercut a product's position in the market with a similarly positioned product that can be just slightly better and/or cheaper.
I'm curious what the actual problems with AGPL were.
If you want your library to get traction with many real world use cases, you need to have a permissive license. If you want to stick to the principles, you’re going to sacrifice adoption.
Not saying one is better than the other, but there’s a tradeoff.
Being toxic to greedy corporations but beneficial to everyone else is the point of the GPL licenses.
There's nothing toxic in the AGPL for you as long as you don't want to make that code proprietary (even without making profits)
They just choose avoid agpl software. Their loss. Unfortunately they also spread FUD on this and many commenters here happily convey it.
Copyright (c) [year] [copyright holders]
Permission is hereby granted to any person obtaining a copy of this software and associated documentation files, to use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software, including for commercial purposes, subject to the following conditions:
If you distribute this software, or any work derived from it, you must release the complete source code under this same licence. If you modify this software and users interact with your version over a network — as a web application, an API, or a hosted service — you must offer those users the complete source code of your version, at no charge. All copies must include this copyright notice and this licence. You may not impose additional licence restrictions beyond this.
These permissions are irrevocable and royalty-free for the term of copyright. THE SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND. This is a plain-language summary. The full legal text of the GNU Affero General Public License, version 3, governs all use for you.
Same rights. Same freedoms only a little more opiniated delivery. Same business card. The only difference: when someone takes your code, tweakes it and builds a service on it, the tweaks, the improvements must come back.
For bonus points make sure your fork has better SEO than the original, so when someone who heard it's permissive embeds it in a proprietary product, you can sue them.
I don’t know that these are terrible things inherently, it kind of depends if he wishes to extract as money as possible from his users by any means necessary or if he’s truly trying to scale it so it can help people. All we have is this article and infinite speculation.
I personally didn’t find herdr useful, so I have no stake in the direction of what the author decides to do with herdr.
https://opensource.google/documentation/reference/using/agpl...
This extends way beyond the superficial toxic license stuff. There is a lot of legal ambiguity around copyleft licenses and most companies just don't want to deal with it unless it's absolutely unavoidable.
https://forklog.com/en/former-coinbase-employee-accused-of-c...
https://techcrunch.com/2026/06/26/corgi-the-buzzy-y-combinat...
No, of course not, they're your friends. They even have a ping pong table and a smoothie bar. It's like in the Soviet Union, everyone's a comrade, nobody's a boss
https://youtu.be/fQlJE7ABNu4
I see some negative comments here that I could understand why funding scares them when it comes to their open source tool but like.. atleast congratulate the guy.
I appreciate that discipline and respect for your user in the current tool, and hope to be a paying customer of a similarly values-aligned business you’ll build on top of it!
I'm not sure the tmux project wants to evolve to support this natively so for now herdr seems like one of the best open and forkable options available. Considering how little I've had to really touch my tmux setup after getting it going I don't think it's necessarily the worst thing in the world if the FOSS community maintains a deshittified fork of herdr, should it come to that.
We (the stagex team) will naturally patch out any corpo tracking bullshit that may or may not happen in the future, and follow the dominant community fork should it be needed, as we did with terraform -> opentofu.
As long as herdr does not enshittify though, we will be happy to provide very high supply chain integrity releases for it as-is starting with probably next months stagex release.
Absolutely no problem with FOSS developers finding revenue streams to give themselves more resources to make their projects better.
My own company is 100% FOSS with nothing held back and will stay that way, even though we are in the current YC batch with more customers signing every week. Admittedly this is atypical, but it can be done.
If you're worried about enshittification I wouldn't be. It's relatively basic open source software that runs locally. A perfect candidate for a fork if the base app starts degrading.
I have such mixed feelings about this - YC means VC means commercialization means enshitification. I really wish that weren't the case, but it so very often is.
Here's hoping this one's different...
(PS I am a big YC fan in general! I don't mean to sound anti-YC or anti-VC or anti-capitalism. But when it comes to low-level essential development tools, I'll never forget what happened to Warp, which started out as such a nice clean terminal project and turned into an absolute money-chasing mess.)
Genuine question - why?
It won't be.
It doesn't have to be that way. YC partners are supportive if you just want to take the YC funding and nothing more, keeping the team small and just focusing on making the product better for customers. Indeed YC advises against taking VC if you don't need it.
VC funding can enshitify things but it can also improve them. Here’s hoping for the latter.
Would something like this qualify:
https://github.com/Qbix
https://github.com/Intercoin
https://github.com/Safebots/Safecloud
So this is another reason why developers do not pay for their tools and instead the developers of these tools go to VCs anyway. It's not the fault of the author, but most of the users (developers themselves) always want their tools for free at $0.
You have to pay and support the tools you use or else the VCs will do it for you so you can't complain when scenarios like this keep happening.
This software was "free" (as in libre) and costed $0 and until now, it was licensed under AGPL 3. But contrary to one common misbelief in open source and free software, the maintenance is not free at all.
> The best thing a software dev can do is donate some of their time to do more open source development, and in that way we all benefit from having more and better open source tools. If someone wants to exchange code for money there are plenty of avenues to do that.
In the case of this project which took off, why would you expect the maintainer to work on the project for free?
I gladly donate / pay subscriptions to software I use regularly... but the company has a responsibility to make it obvious on how to do so
You are straw-manning a point no-one made. Herdr is open source and if the users would like to see it maintained for a long time, they would donate $$$. Clearly the donations were no-where enough and raising money was.
The point is maintaining open source projects for free is NOT sustainable and most HNers in this thread clearly struggle with not understanding that.
> This status quo is fine.
Seems like you would want him to work for free, then wait until the author becomes demotivated and then he abandons the project entirely and we'll see a new post about why Herdr got abandoned.