Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
blader avatar

Taskmaster

  • 514 repo stars
  • Updated March 11, 2026
  • blader/taskmaster

Taskmaster is a Codex CLI wrapper and expect-PTY injector that keeps an agent working until it emits an explicit parseable done signal.

About

Taskmaster is a wrapper around the Codex CLI that keeps an agent working until it emits an explicit parseable done signal. It runs Codex with session recording, polls the log for task-complete events, and checks for a TASKMASTER_DONE token. When the token is missing it injects a follow-up message into the same running process over an expect PTY bridge, and stops when the token appears.

  • Codex wrapper plus an expect-PTY injector that keeps work moving until a done signal
  • Uses a parseable TASKMASTER_DONE::<session_id> completion token
  • Polls the session log and auto-injects a follow-up when the token is missing

Taskmaster by the numbers

  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

taskmaster capabilities & compatibility

Capabilities
orchestration · automation · agent continuation
Use cases
orchestration
Platforms
macOS · Linux
From the docs

What taskmaster says it does

Codex wrapper plus same-process expect PTY injector that keeps work moving until an explicit parseable done signal is emitted.
SKILL.md
Taskmaster for Codex uses session-log polling plus automatic continuation.
SKILL.md
TASKMASTER_DONE::<session_id>
SKILL.md
npx skills add https://github.com/blader/taskmaster --skill taskmaster

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars514
Last updatedMarch 11, 2026
Repositoryblader/taskmaster

What it does

Keep a Codex CLI session running until it emits a parseable done token, auto-injecting continue prompts otherwise.

Who is it for?

Driving long-running Codex CLI tasks to a deterministic completion signal.

Skip if: Agents that already expose native writable stop hooks.

When should I use this skill?

You want a Codex session to continue automatically until an explicit, parseable completion marker is produced.

What you get

The agent keeps working with auto-injected follow-ups until it emits the parseable TASKMASTER_DONE token.

  • A Codex run that continues until a parseable TASKMASTER_DONE token is emitted

By the numbers

  • poll interval 1 second
  • version 4.2.0
  • done token prefix TASKMASTER_DONE

Files

SKILL.mdMarkdownGitHub ↗

Taskmaster

Taskmaster for Codex uses session-log polling plus automatic continuation. Codex TUI does not currently expose arbitrary writable stop hooks, so this skill implements the same completion contract externally.

How It Works

1. Run Codex via wrapper: run-taskmaster-codex.sh sets CODEX_TUI_RECORD_SESSION=1 and a log path. 2. Injector parses log events and checks completion on each task_complete event. 3. Parseable token contract: TASKMASTER_DONE::<session_id> 4. Token missing:

  • inject follow-up user message into the same running process via

expect PTY bridge transport, using the shared compliance prompt. 5. Token present: no further injection.

Parseable Done Signal

When the work is genuinely complete, the agent must include this exact line in its final response (on its own line):

TASKMASTER_DONE::<session_id>

This gives external automation a deterministic completion marker to parse.

Configuration

  • TASKMASTER_MAX (default 0): max warning count before suppression in the

stop hook. 0 means unlimited warnings.

Fixed behavior (not configurable):

  • Done token prefix: TASKMASTER_DONE
  • Poll interval: 1 second
  • Transport: expect only
  • Expect payload mode and submit delay are fixed

Setup

Install and run:

bash ~/.codex/skills/taskmaster/install.sh
codex-taskmaster

Related skills

FAQ

How does taskmaster know work is done?

The agent must include the exact line TASKMASTER_DONE::<session_id> in its final response, giving automation a deterministic completion marker.

What happens if the done token is missing?

It injects a follow-up user message into the same running process over an expect PTY bridge using the shared compliance prompt.

Automation & Workflowsagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.