3 posts tagged with "agent"

When you're managing a fleet of development environments across a network, the transport layer isn't just plumbing — it's the nervous system. Every heartbeat, every command dispatch, every metrics payload depends on it. We needed something that was real-time, resilient, and could degrade gracefully when the network couldn't cooperate.

We chose ASP.NET SignalR as the primary transport, with REST polling as automatic failover. Here's why, and exactly how it works under the hood.

You've got thresh running on a couple of machines. Maybe it's a home lab with a few Linux boxes, or a team with workstations scattered across a network. Either way, you've hit the point where SSH-ing into each node to check on things doesn't scale.

That's exactly what Thresh Hub solves. In this post, we'll walk through real-world fleet patterns — from a simple two-node setup to a multi-team deployment with dedicated mid-tier routing.

Release Date: March 8, 2026
Release Type: Feature Release — Phase 1.6

Thresh 1.6.0 is here, and with it comes the biggest architectural leap since we went cross-platform: agent mode. Every thresh node can now connect to a centralized Thresh Hub over a persistent WebSocket connection, giving you fleet-wide visibility, real-time metrics, and a single pane of glass for all your environments.