Catalyst Dev — Change Log
6.13.0
Apr 14, 2026
Session Labeling System
Add meaningful display names to Claude sessions using the optional label field in worker signals, automatically derived from <skill> <ticket> patterns or set with the --label flag. Labels appear in both terminal and web monitor dashboards, making it easier to identify and track specific development sessions at a glance.
PRs
6.12.0
Apr 14, 2026
Multi-Frontend SSE Event Architecture
Catalyst now sends all orchestration events through a standardized envelope format with filtering support. Connect multiple frontends or tools to the same session using SSE query params like ?filter=session-update,metrics-update or ?session=abc123 to get only the events you need. The new typed event system supports session updates, metrics changes, and annotation events with automatic envelope wrapping for consistent downstream processing.
PRs
6.11.0
Apr 14, 2026
Session-Aware Skills
All six Catalyst skills now automatically track their execution as observable sessions with lifecycle events and phase transitions. Each skill run creates a session entry that links parent workflows to child operations, giving you full visibility into your AI-assisted development workflows. The skills gracefully degrade when session tracking isn’t available, so existing workflows continue working unchanged.
PRs
6.10.0
Apr 14, 2026
SQLite Session Integration
Solo Claude Code sessions now appear directly in the orchestration monitor alongside workflow workers, giving you one unified view of all AI development activity. The session store reader integrates with existing filesystem monitoring, so you can track and filter both orchestrated and standalone sessions through the same /api/sessions endpoint and live SSE streams.
PRs
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.