Mission Control & Pipelines

Dispatch asynchronous background coding pipelines, schedule recurring maintenance with cron, and review isolated branch pull requests.

Studio Command Center

Mission Control (accessible via Ctrl+Shift+M / Cmd+Shift+M or by clicking the Studio icon in the activity bar) is your command center for autonomous, long-running agent workflows.

Unlike real-time chat which blocks your immediate focus, Mission Control allows you to dispatch background engineering jobs that can execute for minutes or hours without supervision.

Non-Blocking Background Execution

When you dispatch a pipeline job, Kernax spawns an isolated execution worker:

• Zero Editor Locking: You can continue writing code, navigating files, and running local builds in your main window while the background worker refactors 50 files.
• Live Telemetry Stream: View real-time log outputs, step transitions, test results, and token expenditures from the Mission Control dashboard.
• Notification On Completion: Kernax triggers a native OS desktop notification once the pipeline reaches a terminal state (pass, fail, or pending review).

Cron Triggers & Scheduled Tasks

Schedule recurring maintenance tasks using standard 5-part cron syntax:

# Nightly Security Audit & Dependency Update (Every day at 02:00 AM)
0 2 * * * --task="Run pnpm audit, upgrade non-breaking patches, verify test suite passes"

# Weekly OpenAPI Specification Synchronization (Every Sunday at midnight)
0 0 * * 0 --task="Scan all Fastify routes and regenerate openapi.yaml schema"

# Daily Code Style & Linter Normalization
30 4 * * 1-5 --task="Run Biome linter across @src/ and fix auto-fixable formatting rules"

Isolated Git Branch Pull Requests

Safety is essential when running autonomous background pipelines. Whenever a pipeline job edits code, it executes within an ephemeral git branch (e.g. kernax/pipeline-task-108):

1. The background worker forks from your current HEAD into a dedicated sandbox branch.
2. All file writes, compiler runs, and test executions occur strictly inside this isolated branch.
3. Upon completion, Mission Control generates a visual Pull Request Card detailing:
   • Unified visual diff of all touched files.
   • Test pass/fail metrics and execution time.
   • Single-click Merge into Current Branch or Discard Branch buttons.