List running and completed overseer.nvim tasks (id, name, status), newest first. origin is 'agent' for tasks this server started and 'user' for the ones they started themselves; only clean up your own.

List task templates overseer discovers in a directory (npm scripts, go-task, make, just, VS Code tasks, etc). An empty list is normal (many repos declare nothing runnable); use overseer_run with a raw cmd instead. Each entry has provider (which task runner it came from) and desc, which is null when that provider supplies no descriptions (npm and make never do, go-task and just usually do), so a null desc means there is nothing to read, not that something was withheld. Entries that have a description are listed first. params lists arguments a template takes, with required marking those that overseer_run will reject the call without. running_task_id is present when a task of that name is already running, which is your signal not to start a second one. Pass filter to match a substring against name and desc; worth doing in a large monorepo, where this can return well over eighty entries.

Return a task's live output, preceded by a status line. task is a numeric id or a case-insensitive name substring; omit it for the most recent task. The status line reports status, exit_code once the task has exited, and total (lines available so far), so you never need a separate overseer_list_tasks to find out whether what you are tailing is still alive. Pass the previous total back as since to get only what is new instead of re-reading the same lines; from tells you where the returned block actually starts, and a from greater than since + 1 means output scrolled past between calls. Set wait_for to a regular expression to block until a matching line appears; use it instead of polling repeatedly. It returns as soon as it matches, or when the task exits, or at timeout_ms (default 15000, max 120000), and reports which of the three happened as waited, so a timeout is never mistaken for success.

Start a long-running command as an overseer task, so it appears in the user's task list, can be stopped from it, and inherits proper process-group teardown. Use for commands that DO NOT exit on their own: dev servers, file watchers, --watch test runs, log tails. For short commands that terminate by themselves, use Bash instead: you need their output in-band, and round-tripping a fast build through start-then-poll is worse. Pass exactly one of template or cmd. Prefer template (a name from overseer_list_templates) when one matches what you want; it runs the repo's own definition under the name the user already sees in their task list. Most repos declare no templates, in which case pass cmd as an argv array, which works anywhere. Note a cmd is a one-off, though: gone when the session ends, and the user cannot run it again without you. If they want it to persist, it belongs in a directory-local template instead of being re-passed as cmd every time; the server instructions describe how. cmd does not go through a shell, so for pipes, globs, && or env prefixes pass an explicit wrapper: ["sh", "-c", "..."]. Returns once the task has produced output or exited, up to settle_ms (default 1500, 0 to return immediately), so a command that dies on startup reports its failure here rather than looking identical to a healthy one until some later tail. Templates that declare params need them supplied here; pass params as an object of name to value. A missing required param comes back as an error naming what it wanted rather than a prompt opening in the editor.

Restart a task by id or name substring (stops it first if running). A name matching more than one task is an error listing the candidates; pass a numeric id instead. Running tasks the user started are refused unless force is set.

Stop a running task by id or name substring. Overseer stops the underlying nvim job, so the task's process tree is torn down rather than left orphaned. A name matching more than one task is an error listing the candidates. Running tasks the user started are refused unless force is set, since a substring like 'dev' can match theirs.

Stop (if running) and remove a task from the list by id or name substring. Disposing a finished task is unguarded; a running one the user started is refused unless force is set. A name matching more than one task is an error.