deniz.in

Markets

Weather

Loading weather

· via Hacker News – Front Page (hnrss.org)

Herdr Studio turns Herdr agent terminals into a browser-based visual workspace

A community-built browser client for the Herdr terminal runtime gives developers one visual view of agent sessions, diffs, worktrees and transcripts across local and SSH-connected hosts.

Herdr Studio turns Herdr agent terminals into a browser-based visual workspace

What launched

Herdr Studio, an independent community project, has appeared on Hacker News' front page, with the listing dated 11 September 2026. It is a browser client for Herdr, a runtime that keeps the terminal sessions of coding agents alive on a machine even when the user's laptop or browser disconnects. Studio turns that runtime into a visual workspace covering terminals, sessions, files, diffs and Git worktrees, accessible from a modern browser.

According to the project's page, Studio deliberately positions itself as a bridge rather than a replacement: agents keep running in real terminal sessions owned by Herdr, and Studio exposes the socket API, terminal streams, files, Git operations and session records to the browser. A running Herdr server is a hard requirement.

What you get

The centrepiece is a single tree of workspaces, tabs, panes and worktrees, with status indicators for each recognized agent showing whether it is working, idle, finished or blocked waiting for input. The stated aim is to let a developer move from a waiting agent straight to the relevant file, diff or transcript, instead of reconstructing context across separate terminal windows.

The terminal itself is presented as a full implementation rather than a log viewer, with streaming output, split panes, scrollback, multi-line paste, clickable links, file previews and IME-safe input. On the review side, changed files can be inspected and annotated — comments attach to diff lines, source gutters or rendered Markdown passages — and the collected feedback can then be sent back into an agent's pane.

Git worktrees get dedicated tooling: they can be created, opened, updated and removed from Studio, with the project saying the source checkout and its dirty files are preserved throughout, plus optional "Paseo hooks" in the worktree lifecycle.

Session history rounds out the feature list. Users can scan agent messages, inspect session metadata, search transcripts, and export either the original session record or a normalized "ATIF trajectory" for supported agents, according to the project page.

How it runs

The setup is described in three steps. First, Herdr owns the agent sessions and keeps them alive through disconnects. Second, a single standalone Studio binary runs alongside Herdr, bridging the local socket API along with terminal streams, files, Git operations and session records; it can connect locally or over SSH to remote Herdr servers, with SSH profiles keeping file and Git views aligned with the remote host. Third, the binary prints a URL that becomes the interface on desktop or mobile, and it can be installed as a PWA.

Availability

Studio ships as a standalone binary for macOS and Linux, with Windows x64 and ARM64 archives on GitHub Releases. The project also leans into mobile use: touch-safe terminal controls, configurable shortcuts and responsive file, diff, pane and session views, with installable PWA support listed for iPhone, iPad, macOS, Chrome and Edge.

Why it matters

As developers increasingly run several coding agents in parallel, the bottleneck shifts from writing code to supervising it — noticing which agent is blocked, reviewing what it changed and stepping in at the right moment. Herdr Studio treats that supervision as the primary workflow rather than an afterthought of terminal management: one tree for the whole fleet, review annotations that flow back to the agent, and session records that can be searched and exported for later analysis.

The architecture matters too. Because agents live in sessions owned by the Herdr daemon and Studio is only a bridge, supervision survives laptop and browser disconnects, and a phone becomes a plausible way to unblock a long-running task. For teams already running agents across local and remote machines, a community-maintained, browser-based interface is a low-commitment way to gain that visibility — though it adds one more moving part, and one more browser-reachable surface, to secure in the development setup.

  • #terminal
  • #developer-tools
  • #ai-agents
  • #git
  • #pwa

Related posts