Herdr raises $6M to put a team behind its solo agent runtime

Bessemer led the seed round as founder Can Celik turns Herdr's open-source runtime for persistent coding agents into a developer-tools company.

By · Published

Primary source: Herdr

Why it matters

Long-running coding agents need persistence, status tracking and remote control outside any single model vendor's interface. Herdr's round backs that runtime layer while testing whether open-source adoption can support a durable developer-tools business.

An illuminated, holographic terminal displays a dynamic open agent runtime with many small, glowing software agents interacting within a sophisticated digital system.

Can Celik (@cancelik) has raised a $6 million seed round for Herdr, the open-source runtime he built to keep fleets of AI coding agents running after engineers close their laptops or lose an SSH connection.

Herdr's announcement on X

Herdr said Bessemer Venture Partners led its $6 million seed round, with Y Combinator, e2 and several angel investors participating. The company announced the financing on September 8, one month after joining YC's Fall 2026 batch.

The round turns a fast-growing open-source project into Celik's attempt to build a lasting developer-tools business. YC still lists Herdr as a one-person operation. Celik wrote in August that he was "the only person behind Herdr," and his funding announcement makes hiring the immediate use of the capital.

From job search to agent runtime

Four months before joining YC, Celik was looking for another job. He had previously built AI-assisted ultrasound technology and led AI teams in fintech, according to YC. His LinkedIn profile lists Bilkent University and work at Kontist, the German fintech acquired by Ageras.

Celik's own use of multiple coding agents pushed him toward Herdr. Existing agent managers imposed their own interfaces and workflows, he wrote in Herdr's YC announcement. Celik wanted agents to remain inside the terminal, where engineers already edit code, run servers, inspect logs and manage remote machines.

He also found himself repeatedly checking which agent had finished, stalled or needed permission to continue. Herdr grew from that bottleneck. A background server owns each terminal session while clients attach and detach from it. The running work stays alive when a terminal closes or a network connection drops.

Herdr's agent documentation shows how Celik has extended that basic terminal-multiplexer model. Herdr organizes sessions by agent state, including working, blocked, idle and done. Scripts and other agents can control sessions through a command-line interface and local socket API.

The architecture lets Herdr support the agent tools engineers already use rather than tying the runtime to a proprietary model or coding assistant. Herdr is distributed under the Apache 2.0 license, and Celik says the runtime will remain open after the financing.

A control layer for agents that keep working

Herdr occupies a narrow layer between terminal multiplexers and full agent workspaces. Tools such as tmux and Zellij preserve terminal sessions, while products including Conductor, Emdash and Superset provide interfaces for managing concurrent coding work, isolated worktrees and review queues.

Herdr's comparison page frames those products as adjacent tools. Celik is betting that engineers need a lower-level runtime that owns real terminals and understands agent state. Worktree managers and review interfaces can sit above it. Virtual machines, containers and sandbox wrappers can provide isolation around it.

That distinction matters as coding sessions stretch from a few prompts into hours of autonomous work. Engineers supervising several agents need to know which session requires attention without opening each terminal. They also need the work to survive a disconnected client, particularly when agents run on remote servers or desktop machines left online overnight.

Herdr's August YC post reported 25,000 GitHub stars, 340,000 downloads and more than 500 community plugins; the company has not disclosed customers, revenue or paid-user counts in the supplied materials.

Celik has described connecting the machines running Herdr as a next step. The project is designed to run across laptops, VPSs and other environments while keeping the core runtime small and open.

The seed round buys people

The financing gives Celik room to turn Herdr's early adoption into an organization without closing the source code that attracted its users. In August, he said he wanted a small team focused on keeping the runtime healthy, fast, portable and extensible.

Hiring is the harder part of that transition. Herdr's adoption has run ahead of its staffing, leaving product development, maintenance and community demands concentrated on one founder. The work includes releases, compatibility, performance and support across operating systems and agent interfaces.

Bessemer's investment places a substantial seed check behind the view that persistent agent execution will become its own infrastructure category. Celik now has to convert developer enthusiasm into a product people will depend on for long-running work, while keeping Herdr useful to engineers who never become paying customers.

Herdr began because Celik concluded that he was the bottleneck in his own agent workflow. A month after joining YC, the bottleneck has moved. The code has users and capital. Celik now has to hire the people who can keep up with both.

Reader comments

Conversation for this story loads after sign-in.