---
type: "post"
slug: "herdr-packages-parallel-coding-agents-as-an-open-runtime"
title: "Herdr Packages Parallel Coding Agents as an Open Runtime"
description: "herdr owns the terminals coding agents run in, keeping panes alive after a disconnect and marking each one working, blocked or idle so a stuck agent is visible."
retrieval_nugget: "herdr owns the terminals coding agents run in, keeping panes alive after a disconnect and marking each one working, blocked or idle so a stuck agent is visible."
published_at: "2026-08-14"
updated_at: "2026-09-12"
record_date: "2026-08-14"
date_kind: "discovered_at"
topics: ["open-source","coding-agents","orchestration"]
entities: ["Herdr"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:herdr-packages-parallel-coding-agents-as-an-open-runtime"
status: "published"
source_urls: ["https://github.com/herdrdev/herdr"]
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:35054d928e427bd381e1a8694934aab8eb1772ae6061e29d5fb7e1d2eb84d25c","reviewed_at":"2026-09-12T10:00:00Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":1,"watch_condition_count":1,"related_record_count":3}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"herdr describes itself as the runtime coding agents live on, and its scope is deliberately narrow: it does not wrap or replace Claude Code, Codex, Cursor, opencode or Grok, it owns their terminals.","observed_facts":[{"text":"herdr keeps terminals running in a background server after the client closes or an SSH connection is lost.","source_urls":["https://github.com/herdrdev/herdr"]},{"text":"Agents drive herdr through a CLI and socket API, spawning panes, prompting each other and waiting until another agent is blocked.","source_urls":["https://github.com/herdrdev/herdr"]}],"mechanism":"Panes keep running in a background server when the client closes or an SSH connection drops, and after a machine restart herdr restores the saved layout and can resume supported agent sessions, while being explicit that the original processes do not survive.","why_now":"Every pane carries a state — working, blocked or idle — so when an agent stops and needs an answer, herdr says so instead of leaving a human to notice a quiet terminal.","implications":["That turns blocked into a coordination primitive rather than a UI hint, which is what parallel agent work actually needs."],"evidence_boundary":"This is repository documentation: it describes behaviour and installation without reliability data or a list of which agent sessions actually resume.","watch_conditions":["The condition to watch is whether resumable sessions are enumerated per harness, because a runtime that restores layout but silently loses one agent's state is harder to trust than one that admits it cannot resume."],"related_records":[{"url":"https://newruntime.com/posts/local-coding-agents-are-becoming-shared-workspaces","relation":"Prior coverage of local agent work becoming a managed workspace."},{"url":"https://newruntime.com/posts/the-coding-agent-workbench-is-becoming-a-product-layer-of-its-own","relation":"Prior coverage of the workbench product layer."},{"url":"https://newruntime.com/topics/agent-harness","relation":"Topic hub for harness and runtime design."}]}
routes: {"html":"https://newruntime.com/posts/herdr-packages-parallel-coding-agents-as-an-open-runtime/","markdown":"https://newruntime.com/posts/herdr-packages-parallel-coding-agents-as-an-open-runtime.md","json":"https://newruntime.com/posts/herdr-packages-parallel-coding-agents-as-an-open-runtime.json"}
---

# Herdr Packages Parallel Coding Agents as an Open Runtime

## Retrieval answer

herdr owns the terminals coding agents run in, keeping panes alive after a disconnect and marking each one working, blocked or idle so a stuck agent is visible.

herdr describes itself as the runtime coding agents live on, and its scope is deliberately narrow: it does not wrap or replace Claude Code, Codex, Cursor, opencode or Grok, it owns their terminals. Panes keep running in a background server when the client closes or an SSH connection drops, and after a machine restart herdr restores the saved layout and can resume supported agent sessions, while being explicit that the original processes do not survive.

Two design choices make it more than a multiplexer. Every pane carries a state — working, blocked or idle — so when an agent stops and needs an answer, herdr says so instead of leaving a human to notice a quiet terminal. And agents themselves drive herdr through a CLI and socket API: they can spawn panes, prompt each other, and wait until another agent is genuinely blocked. That turns blocked into a coordination primitive rather than a UI hint, which is what parallel agent work actually needs.

Making the terminal a managed surface is the same consolidation as [local coding agents becoming shared workspaces](https://newruntime.com/posts/local-coding-agents-are-becoming-shared-workspaces/) and [the coding-agent workbench becoming its own product layer](https://newruntime.com/posts/the-coding-agent-workbench-is-becoming-a-product-layer-of-its-own/). The [agent harness hub](https://newruntime.com/topics/agent-harness/) tracks that layer.

This is repository documentation: it describes behaviour and installation without reliability data or a list of which agent sessions actually resume. The condition to watch is whether resumable sessions are enumerated per harness, because a runtime that restores layout but silently loses one agent's state is harder to trust than one that admits it cannot resume.