dsh-goodjob

Running background jobs, subagents, and multi-turn waits inside DeepSeek Harness often leaves operations scattered across raw logs, event streams, and ad-hoc CLI invocations. There is no unified operations panel to see what is running, what is blocked, and what has changed since you last looked. GoodJob fills that gap: it layers an IDE-style workspace—Explorer, stable tabs, up to four split panes—directly over Jobs, Job Groups, Waits, Subagents, and optional Agent Teams, without introducing a second scheduler, task board, or event bus. Execution still belongs to the DSH capability that started it; GoodJob only projects and operates.

Core capabilities span durable goal tracking with phases and blocked reasons, workflow run and member outcome records, read-only projections of durable reminders with explicit overdue state, deterministic blocker and failure diagnosis, a since-last-visit delta view built from authoritative timestamps, live-preferred session search through DSH's own query engine, exact token accounting from the durable tokenUsage projection, bounded and searchable job log output, full subagent lineage navigation, and agent team roster, task, and mailbox projection when composed. Job Groups provide a compact fan-out / fan-in tool over existing Job ids, and Waits fold wait intents read-only from session events, so complex multi-agent orchestration no longer depends on an external kanban or a third-party state store.

GoodJob is aimed at developers who run multi-task, multi-agent workflows in DeepSeek Harness and need to keep an eye on several background Jobs, trace subagent lineages, and manage durable goals and team states simultaneously. If you want your operations experience to graduate from pure CLI to IDE-grade without standing up a second infrastructure layer, GoodJob is that middle ground.