taskplane
AI agent orchestration for pi — parallel task execution with checkpoint discipline
Description
AI agent orchestration for pi — parallel task execution with checkpoint discipline
Release History
| Version | Changes | Urgency | Date |
|---|---|---|---|
| 0.28.4 | Imported from npm (0.28.4) | Low | 4/21/2026 |
| v0.28.4 | ### Fixed - **Settings TUI:** Agent Extensions section shows "Toggle extensions per agent type" instead of generic "Read-only collection/record fields" label. | High | 4/21/2026 |
| v0.28.3 | ## New - **Forward project and global extensions to spawned agents (#511, #513):** Third-party pi extensions from `.pi/settings.json` (project and global) are now forwarded to worker, reviewer, and merge agents as explicit `-e` flags alongside `--no-extensions`. - New `settings-loader.ts` reads and merges packages from both settings files - Per-agent-type exclusion config: `taskRunner.worker.excludeExtensions`, `taskRunner.reviewer.excludeExtensions`, `orchestrator.merge.excludeEx | High | 4/21/2026 |
| v0.28.2 | Sage review remediation for v0.28.1 dashboard fixes: - **#488:** Step label uses V2 snapshot whenever present, even when checkbox totals are 0 - **#493:** Segmented progress bar no longer shows current wave as 'done' during merge - **#494:** Running tasks with stale 0-total sidecar data show 'executing...' instead of '0%' - **#499:** `deleteBatchState` uses workspace root in ALL paths (manual, supervisor, PR lifecycle via `buildCiDeps`) | Medium | 4/14/2026 |
| v0.28.1 | **9 fixes:** - **#487:** Stale STATUS.md viewer clears when new batch starts - **#488:** Lane step label updates on every poll - **#491:** Succeeded tasks show 100% and 'Complete' - **#493:** Wave indicators only green for completed waves during merge - **#494:** Segment-scoped progress for non-final segments - **#497:** Supervisor recovery actions show context/detail descriptions - **#498:** Merge telemetry associated with correct wave - **#499:** `integratedAt` written to batch history before | Medium | 4/14/2026 |
| v0.28.0 | **Phase A: Segment-scoped worker visibility** Multi-repo polyrepo tasks now support `#### Segment: <repoId>` markers in PROMPT.md steps. Workers only see their segment's checkboxes, complete them, and exit cleanly — no more cross-repo confusion or supervisor intervention. - **TP-173:** Discovery parser extracts step-segment mappings - **TP-174:** Lane-runner filters prompt, progress, stall detection per segment - **TP-175:** Worker prompt + skill updated with segment marker guidance - **TP-176 | Medium | 4/14/2026 |
| v0.27.0 | **11 bug fixes** closing #441, #446, #451, #452, #453, #454, #455, #457, #458, #296, #425 **Segment lifecycle (TP-165):** .DONE no longer created prematurely after first segment. Expansion requests consumed correctly at segment boundaries. Worker agent ID resolution fixed for workspace mode. **Wave planner (TP-166):** Phantom waves eliminated. Global lane cap enforced in workspace mode. **Init (TP-167):** Windows backslash paths normalized to forward slashes. **Cleanup (TP-168):** Telemetry | Medium | 4/13/2026 |
| v0.26.1 | **orch-integrate already-merged detection:** When the supervisor resolves conflicts manually, calling `/orch-integrate` afterward now detects the orch branch is already merged and runs cleanup only (deletes branch, clears batch state, moves to history view). Previously it failed with 'branches have diverged'. **Supervisor primer fix:** Supervisor now explicitly instructed to call `orch_integrate()` after manual conflict resolution. **Dashboard:** Human-readable labels for recovery actions (e.g | Medium | 4/11/2026 |
| v0.25.8 | Follow-up fixes from Sage code review of TP-164 merge agent live telemetry. - Fix telemetry precedence: merge snapshots are now the unambiguous primary source for merge telemetry (no conditional override logic needed since merge agents don't write JSONL) - Fix terminal snapshot status: a successful merge that gets a clean-exit kill now correctly shows 'complete' rather than 'failed' - waveIndex: added optional param to spawnMergeAgentV2, threaded through from both call sites so snapshot metad | Medium | 4/11/2026 |
| v0.25.7 | **TP-163 (fixes #471):** ENOENT crash when task folders exist on disk but aren't committed before running `/orch`. The staging commit now fast-forwards the orch branch so worktrees see the new files. Includes Sage-reviewed hardening: CAS-style ref update to prevent branch rewind in multi-wave batches. **TP-164 (fixes #465):** Merge agents now show live telemetry (tool calls, cost, context %, elapsed time, last tool) in the dashboard MERGE AGENTS pane during the merge phase, instead of showing n | Medium | 4/11/2026 |
| v0.25.6 | Follow-up fixes from Sage code review of the TP-157/158/159 batch. **TP-157:** Fixed peer fallback path in `resolveTaskplanePackageFile`. Previous path ascended only one level from pi's package dir, landing in `@mariozechner/taskplane` (scoped, non-existent). Now correctly ascends to `node_modules/taskplane` (unscoped). **TP-158:** Added `paused` to the reload-skip phase check in `doOrchStart`. A paused batch is resumable — its config must not change mid-run. **TP-159:** After `markOrphansCra | Medium | 4/11/2026 |
| v0.25.5 | **TP-157:** Consolidated all npm/package path resolution into `path-resolver.ts` — fixes macOS resolution reliability across nvm/Homebrew/volta/custom-prefix setups. **TP-158 (fixes #460):** `/orch` now reloads config from disk before starting a batch, so config files created mid-session are picked up immediately without restarting pi. **TP-159 (fixes #461):** Ghost worker detection — orphan processes (silent subprocess death) are now detected each monitor poll cycle and marked crashed immedia | Medium | 4/11/2026 |
| v0.25.4 | Follow-up to the #472/#474 macOS fixes based on Sage code review.\n\n**Fixed:** `agent-host.ts resolvePiCliPath()` used `require('child_process')` inside an ESM module for the `npm root -g` call. In true ESM, `require` is undefined; the `try/catch` swallowed the error silently, leaving dynamic resolution as dead code. This could cause engine-hosted agent spawning (workers, mergers) to fail on nvm/volta/custom-prefix macOS setups — the same class of failure as #472/#474.\n\n**Also:** Added cachin | Medium | 4/10/2026 |
| v0.25.3 | **Bug fix:** Two functions in the review spawning path (`resolvePiCli` and `loadReviewerPrompt`) had hardcoded path lists that missed `/opt/homebrew` and had no `npm root -g` fallback. On macOS with Homebrew, the pi CLI couldn't be found, the reviewer failed to spawn, and all reviews were silently skipped with UNAVAILABLE. Fixed with the same robust resolution pattern used elsewhere in the codebase. | Medium | 4/10/2026 |
| v0.25.2 | **Bug fix:** Reviews were silently skipped on macOS when the base `task-worker.md` template couldn't be located due to npm PATH resolution failures (common with nvm/Homebrew in non-interactive shells). Workers would run without the review_step instructions and skip all reviews regardless of review level. Fixed by using the robust `resolveTaskplanePackageFile()` path resolution in `loadBaseAgentPrompt()`. | Medium | 4/10/2026 |
| v0.25.1 | Updated dashboard logo SVGs (taskplane-word-white.svg and taskplane-word-color.svg). | Medium | 4/10/2026 |
| v0.25.0 | ## What's Changed * release: v0.24.31 — multi-segment .DONE fix, polyrepo bug fixes, local build by @HenryLach in https://github.com/HenryLach/taskplane/pull/463 **Full Changelog**: https://github.com/HenryLach/taskplane/compare/v0.24.31...v0.25.0 | Medium | 4/8/2026 |
| v0.24.31 | - TP-145-149: Multi-segment .DONE defense, orch branch investigation, skipped task preservation, wave display, integration ordering - Local build script for dev testing - Dashboard message wrapping - Sage review remediations - 3252 tests pass | Medium | 4/7/2026 |
| v0.24.30 | - Engine consumes expansion requests using outcome.segmentId (#452) - Workspace config resolution (#424), doubled path, task_packet_repo, Windows backslashes (#446) - 3231 tests pass | Medium | 4/7/2026 |
| v0.24.29 | Workspace YAML no longer short-circuits config resolution. Closes #424. 3231 tests pass. | Medium | 4/6/2026 |
| v0.24.28 | Fix doubled config repo name in workspace init tasks directory. 3231 tests pass. | Medium | 4/6/2026 |
| v0.24.27 | taskplane init now writes task_packet_repo in workspace YAML. 3231 tests pass. | Medium | 4/6/2026 |
| v0.24.26 | All path inputs normalized to forward slashes in taskplane init (#446). 3231 tests pass. | Medium | 4/6/2026 |
| v0.24.25 | - Safety-net auto-commit for uncommitted worker artifacts before merge phase - Sage remediations for segment expansion resume bugs - 3231 tests pass | Medium | 4/6/2026 |
| v0.24.24 | Merge agent was silently failing to authenticate since v0.24.21 due to PI_CODING_AGENT_DIR isolation cutting off auth.json. Removed. 3231 tests pass. | Medium | 4/6/2026 |
| v0.24.23 | - TP-142: request_segment_expansion tool + file IPC - TP-143: Engine DAG mutation with successor rewiring - TP-144: Acceptance tests - Resume crash fix (#441), topo-sort rollback, uniqueness validation - 3231 tests pass | Medium | 4/6/2026 |
| v0.24.22 | - TP-140: Global preferences architecture (schema → global → project overrides) - TP-141: First-install bootstrap + cross-provider reviewer/merger guidance - Merge agent thinking defaults to off (#439) - Deprecated /task commands removed - 3195 tests pass | Medium | 4/6/2026 |
| v0.24.21 | - Test and merge agent isolated from user preferences (prevents merge verification failures) - Enum settings use scrollable picker instead of toggle cycling - 3177 tests pass | Medium | 4/5/2026 |
| v0.24.20 | TP-138: Inherit defaults + thinking picker in /taskplane-settings TP-139: Init model picker + global defaults + `taskplane config --save-as-defaults` Sage review remediations applied. 3177 tests pass. | Medium | 4/5/2026 |
| v0.24.19 | Fix: mergeThinking user prefs were silently dropped. Found by Sage review. | Medium | 4/5/2026 |
| v0.24.18 | MergeConfig now has thinking field. All agents can use thinking mode. 3152 tests pass. | Medium | 4/5/2026 |
| v0.24.17 | Sage-style two-level model picker in /taskplane-settings. Provider → model selection with 'inherit' as first option. 3152 tests pass. | Medium | 4/5/2026 |
| v0.24.16 | TP-137: Batch history survives orch_integrate. Fixes #423. 3152 tests pass. | Medium | 4/5/2026 |
| v0.24.15 | Clear stale lane snapshots at wave boundaries + 60s tracker grace period. Fixes false task failures at wave start in workspace mode. 3148 tests pass. | Medium | 4/4/2026 |
| v0.24.14 | Same-repo segments now resolve packet paths inside the worktree. Fixes .DONE written outside worktree → false task failure. Also includes missing runGit import from v0.24.13. 3148 tests pass. | Medium | 4/4/2026 |
| v0.24.13 | waves.ts called runGit() but only imported getCurrentBranch from git.ts. ReferenceError silently caught → fell back to develop branch. Root cause of persistent wave 2 worktree failures. 3148 tests pass. | Medium | 4/4/2026 |
| v0.24.12 | check.status → check.ok in resolveBaseBranch. v0.24.10 regression fix. 3148 tests pass. | Medium | 4/4/2026 |
| v0.24.11 | Merge result path normalized to forward slashes in merge request. Prevents MSYS path misresolution on Windows. 3148 tests pass. | Medium | 4/4/2026 |
| v0.24.10 | Wave 2+ worktrees now branch from orch branch (with prior wave merged work) instead of repo HEAD. Fixes dependency satisfaction failures in polyrepo segment execution. 3148 tests pass. | Medium | 4/4/2026 |
| v0.24.9 | packetTaskPath resolved to absolute for cross-repo segment execution. First polyrepo segment test surfaced this. 3148 tests pass. | Medium | 4/4/2026 |
| v0.24.8 | ## Multi-repo segment execution (TP-132–136) - Engine segment frontier: sequential per-task segment execution - Segment-aware lane execution: segmentId in snapshots, separate cwd/packet paths - Segment persistence + resume: segments[] in batch state, frontier reconstruction - Segment observability: dashboard + supervisor alerts - Spec V2 alignment ## Crash notification fixes - Supervisor alert on engine crash via IPC error handler - Disk persistence on crash (fixes #421) 3148 tests, 0 failures | Medium | 4/3/2026 |
| v0.24.7 | Missing guard on optional onTelemetry callback caused engine crash for merge/reviewer agents. 3124 tests pass. | Medium | 4/3/2026 |
| v0.24.6 | - TP-129: Live context % refresh + reviewer telemetry parity - TP-130: Engine worker diagnostics (error handlers, stderr capture, snapshot failure counter) - TP-131: TMUX naming cleanup (dashboard, server, templates, audit) - Sage review fixes: immediate context telemetry, stderr flush safety, duplicate alert suppression, frontend version compat - 3124 tests pass | Medium | 4/3/2026 |
| v0.24.5 | - RULE #1: check boxes immediately after each item (not at step end) - Checkpoint reminder in worker prompt - Stall timeout: 30 → 60 min | Medium | 4/3/2026 |
| v0.24.4 | TP-128: TMUX removed from task-runner.ts, CLI, supervisor templates. -5876 lines, 15 reviews, 3119 tests pass. | Medium | 4/3/2026 |
| v0.24.3 | - **Engine crash fix**: emitSnapshot non-throwing, interval/callback guards - **Worker timeout**: 30 → 120 min default - **Context window**: auto-detect from model (0 = inherit) - 3413 tests pass | Medium | 4/3/2026 |
| v0.24.2 | - **Reviewer sub-row** in dashboard during reviews (live telemetry, review type/step labels) - **TP-122–126**: TMUX extrication completion (reference guards, operator messaging, comment sweep, compat shim, final removal) - **TP-127**: Wave transition fix (stale snapshot detection + 30s registry fallback) - **Config auto-migration**: legacy TMUX fields silently fixed on load - 3413 tests pass | Medium | 4/3/2026 |
| v0.24.1 | - Legacy TMUX config fields auto-migrated on load (no crash) - TP-127: multi-wave batch dashboard fix (stale snapshot detection) - Dead TMUX functions removed (-459 lines) - 3407 tests pass | Medium | 4/3/2026 |
| v0.24.0 | ## Highlights - **TMUX extrication complete** (orch runtime) — 9 tasks, 427→80 refs - **V2 worker system prompt** — full 362-line base template with checkpoint discipline - **review_step tool** — workers spawn reviewer agents at step boundaries - **Telemetry pipeline** — fixed end-to-end: live dashboard, batch summary, batch history ## Breaking Changes - `tmux_prefix` → `sessionPrefix` in config (old field throws error with migration guidance) - `tmuxSessionName` → `laneSessionId` in persisted | Medium | 4/3/2026 |
| v0.23.16 | Task creation skill now has inline scoring rubric at Step 2 and warns against defaulting to Level 0. | Medium | 4/2/2026 |
| v0.23.15 | - Workers get full 362-line base template with checkpoint discipline and review instructions - review_step tool spawns reviewer subprocess from bridge extension - Reviewer writes feedback to .reviews/, returns APPROVE/REVISE/RETHINK verdict | Medium | 4/2/2026 |
Dependencies & License Audit
Loading dependencies...
Similar Packages
@icex-labs/icex-flowDeterministic agent workflow orchestration — eliminate randomness in AI agent pipelines0.4.1
@gugamistri/harnessAI Agent Harness - Multi-model orchestration framework for AI coding agents0.10.0