Creates a memoized unifiedTabs array that combines aiTabs and
filePreviewTabs according to the session's unifiedTabOrder. Uses
a discriminated union type to allow components to render the
appropriate content for each tab type (AI or file preview).
Phase 1 of file preview tabs feature:
- Add FilePreviewTab interface with id, path, name, extension, scrollTop,
searchQuery, editMode, editContent, and createdAt fields
- Add UnifiedTabRef type for tab ordering across types
- Add filePreviewTabs, activeFileTabId, and unifiedTabOrder to Session
- Update all 13 session creation locations with new fields
- Update session restoration to hydrate new fields from persistence
This establishes the data model for coexisting AI tabs, file preview tabs,
and future terminal tabs in a unified tab bar.
Changed IssueCard from <button disabled> to <div role="button"> to allow
nested PR link button to receive click events. Disabled buttons block all
pointer events on children, even with pointerEvents: 'auto' style.
- Outer container is now a div with role="button" and manual keyboard handling
- PR link is now a proper <button> that can receive clicks independently
- Maintains same visual styling (opacity-60 for unavailable issues)
- Keyboard navigation preserved via tabIndex and onKeyDown
- Moderator @mentions now normalize names (spaces→hyphens) for reliability 🧭
- Participant and available-session lists now show mention-ready normalized handles 👥
- Header responsiveness tuned for AUTO mode’s extra button width 📐
- Session name now hides on ultra-narrow panels to save space 🪟
- Git branch icon won’t shrink; branch text truncates cleanly ✂️
- Symphony issue PR link upgraded from span to proper button 🧷
- PR link click handling simplified; keyboard hacks removed for cleaner UX ⌨️
- Batch TTS settings now use refs to avoid stale closures mid-run 🎙️
- Audio feedback toggles take effect immediately during batch processing ⚡
- Batch processor deps slimmed since audio settings are ref-driven 🧼
- Add isGeneratingName property to AITab interface
- Show Loader2 spinner in tab while name generation is in progress
- Set isGeneratingName true before API call, false on completion/error
- Spinner only shows when automatic tab naming is enabled
Moved additional visual/output settings from General to Display:
- Interface font family and size
- Terminal width (columns)
- System log level and max buffer
Updated tests and docs to reflect new Display tab location.
When closing the Auto Run Configuration modal, show a confirmation
dialog if there are unsaved changes to:
- Document list (documents added or removed)
- Loop settings (enabled/disabled, max loops)
- Agent prompt (edited from initial value)
If no changes were made, the modal closes immediately without
confirmation.
This prevents accidental loss of configuration when users press
Escape, click Cancel, or click the X button.
Add comprehensive test suite to verify modal priority ordering:
- Child modals must have higher priority than parents (30 test cases)
- Ensures DocumentSelectorModal closes before BatchRunner
- Ensures MarketplaceModal closes before BatchRunner/AutoRunExpanded
- Verifies confirmation dialogs are 1000+, overlays are lower priority
- Tests priority ranges match documented conventions
These tests will catch future regressions where child modals have
incorrect priorities, causing Escape to close parent modals first.
Split General settings panel by creating new Display tab containing:
- Max output lines per response
- Document graph settings (external links, max nodes)
- Context window warnings (thresholds)
Updated docs to reflect new panel location.
When a new session starts and the first message is sent, Maestro now
automatically generates a descriptive tab name based on the user's
request. This runs in parallel with the main prompt processing and
uses the same AI agent (honoring SSH remote configurations).
Implementation:
- Add tab naming prompt at src/prompts/tab-naming.md
- Add IPC handler (tabNaming:generateTabName) that spawns ephemeral
session to generate names with 30s timeout
- Integrate with onSessionId callback to trigger naming for new tabs
- Only update name if tab is still in UUID format (user hasn't renamed)
- Add automaticTabNamingEnabled setting (default: true)
- Add Settings UI checkbox under General section
Tab names are 2-5 words, Title Case, and capture the specific intent
rather than generic descriptions. Examples:
- "Help me implement JWT auth" → "JWT Auth Implementation"
- "Fix the checkout bug" → "Checkout Bug Fix"
Tests: 22 new tests covering IPC handler, settings, and edge cases
Docs: Updated general-usage.md, features.md, and configuration.md
Apply RTL text direction with LTR text isolation to show the rightmost
(filename) portion of document paths when truncated, while maintaining
full path on hover via title attribute.
Updated components:
- DocumentsPanel: Auto Run document list entries
- RightPanel: Auto Run progress indicator (single and multi-doc views)
When opening the lightbox from staged images, a snapshot of stagedImages
was saved to lightboxImages. The LightboxModal used this snapshot for
navigation. When deleting an image, only stagedImages was updated but
lightboxImages remained stale, causing the deleted image to still appear.
Fix: Update both stagedImages AND lightboxImages in handleDeleteLightboxImage.
Added regression tests that simulate the parent state synchronization
pattern and verify both states are updated on deletion.
Add overflow-y-auto and max-h-[calc(100vh-120px)] to hamburger menu
dropdown containers so content can scroll when the viewport doesn't
have enough vertical space to display all menu items.
Applied to both expanded and collapsed sidebar menu overlays.
- Stabilized group-chat integration tests by mocking Electron `app.getPath()` 🧪
- Added preload filesystem support to write files on SSH remotes 🚀
- Expanded `fs:writeFile` IPC signature to include optional remote identifier 🔌
The useInputProcessing test for "preserves multi-word arguments with
spaces" was failing because mockProcessQueuedItemRef.current accumulated
calls across tests in the nested describe block. Added a beforeEach to
explicitly clear the mock, ensuring mock.calls[0] always references the
current test's call.
Adds a "Response Completeness" section to the Maestro system prompt
instructing agents to make each response self-contained with clear
summaries, relevant context, and key details. This ensures users can
understand responses even when only seeing the most recent message.
Updated all agent prompts to explicitly state that only the LAST
message is captured by the system. This ensures agents produce
complete, self-contained responses with all relevant information.
Prompts updated:
- context-grooming.md, context-summarize.md, context-transfer.md
- autorun-default.md, autorun-synopsis.md
- group-chat-participant.md, group-chat-participant-request.md
- group-chat-moderator-system.md, group-chat-moderator-synthesis.md
- maestro-system-prompt.md (new "Response Completeness" section)
Enable saving markdown content directly to remote filesystems
when connected via SSH. The fs:writeFile IPC handler now accepts
an optional sshRemoteId parameter and uses writeFileRemote for
SSH transport.
The native folder dialog can only browse local filesystems, so hide the
browse button when the session is running over SSH (where the default
path would be a remote path). Users can still manually type a path.
Changed the git info popup's remote URL link to use
window.maestro.shell.openExternal() instead of window.open()
so it opens in the user's default system browser.
- Add await to shell.openExternal call to ensure proper async handling
- Show toast notification when no remote URL is found for the repository
- Add error handling with toast feedback for any failures
- Update tests to verify toast notifications are shown on error
Fixes issue where the command didn't provide feedback when failing.
Custom notification commands (e.g., TTS, fabric pipelines) should only
run for regular AI conversation flow toasts, not for synopsis messages.
Added skipCustomNotification flag to Toast interface and set it to true
for synopsis toasts. This prevents the notification command from being
executed when a synopsis completes, while still showing OS notifications
and toast UI.
Document nodes with long unbroken text (like separator lines with ====)
were bleeding outside their boundaries. Fixed by:
- Setting fixed width (280px) on container instead of just maxWidth
- Using break-all word breaking for description text
- Adding webkit line clamping to limit description to 3 lines
- Using text-overflow: ellipsis with overflow: hidden
- Shows "Drop here to ungroup" zone when dragging a session and no ungrouped sessions exist
- Allows users to drag sessions out of groups even when Ungrouped Agents folder is hidden
- Added tests for drop zone visibility and drop handler
Previously, the Test button would show "Stop" after the notification
command started and remain visible even after the process exited,
requiring an 8-second timeout fallback to reset.
Now the component listens for the onCommandCompleted event and
immediately resets to "Test" (via Success state) when the process
exits naturally. The Stop button is only shown while the process
is actively running.
Remove backward compatibility shim and fully migrate from legacy ttsId
property to notificationId across all notification-related code:
- Update NotificationsPanel.tsx to use result.notificationId
- Remove deprecated ttsId from NotificationCommandResponse interface
- Remove legacy TTS alias exports from handler
- Update all test files and mocks to use notificationId
Changed elapsed time calculation for USER history entries to use the
actual task duration (from thinkingStartTime to completion) instead of
time since the last synopsis. This accurately reflects how long the
agent was actively working on the task being synopsized.
Add elapsed time calculation when creating USER history entries via
the saveToHistory/synopsis feature. Time is calculated from lastSynopsisTime
(if a previous synopsis exists) or tabCreatedAt (for first synopsis).
This complements the existing elapsed time tracking for AUTO entries.
- Rename "Speakable Notifications" to "Custom Notifications" in features
- Update Notifications tab description to remove TTS-specific language
- Revise Custom Notification section with broader command examples
- Remove default TTS bias from configuration guidance
The previous fix added document-level dragover/drop handlers to call
preventDefault(), but handleImageDragOver was calling stopPropagation()
which prevented the document-level handlers from firing during the bubble
phase. Switching to capture phase ensures preventDefault() is called at
the document level before element handlers can stop propagation.
Update notification tests to clearly document and verify that:
- Custom notification commands have NO whitelist and NO validation
- ANY executable path, binary name, or arguments are allowed
- Shell pipelines with redirects and pipes are fully supported
Also rename TTS terminology to generic notification terminology:
- resetTtsState → resetNotificationState
- getTtsQueueLength → getNotificationQueueLength
- getActiveTtsCount → getActiveNotificationCount
- clearTtsQueue → clearNotificationQueue
- getTtsMaxQueueSize → getNotificationMaxQueueSize
- Add onCommandCompleted alongside deprecated onTtsCompleted
This ensures the feature remains open-ended for user flexibility.
Without preventing default on both dragover and drop at the document level,
Electron/Chromium can reject subsequent drag-and-drop operations after the
first drop. This adds document-level handlers that call preventDefault() on
both events, ensuring the drop zone remains valid across multiple operations.
- Remove TTS command whitelist validation - users can now configure any
command for custom notifications (e.g., fabric piped to 11s)
- Enable shell mode for spawn to support pipes and command chains
- Add visual feedback to Test button (running/success/error states)
- Remove speech bubble from AI response messages in TerminalOutput
- Rename internal TTS terminology to more generic "notification command"
- Update tests to reflect new behavior
Fixes overlay not covering sidebar and file panel by rendering the
modal via React portal to document.body, ensuring proper z-index
stacking across all UI layers.
Stats DB initialization failures were only logged locally, providing no
visibility into production issues. This change adds Sentry reporting for:
- Database corruption detection (integrity check failures)
- Native module loading failures (architecture mismatches)
- Database creation failures
- General initialization failures
Created reusable Sentry utilities in src/main/utils/sentry.ts that
lazily load @sentry/electron to avoid module initialization issues.
Add comprehensive crash detection for renderer process failures that
Sentry in the renderer cannot capture (because the process is dead,
broken, or failed before Sentry initialized):
- render-process-gone: captures crash, kill, OOM, launch-failed
- unresponsive/responsive: tracks frozen window states
- crashed: handles page-level crashes
- did-fail-load: captures page load failures (network, invalid URLs)
- preload-error: captures preload script failures before app loads
- console-message: forwards critical renderer errors (TypeError, etc.)
Reports to Sentry from main process with detailed context.
Auto-reloads renderer after non-intentional crashes.
When users select "All" for Max Output Lines, Infinity is stored but
JSON.stringify(Infinity) produces null. On app restart, this null value
was being loaded directly, causing:
- null * 1.5 = 0 for maxHeight calculation
- All AI responses appearing fully collapsed (only "Show all X lines")
Now we detect null values for maxOutputLines and restore them as
Infinity, matching the user's original "All" selection.
Root cause: JSON cannot represent Infinity, so it becomes null during
serialization to electron-store.
Fixes the regression where maxOutputLines setting was lost on restart.
Add a save icon to the action buttons at the bottom of AI responses
that opens a modal allowing users to save the markdown content to a
file. The modal includes:
- Folder path input with a browse button for filesystem navigation
- Filename input with automatic .md extension handling
- Error handling and validation
- Remove "Pencil" and "Image" labels to show icon-only for those controls
- Update Thinking description to "toggles display of agent thinking"
- Make label prop optional in TourIcon component
- Convert tourSteps.ts to tourSteps.tsx to support JSX content
- Add descriptionContent/descriptionContentGeneric fields to TourStepConfig
for rendering JSX after the text description
- Create TourIcon component that renders actual Lucide icons inline
- Update input area step to show PenLine, ImageIcon, History, Eye, Brain,
and Keyboard icons matching the actual UI controls
- Widen tooltip to 480px when step has extra JSX content
- Restore original description text, move icon explanations to JSX content
When loading remote content (e.g., README.md from SSH), the loading
indicator now takes over the entire main panel instead of showing
alongside the terminal output. This prevents the awkward half-filled
appearance.
Apply the same fix from the marketplace handlers to Symphony:
- getRegistry: Falls back to expired cache when GitHub fetch fails
- getIssues: Falls back to expired cache when GitHub fetch fails
This prevents showing empty data when the network is unavailable
but valid (though expired) cache data exists.
