Herdr 加入了 Y Combinator。其运行时将保持开源。
Herdr is joining Y Combinator. The runtime stays open

原始链接: https://herdr.dev/blog/herdr-is-joining-y-combinator/

Herdr 的独立开发者 Can 已将该项目从一个个人工具发展成为拥有 2.5 万颗星标和 34 万次下载量的广泛应用平台。Herdr 最初旨在解决管理 AI 智能体的“瓶颈”问题,它提供了一个强大的终端运行环境,将终端视为一等公民,使智能体能够在不同环境中持续运行并无缝协作。 由于意识到单凭一人之力已无法维持其快速增长,Can 正在加入 Y Combinator 的 F26 批次,以组建专业的团队。Herdr 的核心运行时已重新授权为 Apache-2.0 协议,以确保其对所有人保持免费和开放。 展望未来,重点仍在于通过丰富的插件生态系统保持核心的精简与可扩展性,同时建立跨机器的连接并增加客户端以支持复杂的工作流。尽管转型为一家公司,其使命依然不变:为开发者提供一种精简、灵活的 AI 智能体管理方式,而不受限于束缚性的专有工具。Can 强调,尽管 Herdr 在不断演进,但其追求简洁、高性能和用户自定义工作流的理念将始终保持不变。

专为管理多个 LLM 代理而设计的终端多路复用器开发工具 **Herdr** 已加入 Y Combinator。尽管创建者宣布其运行时将保持开源,但这一消息在 Hacker News 上引发了关于该项目未来以及风险投资在开发工具中角色的激烈辩论。 许多用户称赞 Herdr 能够追踪代理状态并简化基于代理的工作流程。然而,该公告引发了对“平台腐化”(enshittification)的广泛担忧——人们普遍担心获得风投支持的工具最终会限制功能、优先考虑专有增长,或被迫转向以企业为中心的模式。 讨论中突显了几个相互冲突的观点: * **开源价值:** 开源支持者认为,对于开发工具而言,可检查性和可分叉性至关重要,特别是随着人工智能使用户在项目偏离轨道时更容易维护个人分支。 * **可持续性:** 一些人认为,开源开发者往往难以实现盈利,尽管存在相关风险,但风险投资仍是维持开发为数不多的可行途径之一。 * **“灵感编程”(Vibe Coding)时代:** 许多人认为,由于现代人工智能使得重写或修补代码变得轻而易举,“撤资”或项目变质的威胁已经减弱,因为如果官方版本质量下降,用户完全可以简单地对软件进行分叉。
相关文章

原文

Hey everyone, it’s Can, the only person behind Herdr. This post is about how I decided to change that.

Four months ago I was looking for another job. Thinking about where to go career-wise. Thinking about software engineering and its future in general, my hobby projects, applications, whiteboard interviews (I still can’t believe we do those). And at some point it hit me: I am the bottleneck.

This is a management and engineering problem. I don’t want to install an app or learn a new tool just to manage my agents and my development style. I want something that fits me. You know how every company releases their own agent these days? No, don’t do that. Let my agent integrate with your product, don’t offer me another agent.

Same idea here. I didn’t like what I tried, so why not build it? So I built a runtime. But what is a runtime?

Runtime

CLI coding agents run in terminals, and terminals have always been our home: editing code (yes, nvim chads), running servers, navigating projects, maintaining CI, machines, configurations. It’s the root. It’s the connection. So agents need first class primitives there.

A terminal pane belongs to an agent. A pane belongs to a tab. Tabs belong to a project.

They need to be persistent. We have agents running for hours now, sometimes days. And once you have the runtime, where they run stops mattering. You should be able to run them anywhere and keep them running.

That’s where Herdr was born. But a runtime without an interface is nothing, so: the TUI.

TUI

The TUI is the UI I use every day, and it carried Herdr this far. Not because it’s a UI, but because it shows the concepts Herdr believes in: tracking agents at a glance, dividing work between projects instead of getting lost in a pile of agents, being alerted only when an agent actually needs you.

It also has one big advantage, and it’s the reason it stays first class forever: it’s bundled. Install Herdr on your VPS, ssh in, and your UI is already there. Or run herdr --remote user@host and it installs itself. Depending on your network speed, you’re a couple of seconds away from an agent running. One command and you’re in. Nothing beats that.

Still, the TUI was never meant to be the only client. A runtime means people can build on top of it, and people did! A Raycast extension, a Stream Deck with buttons for herdr, an iOS app that drives a whole session from a phone. More than 500 plugins, one month after the marketplace released. I didn’t build any of these.

The TUI has its limits too. Some of the ideas in my head are hard to build inside a terminal, and I trust terminals, but Herdr will need more clients. More on that later.

Where we are now

So a solo project reached 25k stars and 340k downloads, and it became more than one person can carry.

Herdr is joining Y Combinator, F26 batch. I’m excited to make Herdr a company that builds a developer tool for anyone juggling agents all day. I want to build a small team: people who keep the runtime healthy, robust, fast, running anywhere easily, and more extensible. Letting you do more while Herdr stays small.

The runtime, what you use right now, stays free. Apache-2.0. That’s why I recently switched it from AGPL to Apache: I want everyone to use Herdr freely, without any problem.

Where we’re going

I want to build on top of the open Herdr runtime like everyone else. I’ll keep supporting the open source while building the features people really need. The demand is already visible: multiple clients, a laptop, a VPS for the six hour job, a sandbox for risky code and ephemeral agents. Herdr can run anywhere today, but those machines are disconnected.

It should be connected.

There are many more features in my head, but I don’t want to rush. People keep telling me they love that Herdr stays lean, and that’s what I want to protect. In an age where adding one more feature costs nothing, choosing what goes in the core is the most important decision, I believe. So the core stays small, and everything else stays possible through extensions: your style, your flows, your company’s setup, your themes, your crazy ideas.

Thank you for getting Herdr this far. Thanks for the support, for sharing the love. You have no idea how grateful I am.

Anyway, back to work.

A ram, asleep above the clouds. Or working, hard to tell.

联系我们 contact @ memedata.com