outdoThe typed task runner for Bun

Tasks live in a typed do.ts — no YAML, no Makefile, no DSL. One-line tasks, compile-time checked deps and steps, schema-validated env and flags, parallel DAG scheduling, caching, CI and git hooks. Zero runtime dependencies.

Get Started

Why outdo?

GitHub

🧠

Typed do.ts, not YAML

A task can be one command string — or a typed object. Autocomplete everywhere, and a dep or step typo is a compile error with a "did you mean" fix. Your package.json scripts are tasks too.

🔐

Env contracts

Declare a zod / valibot / arktype schema per task. Validated before anything runs; outdo --print-env shows which file set every variable.

🎛️

Typed CLI flags per task

Declare flags once — as zod schemas or plain specs, with choices and positional values — and get strict parsing, auto-generated --help, and Tab completion of the values.

🕸️

Parallel DAG scheduler

Independent branches run concurrently with prefixed, multiplexed output. Conditional deps, opt-in retries, timeouts, fail-fast with cooperative aborts.

⚡

Fingerprint caching

Declare inputs and outputs; unchanged tasks are skipped by content hash, deleted outputs come back from the cache, and outdo explain tells you exactly why anything re-runs.

🔌

Services that are actually ready

Readiness probes (log line, TCP port, HTTP health) gate dependents. outdo dev brings your stack up in order — db, api, web.

🌿

Monorepos without turbo

Member package.json scripts become pkg#task, ^build orders packages by their dependencies, and --affected runs only what changed — through both the package graph and the task graph.

🚦

CI, hooks and deploys

outdo ci folds logs, annotates failures and runs only what changed. Git hooks, ssh deploys, Docker layers and a compose preset live in do.ts too.

🛡️

Safe by default

protect and confirm ask before dangerous tasks (and refuse without a terminal), requires checks the stack is up, OUTDO_READONLY keeps unattended runs read-only.

📊

Run reports & traces

outdo build --json emits a full execution report — per-task timing, cache result, critical path. --profile writes a Chrome trace.

🤖

Built for AI agents too

outdo mcp turns every task into a typed tool, an installable skill teaches the agent outdo, and ls --json, --dry=json, explain --json and run reports answer everything else.

Sixty seconds of outdo

installdo.tsrun

bun add -d @meslzy/outdo
bunx outdo init      # scaffolds a starter do.ts

import { defineTasks } from "@meslzy/outdo";
import { z } from "zod";

export default defineTasks({
	fix: "bunx biome check --write", // a task can be one command
	build: {
		desc: "Build the project",
		inputs: ["src/**/*.ts"], // fingerprint cache
		outputs: ["dist/**"],
		run: "bun build src/index.ts --outdir dist",
	},
	test: {
		deps: ["biuld"], // ← compile error: Did you mean "build"?
		run: "bun test",
	},
	gate: { steps: ["fix", "build", "test"] }, // one after another
	deploy: {
		env: z.object({ DEPLOY_URL: z.url() }), // validated before anything runs
		args: { dry: { type: "boolean", short: "d" } },
		protect: true, // asks first; --yes answers
		run: async ({ $, env, args }) => {
			if (!args.dry) {
				await $`./push.sh ${env.DEPLOY_URL}`;
			}
		},
	},
});

outdo                     # grouped task list (package.json scripts included)
outdo build               # run a task + its deps
outdo gate --from build   # part of a task's steps
outdo deploy -d           # typed flags
outdo --watch build       # re-run on change
outdo explain build       # why will it run? what's cached?
outdo --affected test     # only what changed vs the base branch
outdo --json build        # full run report for CI / agents
bunx outdo ci gate        # in GitHub Actions: changed tasks, folded logs, annotations