Joclto

Hermes Taskwatch — Productivity skill for Claude Code

Productivity community

Background-task watchboard for the Hermes Desktop app - live roster, silence heartbeat, append-only output view and OS notifications for any terminal agent (claude, opencode, codex...).

How to install Hermes Taskwatch

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Joclto/hermes-taskwatch and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Hermes Taskwatch does

Background-task watchboard for the Hermes Desktop app - live roster, silence heartbeat, append-only output view and OS notifications for any terminal agent (claude, opencode, codex...). Local-only.

Alternatives in Productivity

  • Tradingview MCP — Real-time crypto & stock screening, advanced technical indicators, Bollinger Bands intelligence, candlestick p 2.6k ★
  • Pi Subagents — Claude Code like Sub-Agents & Workflow Orchestration for Pi — parallel execution, live widget, fleet view, cus 967 ★
  • Schedule History — View execution history for all scheduled tasks with interactive selection 510 ★

README

TaskWatch

A background-task watchboard for the [Hermes Agent](https://github.com/NousResearch/hermes-agent) desktop app: every process your chat dispatches through `terminal(background=true)` — **claude, opencode, codex, zcode, a build, a test run, anything** — rendered as a live roster with output tail, runtime, a silence heartbeat and OS notifications.

你派出去的后台编码代理(cc / opencode / codex / 任何终端进程)在干什么、有没有卡死,一块面板看清。

Screenshots

TaskWatch watchboard pane

*The watchboard pane: one row per dispatched background process, with runtime, status and the latest output line.*

Expanded live output

*Expanded row: the append-only live tail — scrollable history while the task keeps running.*

Why

Dispatching a coding agent in the background answers "is it running?" but not **"what is it doing, is it stuck, did it finish?"** — and each agent has its own transcript format. TaskWatch watches at the **terminal-process layer** instead: it renders the gateway's own `process.list` projection for the focused chat, so it is agent-agnostic by construction.

Features

  • Live roster pane — one row per background process: command, runtime, last output line, status dot
  • Silence heartbeat — a running task whose output stops changing shows silent N min; configurable threshold (5/10/20/30 min)
  • OS notifications — task goes silent past the threshold, or exits (success/failure by exit code) → native toast (fires while you are away from Hermes; in-app toast otherwise)
  • Stop button — two-click confirm, goes through the gateway's process.kill verb and only reaches processes the focused chat owns
  • Expandable output — click a row to expand a scrollable view of the most recent 32 KB of output (agent thinking included when the agent prints it to the terminal); mouse-wheel through it while the task keeps running
  • Status-bar chip — runnin