API discovery: NousResearch's Hermes Agent has added live_transcripts to its public delegate_task contract. Each child receives a pre-created, append-only log under a local delegation cache, and the dispatch response returns the paths before the batch finishes. The project’s delegation guide documents the intended move: follow a selected task with tail -f while the parent continues working, then receive the consolidated result through the normal path.
Try it
Use it for a three-way engineering check: one child runs a focused test, one traces a suspected regression, and one audits a public API change. If the test worker is quiet longer than expected, inspect only its local transcript for the last tool call or error instead of pulling every child event into the parent context. The public implementation says the live log is a side channel and keeps it separate from message content; it also records a small manifest with task goals and statuses.
Copy-paste agent instruction
Delegate these three tasks in parallel: run the focused test, inspect the suspected regression, and review the API change. After dispatch, return the live_transcripts paths and a one-line description of each task. Do not paste transcript contents into the parent conversation by default. If I ask to inspect one task, tail only that local log, summarize the latest tool call or result, and stop before sharing any credential, private path, or sensitive tool output.Test caveat
This is a local Hermes tool contract, not a hosted monitoring API. It depends on the local installation, configured model/provider credentials, filesystem access, and the active runtime backend; the documentation is not a rate-limit, uptime, or cross-backend guarantee. The logs can include goals, assistant text, thinking snippets, tool calls, and tool results. Hermes truncates displayed fields, but that is not a universal redaction promise—inspect before sharing, and test the behavior in a safe local session before relying on it for sensitive work.