jedarden/trail-boss
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(readme): frame Trail Boss as human-on-the-loop / dead-letter queue

Browse source 
Emphasize that agents run autonomously and the human is engaged only by
exception — the failure-mode handler / dead-letter-queue processor for a fleet
of agents, not a gate on every step.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
jedarden 2026-05-24 22:56:59 -04:00
parent f5e66b831c
commit 7650735f18
1 changed files with 16 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
README.md
View file

@ -6,10 +6,20 @@ order — Trail Boss is the single pane where it reports in. You ride over, set
wave it on), and your reply lands back in the exact session — so you stop hand-cycling
terminal windows hunting for whoever's stuck.**
Trail Boss inverts the human-in-the-loop bottleneck. Instead of *you* polling many concurrent
agent sessions to find the one that needs you, each stuck session raises its hand and Trail
Boss presents them as one **prioritized queue — most-stuck first**. Read the context, give the
order (reply), or wave it on (skip).
## Human *on* the loop, not *in* it
Trail Boss turns human-**in**-the-loop into human-**on**-the-loop. Classic agentic HITL wires
you into the inner cycle — approving each step, answering each prompt — so you are the
bottleneck on every iteration. Trail Boss flips it: agents run autonomously by default and you
supervise from above, engaged only by **exception**. When an agent can't proceed on its own —
needs a decision, hits a permission gate, or exhausts its turn — it falls through to you.
Put plainly, **the human is the failure mode.** Trail Boss is a **dead-letter queue for a fleet
of agents**: the happy path never touches you; only stalled work routes to you, you process the
exception (reply or skip), and it goes back on the wire. Instead of *you* polling many sessions
to find the one that needs you, each stuck session raises its hand and Trail Boss presents them
as one **prioritized queue — most-stuck first**. Read the context, give the order (reply), or
wave it on (skip).
```
┌─ TRAIL BOSS ────────────────────────────────────────────── 3 stuck ───┐
@ -41,7 +51,8 @@ periodically stalls waiting on a human:
Discovering those stalls by manually cycling windows is the bottleneck — with N sessions,
most of your time goes to *finding* the one that needs you, not *answering* it, and a session
can sit blocked for minutes while otherwise-parallel work waits. The human is the scarce
resource; the system should route the human's attention, not the other way around.
resource; the system should route the human's attention, not the other way around — engaging
you by exception, not on every step.
## How it works