Hydra Local’s publisher presents its open-source agentic terminal as combining a PTY daemon with browser access, potentially providing a reusable terminal execution interface for agent workflows.
state: corroboratedheat: lowuncertainty: mediumknownscott: lowagent-harnesses developer-toolshydraterm
What is this?
Hydra Local is an open-source 'agentic terminal' published under the handle hydraterm, presented in a Hacker News submission (2026-09-09, 14 pts, 9 comments) as combining a PTY daemon with browser access so coding-agent terminal sessions persist and can be resumed from another machine or phone; the linked GitHub echo merely restates the submission, the only concrete durability claim is one commenter's unverified report of closing the app and resuming elsewhere, and commenter questions vs tmux/Zellij went unanswered. A month later a second, independent implementation of the same pattern surfaced: Agent Guild (Reddit user odd_essentials, 2026-10-07), a PTY-backed local manager running Claude Code, Codex CLI, Antigravity CLI, Grok Build and a shell side by side from one web page, with sessions persisting after close — negligible traction, implementation unverified. This grounding pass found no external corroboration: the web search returned zero results (deadline reached), so everything rests on the case's captured echoes, and neither tool has been depth-verified or shown to expose a reusable programmatic execution interface for agent workflows.
Why it matters to Scott
Scott's canon already holds this exact position — ip:concept.durable-external-state and ip:concept.session-addressability state it, ip:framework.long-running-agents makes the underlying claim (durable state outside the model so work survives session death), dev:concept.resumable-agent-job-control-plane works the implementation problem, and dev:project.ask is his own build of it — so Agent Guild's independent PTY manager is a second low-traction repetition of a held position, not a consequential party newly arriving at it. Until either tool is depth-verified or exposes a reusable programmatic execution interface his agent workflows could actually call, nothing here bears on his implementation choices.
ip:concept.durable-external-stateip:concept.session-addressabilityip:framework.long-running-agentsdev:concept.resumable-agent-job-control-planedev:project.askradar:caffold-cross-device-workspaceradar:rcman-remote-agent-process-managerradar:muxel-multi-agent-terminalradar:captain-miao-terminal-agent-orchestration
queries asked of Scott's wikis
- Ask terminal agent session persistence resumable agent runs across devices
- Give the Agent a Workshop durable execution environment positions
- agent harness reusable shell execution interface tool API design
- running multiple coding agent CLIs side by side orchestration
- tmux Zellij terminal multiplexer prior art in dev tooling projects
- local-first agent compute browser or mobile access to dev environment
Measured heat
now 0 pts/hpeak 1 pts/hcomments 0/hpeers p14momentum: steady3 platformsage 762h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p57 vs 519 stories at the 720h mark (now 762h old) — ahead of ai-agent-ransomware-operation (1.0x), behind openai-daybreak-frontline-subsidies (0.9x)
Evidence (3) — ⭐ canonical anchor
Interpretation history
2026-10-07T19:07:07Z
grounded: known/low — Scott's canon already holds this exact position — ip:concept.durable-external-state and ip:concept.session-addressability state it, ip:framework.long-running-ag
2026-10-07T18:57:52Z
Agent Guild gives the durable, web-accessible agent-terminal pattern a second independent implementation (PTY-backed, sessions survive closing the page), lifting the case from a single tooling lead to early pattern corroboration — but it corroborates the pattern, not Hydra Local's specific capability claims, which still rest on the publisher's description plus one unverified resume-across-devices comment.
2026-10-07T18:32:49Z
evidence attached: reddit.post.1x0296w — Agent Guild is an independent PTY-backed multi-agent terminal manager with persistent sessions, corroborating spread of the reusable agent-terminal pattern.
2026-09-10T06:34:13Z
A commenter now reports leaving an agent running after closing the app and resuming the same session from another device, giving Hydra Local a concrete continuity claim beyond its publisher’s description. This is unverified testimony with unknown independence, not yet evidence of operational reliability or a reusable agent execution API.
2026-09-09T22:33:14Z
The reobservation adds no substantive evidence: the GitHub echo restates the publisher’s submission rather than independently verifying the implementation. Hydra Local remains a tooling lead, with no demonstrated reusable agent interface or operational advantage that would change Scott’s implementation choices.
2026-09-09T22:27:54Z
grounded: known/low — Scott already builds shell-executing agents in “Ask terminal agent” and argues for capable execution environments in “Give the Agent a Workshop ebook”; Hydra Lo
2026-09-09T22:23:29Z
case created — The linked implementation is a distinct harness artifact, but the title-only observation establishes neither session durability nor operational reliability.
Decision trace
- 10-08 06:11attention_routeThe editor compared this story and chose to keep watching.
- 10-08 06:07attention_candidatematerial_reprice
- 10-08 06:07repriceAgent Guild gives the durable, web-accessible agent-terminal pattern a second independent implementation (PTY-backed, sessions survive closing the page), lifting the case from a single tooling lead to
- 10-08 06:07groundScott's canon already holds this exact position — ip:concept.durable-external-state and ip:concept.session-addressability state it, ip:framework.long-running-agents makes the underlying claim (du
- 10-08 05:57review_reactivatedAgent Guild gives the durable, web-accessible agent-terminal pattern a second independent implementation (PTY-backed, sessions survive closing the page), lifting the case from a single tooling lead to
- 10-08 05:42attention_routeThe editor compared this story and chose to keep watching.
- 10-08 05:32attention_candidateattach
- 10-08 05:32attachAgent Guild is an independent PTY-backed multi-agent terminal manager with persistent sessions, corroborating spread of the reusable agent-terminal pattern.
- 10-08 05:28propose_attachAgent Guild is an independent PTY-backed multi-agent terminal manager with persistent sessions, corroborating spread of the reusable agent-terminal pattern.
- 10-02 22:59review_dormantscheduled targets exhausted or 28 quiet days
- 10-02 22:59drop_targetsquiet through full ladder or over cap 8
- 09-12 02:41review_screenThe changes add questions comparing Hydra Local with existing tools and asking about session scope, but introduce no verified new fact or consequential evidence; the continuity claim was already prese
- 09-10 16:34repriceA commenter now reports leaving an agent running after closing the app and resuming the same session from another device, giving Hydra Local a concrete continuity claim beyond its publisher’s descript
- 09-10 16:34alert_silentCross-device session continuity is a useful capability lead, but the unsupported comment does not establish an implementation advantage that changes Scott’s choices today. It can wait for a regular br
- 09-10 16:34alert_routeCross-device session continuity is a useful capability lead, but the unsupported comment does not establish an implementation advantage that changes Scott’s choices today. It can wait for a regular br
- 09-10 16:21sensor_dirtycomment_update
- 09-10 09:21sensor_dirtyengagement_update
- 09-10 08:33repriceThe reobservation adds no substantive evidence: the GitHub echo restates the publisher’s submission rather than independently verifying the implementation. Hydra Local remains a tooling lead, with no
- 09-10 08:33alert_silentThere is no new release, capability evidence, or consequential adoption to surface. The existing publisher-described tooling discovery can wait for a regular briefing; adjacent topic heat does not est
- 09-10 08:33alert_routeThere is no new release, capability evidence, or consequential adoption to surface. The existing publisher-described tooling discovery can wait for a regular briefing; adjacent topic heat does not est
- 09-10 08:32alert_silentThe publisher presents Hydra Local as an open-source terminal combining a PTY daemon and browser access. That is relevant tooling discovery, but the supplied evidence shows no distinctive execution in
- 09-10 08:32alert_routeThe publisher presents Hydra Local as an open-source terminal combining a PTY daemon and browser access. That is relevant tooling discovery, but the supplied evidence shows no distinctive execution in
- 09-10 08:27groundScott already builds shell-executing agents in “Ask terminal agent” and argues for capable execution environments in “Give the Agent a Workshop ebook”; Hydra Local’s publisher-described terminal is an
- 09-10 08:23createThe linked implementation is a distinct harness artifact, but the title-only observation establishes neither session durability nor operational reliability.