parallel-ai-session-orchestration-with-git-worktree-isolation
Manages multiple concurrent AI coding sessions (Claude Code and OpenAI Codex) running in parallel on the same repository by automatically creating isolated Git worktrees for each session. Uses Electron's multi-process architecture (main process handles SessionManager and WorktreeManager services) with IPC-based coordination to prevent file conflicts and state collisions. Each session maintains its own filesystem context while sharing the parent repository metadata.
Unique: Uses Git worktree isolation at the filesystem level (not just logical separation) combined with Electron's main/renderer process architecture to provide true parallel execution without conflicts. SessionManager and WorktreeManager services coordinate lifecycle across multiple concurrent sessions via IPC, enabling atomic session creation/deletion with automatic worktree cleanup.
vs alternatives: Provides true filesystem isolation for parallel AI sessions unlike Cursor or VS Code extensions which run sequentially or share context, enabling genuine side-by-side comparison of different AI approaches on identical code.
multi-panel-ai-conversation-management-within-sessions
Enables multiple independent AI conversation threads (panels) to run concurrently within a single session context, each maintaining separate conversation history and state. The Panel System Architecture routes AI requests through a unified interface that dispatches to Claude or Codex APIs while maintaining panel-specific context windows and conversation state in the database layer. Panels share the same worktree filesystem but maintain isolated conversation threads.
Unique: Implements panel-level conversation isolation within a shared worktree context using a dedicated Panel System Architecture that routes requests through a unified dispatcher. Each panel maintains independent conversation state in the SQLite database while sharing filesystem access, enabling true parallel reasoning without context contamination.
vs alternatives: Separates conversation threads at the architectural level (database-backed panel state) rather than UI-only separation, enabling persistent multi-threaded reasoning that survives application restarts and supports complex task decomposition.
event-system-for-reactive-state-updates
Implements a publish-subscribe event system that emits state changes from backend services (SessionManager, WorktreeManager, DatabaseService) to the UI renderer process. Services emit typed events when state changes (e.g., session created, file modified, command executed), and the renderer subscribes to these events to update the UI reactively. Events are routed through IPC, enabling real-time UI updates without polling.
Unique: Implements a typed event system that bridges main and renderer processes via IPC, enabling reactive UI updates without polling. Events are emitted by core services (SessionManager, WorktreeManager) and subscribed to by React components, creating a reactive data flow.
vs alternatives: Provides event-driven state synchronization between backend and UI rather than polling or manual state management, reducing latency and CPU overhead while maintaining type safety.
session-creation-and-configuration-management
Provides a workflow for creating new AI sessions with configurable parameters (model selection, system prompts, branch/worktree settings). The Session Creation and Configuration subsystem validates inputs, initializes a new session record in the database, creates an associated Git worktree, and sets up initial panel contexts. Users can configure per-session settings like AI model (Claude vs Codex), temperature, max tokens, and custom system prompts.
Unique: Implements session creation as an atomic operation that coordinates multiple services (DatabaseService for metadata, WorktreeManager for filesystem isolation, SessionManager for lifecycle). Configuration is stored in the database and applied consistently across all session operations.
vs alternatives: Provides integrated session creation with automatic worktree setup and configuration persistence, eliminating manual Git and configuration management compared to standalone AI tools.
project-and-session-organization-with-hierarchical-ui
Organizes multiple sessions within projects using a hierarchical UI structure. Projects group related sessions, and sessions contain multiple panels for different conversation threads. The Navigation and Layout subsystem renders a sidebar with project/session/panel hierarchy, enabling quick switching between contexts. Session metadata (creation time, model, status) is displayed in the UI for easy identification.
Unique: Implements a hierarchical project > session > panel organization in the UI, with metadata display for each level. Navigation state is managed reactively, enabling quick context switching without losing state.
vs alternatives: Provides built-in project and session organization in the UI rather than requiring external project management tools, enabling faster context switching and clearer session management.
settings-and-configuration-persistence
Manages application-wide settings (API keys, default models, UI preferences) through a ConfigManager service that persists settings to disk. Settings include API credentials for Claude and Codex, default AI model selection, UI theme, and logging level. Settings are loaded on application startup and can be modified through a settings UI panel. Sensitive settings (API keys) are stored securely using OS-level credential storage when available.
Unique: Implements ConfigManager as a core service that handles both application-wide settings and per-session configuration, with persistence to disk and optional OS-level credential storage for API keys. Settings are loaded early in the startup sequence and applied consistently across all services.
vs alternatives: Provides centralized configuration management with optional secure credential storage, eliminating the need for manual environment variable setup compared to CLI-based tools.
file-operations-and-ipc-based-file-access
Provides file read/write operations within worktrees through IPC-based file access APIs. The File Operations and IPC subsystem exposes file operations (read, write, delete, list directory) through the preload script, allowing the renderer to request file operations from the main process. File operations are scoped to the active worktree, preventing access outside the session context. All file I/O is handled by the main process, maintaining security boundaries.
Unique: Implements file operations through IPC with scoping to the active worktree, preventing accidental access outside the session context. All file I/O is handled by the main process, maintaining security boundaries between renderer and filesystem.
vs alternatives: Provides secure, scoped file access through IPC rather than direct renderer access to the filesystem, preventing security vulnerabilities while maintaining audit trails of file modifications.
claude-code-integration-with-streaming-output-rendering
Integrates Claude Code CLI (≥2.0.0) as a native AI backend with real-time streaming output rendering in the UI. The Claude Integration layer in the main process spawns Claude Code CLI as a child process, captures streaming responses via PTY (pseudo-terminal) management, and pipes structured output to the renderer process via IPC. AI Output Rendering components parse and display Claude's responses with syntax highlighting and interactive code blocks.
Unique: Wraps Claude Code CLI as a managed subprocess with PTY-based streaming output capture, enabling real-time response rendering without buffering. Integrates Claude's native capabilities directly into Crystal's multi-session architecture rather than using Claude API directly, preserving Claude Code's full feature set including file operations and terminal access.
vs alternatives: Provides tighter integration with Claude Code's native CLI than REST API wrappers, enabling access to Claude Code's full capabilities (file system operations, terminal execution) while maintaining streaming output and multi-session isolation.
+7 more capabilities