Catalyst Dev — Change Log
6.9.0
Apr 14, 2026
Session Lifecycle CLI
The new catalyst-session command gives any skill a universal interface to report lifecycle events,
metrics, and tool usage to the SQLite session store. Replace direct JSON file writes with structured
calls like catalyst-session start --skill myskill, catalyst-session phase $id running, and
catalyst-session metric $id --cost 0.05 to get automatic tracking in the orchestration monitor and
session APIs.
PRs
6.8.0
Apr 14, 2026
SQLite Session Store
Catalyst now persists all agent activity—both solo and orchestrated sessions—to a durable SQLite
database instead of fragile per-worker JSON files. The new catalyst-db.sh CLI provides session
CRUD, event logging, metrics tracking, and PR management with concurrent read/write support. Run
catalyst-db.sh init to create the database schema and start building persistent workflow history.
PRs
6.7.0
Apr 14, 2026
Pre-assigned Migration Numbers
The orchestrator now reserves sequential Supabase migration numbers for database tickets during wave
briefing, preventing filename collisions when multiple workers generate migrations in parallel.
Migration-likely tickets are detected via labels (database, migration, schema) and keywords,
then assigned unique NNN_ prefixes that appear in the briefing’s new Migration Number Assignments
section.
PRs
6.6.0
Apr 14, 2026
Fix-up and Follow-up Recovery Patterns
Two new orchestration patterns handle post-merge issues: fix-up workers push targeted commits to
open PRs when reviewers find blockers, while follow-up workers create new Linear tickets and fresh
worktrees for issues discovered after merge. Use orchestrate-fixup and orchestrate-followup
scripts to dispatch the appropriate recovery pattern based on your PR state.
PRs
6.5.4
Apr 14, 2026
Orchestrator-Controlled Merge Polling
Workers now exit cleanly after opening PRs with auto-merge armed, while the orchestrator handles the long poll until actual merge completion. This fixes premature worker termination issues where subprocess workers would exit before PRs were fully merged, with the orchestrator taking over merge monitoring duties and updating worker status when PRs complete.
PRs
6.5.3
Apr 14, 2026
Worker Worktree Context Fix
Fixed ticket extraction in worker worktrees so branches like orch-data-import-2026-04-13-ADV-220
correctly identify ADV-220 as the current ticket instead of false matches from orchestrator
prefixes. Worker worktrees now include an orchestration field in their workflow context, enabling
proper telemetry grouping across orchestrator and worker sessions.
PRs
6.5.2
Apr 13, 2026
PR Polling Through Merge
Orchestrated workers now actively poll PR state, CI status, and review comments until merge completion instead of exiting after creating the PR. The verification script independently confirms PRs reached MERGED state, catching any workers that ignore polling instructions. Workers wait a minimum 3 minutes then poll every 30 seconds with concrete step-by-step instructions.
PRs
6.5.1
Apr 13, 2026
Linearis Command Consolidation
Removed duplicated Linear CLI commands from 8 files, making the linearis skill the single source of
truth for all command syntax and options. Fixed a setup validation false positive that incorrectly
flagged properly configured thoughts directories. Agents now reference /catalyst-dev:linearis
instead of maintaining their own stale command examples.
PRs
6.5.0
Apr 13, 2026
Orchestration Monitor
Live dashboard tracks your orchestrator runs in real-time with worker status, phase timelines, and
cost analytics. See which workers need attention, browse wave briefings, and analyze parallelism
efficiency across completed runs. Launch with plugins/dev/scripts/orch-monitor from any workspace
with orchestrator history.
PRs
6.4.2
Apr 13, 2026
Linearis Integration Cleanup
Remove hardcoded CLI commands across 12 skills in favor of referencing the linearis skill for
syntax, ensuring single source of truth. Fix direnv timing in worktree creation to prevent
re-blocking when setup hooks modify .envrc, and remove broken @me assignee references that
linearis can’t resolve.