vibe-kanban

Author	SHA1	Message	Date
Britannio Jarrett	50d285cfe5	use existing config system instead of local storage for showcase tracking (vibe-kanban) (#1049 ) * Perfect! All tasks completed successfully. Here's what was implemented: ## Summary ✅ Migrated showcase persistence from localStorage to v8 config system Backend (Rust): - Created [v8.rs](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/0960-use-existing-con/crates/services/src/services/config/versions/v8.rs) with `ShowcaseState` struct tracking `seen_versions: HashMap<String, u32>` - Implemented migration from v7→v8 with default empty showcases - Wired up v8 as active config version Frontend (TypeScript): - Created [useShowcasePersistence.ts](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/0960-use-existing-con/frontend/src/hooks/useShowcasePersistence.ts) hook using config API - Refactored [useShowcaseTrigger.ts](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/0960-use-existing-con/frontend/src/hooks/useShowcaseTrigger.ts) to use new persistence (kept API unchanged) - Deleted old localStorage utility - Generated TypeScript types including `ShowcaseState` Key Features: - Showcase state persists to config file (survives random port changes) - Tracks highest version seen per showcase ID - Optimistic updates for responsive UX - Automatic v7→v8 migration on startup * Cleanup script changes for task attempt 096017a4-28dd-4092-a3ef-7180232ee7d2 * Done! Now `default_git_branch_prefix` is imported from v7 instead of being duplicated. * Cleanup script changes for task attempt 096017a4-28dd-4092-a3ef-7180232ee7d2 * fix FeatureShowcaseModal race condition (vibe-kanban) (#1050) * Done! Collapsed v8 back into v7. The `showcases` field is now part of v7 with `#[serde(default)]`, making it backward compatible without needing a version bump. * Cleanup script changes for task attempt 096017a4-28dd-4092-a3ef-7180232ee7d2 * Fixed! ✅ * showcase simplification (vibe-kanban 94972ea4) frontend/src/config/showcases.ts I want to make it harder to make mistakes here, lets use the type system to our advantage. 1. We could forget to update the `export const showcases` variable, so instead of expecting `taskPanelShowcase`, we should move showcases to all be under one object and only access them through that object. 2. The versioning system is overkill, instead of a `showcases` map with `seen_versions` as another map, we can have a `seen_features` set (realistically an array in JSON) that we insert keys into.	2025-10-17 18:43:40 +01:00
Alex Netsch	749a826f2e	Fix queue not working (vibe-kanban) (#1047 ) * The regression came from the big FE reshape in `518230f8a`. That commit remapped “open details” to `⌘/Ctrl+Enter` in the Kanban scope; the follow‑up submit has always lived on the same shortcut. When the textarea is focused both scopes (`kanban` and `follow-up-ready`) are active, so pressing `⌘/Ctrl+Enter` fires the Kanban handler first, cycling the view instead of calling the queue submit. That’s why the queue no longer “auto triggers” unless you click the button. I left the backend untouched (per your revert) and fixed the shortcut conflict instead: - `frontend/src/pages/project-tasks.tsx:379` – detect when the follow-up scope is active (`activeScopes.includes(Scope.FOLLOW_UP_READY)`) and only register the Kanban `useKeyOpenDetails` handler when it isn’t. This keeps the new navigation shortcut for the board while letting the follow-up queue reclaim `⌘/Ctrl+Enter` whenever the editor is focused. Tests (pre-existing warnings only): - `pnpm lint` Give it a try: with the follow-up editor focused, `⌘/Ctrl+Enter` should queue (or send) again, while the view-cycle shortcut still works elsewhere. Natural next step would be a quick manual smoke test to confirm both shortcuts behave as expected. * You were right: the queue still wouldn’t drain when the Preview tab was open because the dev‑server process stays “running” in the background. Our follow-up queue logic refuses to start if any process for the attempt is running, so it kept treating that long-lived DevServer process as a blocker—even after you clicked Queue or Send. I tightened the check so we ignore DevServer runs when deciding whether it’s safe to kick off the next follow-up: - `crates/services/src/services/drafts.rs:152` – when `has_running_processes_for_attempt` scans the execution list, it now filters out processes whose `run_reason` is `DevServer`. That way only real CodingAgent/cleanup activity blocks the queue. Verification: - `cargo check -p services` With this change you can keep the preview pane (and its dev server) open and queued follow-ups will still fire as soon as the current coding run finishes.	2025-10-17 15:46:37 +01:00
Britannio Jarrett	c48ba45573	feature showcase (vibe-kanban) (#1042 ) * Done! I've created a floating onboarding panel that: 1. Anchors to the resize handle - Uses `#handle-kr` (the drag handle between kanban and task panel) as an anchor point 2. Floats to the left - Positioned with fixed positioning, offset from the handle's right edge 3. Tracks panel movement - Uses MutationObserver and resize listeners to stay anchored even when the panel is resized 4. Animates in/out - Smooth fade and slide transitions with framer-motion 5. Shows for all tasks - Displays whenever `isPanelOpen` is true (desktop only) The component includes placeholder content with a welcome message, step indicators (1 of 3), and Next/Skip buttons ready for your multi-stage guide implementation. * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Perfect! I've updated the onboarding component with a multi-stage system featuring 5 sections: Features: - 5 stages: Follow-ups, Code Review, Git Actions, Live Previews, and VK Companion - Video support: Each stage displays the same video (for now) with autoplay and loop - Navigation: Previous/Next buttons, with "Finish" on the last stage - Progress indicators: Dots and "Step X of 5" counter - Smooth transitions: Content slides between stages using framer-motion - Skip option: Available on all stages Each stage has a descriptive title and two-sentence description explaining the feature. The videos automatically reload and play when switching between stages. * Increased the panel width from 384px (w-96) to 576px (w-[36rem]). The video should now be significantly larger. * Fixed! The positioning now: - Checks the panel height and viewport bounds - Keeps 20px margin from top and bottom edges - Adjusts the anchor position if the panel would overflow - Re-calculates when stage changes (since content height may vary) * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Fixed! Now the panel: - Checks if it would overflow at top or bottom when centered - Switches to top-aligned positioning when it would overflow - Calculates a safe top position that keeps the entire panel visible - Uses `translateY(0)` instead of `translateY(-50%)` when top-aligned * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Fixed! I simplified the positioning logic: - Centers the panel vertically on the handle position - No transform needed - uses absolute top positioning - Ensures 20px margins from viewport edges - Panel stays fully visible when it would overflow * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Fixed! Now it properly centers the panel on the middle of the handle by using `handleRect.top + handleRect.height / 2` as the center point, then offsetting by half the panel height. * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Done! Converted to a modal with: - 2/3 screen width centered horizontally - Bottom aligned with 2rem margin from bottom - Backdrop overlay that doesn't dismiss on click - No ESC dismiss (removed keyboard handler) - Smooth slide-up animation from bottom * Fixed! The issue was that framer-motion's `y` transform was overriding the Tailwind `-translate-x-1/2`. Now using inline style for `translateX(-50%)` which works alongside motion's `y` transform. * Perfect! Now the modal is horizontally centered using `left-[16.66%]` (which is 100% - 66.66% divided by 2) and `w-2/3`, which means it takes up 2/3 of the width and is centered. This won't conflict with framer-motion's transform animations for the y-axis. * Done! I've made the following changes: 1. Removed Skip and Close buttons - Users can just click "Next" through all stages or "Finish" on the last one 2. Improved step count visual hierarchy: - Moved the numeric count (1 / 5) to the top right next to the title - Made it more prominent with `font-medium` styling - Changed the dots to full-width progress bars that stretch across the bottom - Progress bars use `h-1` height and `flex-1` to distribute evenly - Cleaner, more modern progress indicator The layout now has better visual hierarchy with the count at the top and a progress bar below the description. * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Fixed! I've added `aspect-video` to the video container, which reserves a 16:9 aspect ratio space before the video loads. The video now uses `h-full object-cover` to fill that space. This prevents layout shift during the entrance animation. * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Perfect! I've updated the buttons to match the app's theme: 1. Added icons: `ChevronLeft` for Previous and `ChevronRight` for Next 2. Removed border radius: No `rounded` class 3. Outline border: Using `border border-input` for Previous and `border border-foreground` for Next 4. Consistent sizing: Using `h-10 px-4 py-2` matching the default button size 5. Proper styling: Following the button variants from the app's button component The buttons now match the visual style used throughout the rest of the application. * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * ## Summary I've successfully implemented a generic feature showcase system following delegation-oriented development: ### ✅ Completed Components 1. Type System - `frontend/src/types/showcase.ts` 2. Configuration - `frontend/src/config/showcases.ts` (task panel showcase with 5 stages) 3. Persistence - `frontend/src/utils/showcasePersistence.ts` (localStorage-based) 4. Video Progress Hook - `frontend/src/hooks/useVideoProgress.ts` (tracks loading/buffering/playback) 5. Media Component - `frontend/src/components/showcase/ShowcaseStageMedia.tsx` (images/videos with loading states) 6. Main Modal - `frontend/src/components/showcase/FeatureShowcaseModal.tsx` (with ESC key handling) 7. i18n Keys - Added to `tasks.json` 8. Integration - Replaced TaskPanelOnboarding in project-tasks.tsx ### 🎯 Key Features - ✅ Supports images and videos with loading indicators - ✅ Video progress bar (buffered + played, like vibe-kanban-website) - ✅ ESC key properly scoped (closes modal, not task panel) - ✅ LocalStorage persistence (`showcase:<id>:v<version>:seen`) - ✅ i18n support for all content - ✅ Single-stage support (hides nav if 1 stage) - ✅ Flexible trigger location (configured per showcase) - ✅ All TypeScript and Rust checks pass ### 🧪 Ready for Browser Testing What port is your dev server running on? I'll test: 1. Opening a task triggers the showcase 2. Video loading states and progress bars 3. Stage navigation (Previous/Next/Finish) 4. ESC closes only modal, not task panel 5. Persistence (doesn't show again after Finish) * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * ## ✅ Feature Showcase System - Complete! Successfully implemented a generic, reusable feature showcase system following delegation-oriented development with full QA verification. ### 📦 Deliverables Core Components: - `FeatureShowcaseModal` - Main modal with ESC key scope management - `ShowcaseStageMedia` - Image/video renderer with loading states & progress bars - `useVideoProgress` - Hook for video buffering/playback tracking - `showcasePersistence` - LocalStorage helpers for seen tracking - Type definitions & configuration system Integration: - Migrated task panel onboarding to new system - Added i18n keys for all showcase content - Removed old `TaskPanelOnboarding` component ### ✨ Features ✅ Flexible Triggers - Can be placed anywhere (currently on task panel open) ✅ ESC Key Handling - Proper scope management (closes modal, not underlying feature) ✅ Media Support - Images and videos with loading indicators ✅ Video Progress - Thin progress bar showing buffered/played state ✅ Persistence - LocalStorage tracking with version support ✅ i18n Ready - Full localization support ✅ Single/Multi-stage - Adapts UI for 1 or multiple stages ✅ Mobile-aware - Only shows on desktop (width ≥ 1280px) ### 🧪 QA Results All tests passed including: - Showcase triggering on task open - Navigation between 5 stages - ESC key scope handling - Persistence across sessions - Responsive behavior - Edge case handling ### 🎯 Usage To add a new showcase: 1. Define config in `showcases.ts` 2. Add i18n keys in `tasks.json` 3. Trigger where appropriate with `hasSeen()` check 4. Render `<FeatureShowcaseModal>` with config * Done! Removed backdrop click to close functionality. Users can only close the showcase by: - Clicking "Finish" button on the last stage - Pressing ESC key * Fixed! The showcase now: - Shows on all screen sizes (mobile and desktop) - Mobile: Full width with 1rem horizontal padding - Desktop (xl+): 2/3 width, centered - Bottom spacing adjusts responsively (1rem mobile, 2rem desktop) * update task text * Done! ESC is now captured but does nothing. Users must click through the stages or use "Finish" to close the showcase. * update task text * i18n (vibe-kanban 7f62c07e) run scripts/check-i18n.sh and resolve any discrepancies by translating missing values. * Done! All changes complete: ✅ Mobile support - Removed mobile check, now shows on all devices with responsive width ✅ Component docs - Added JSDoc to both FeatureShowcaseModal and ShowcaseStageMedia ✅ Progress bar - Increased height from 2px to 4px for better visibility ✅ Developer guide - Created comprehensive README.md in `components/showcase/` The showcase now works across all screen sizes and has full documentation for future development. * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * Fixed! Removed the incorrect ESC test from the checklist. The showcase can only be closed by clicking "Finish" on the last stage (ESC is captured but disabled). * Fixed! Removed that line and also corrected "after closing" to "after finishing" to be accurate. * Fixed! Now all button labels use i18n keys: - `showcases.buttons.previous` - `showcases.buttons.next` - `showcases.buttons.finish` * Perfect! All review comments addressed: ## ✅ Changes Complete 1. Scope handling documentation - Added detailed comment explaining why we enable/disable scopes 2. Created `useShowcaseTrigger` hook - Extracted and simplified the trigger logic 3. Refactored project-tasks.tsx - Now uses the hook (much cleaner) 4. Updated README - Reflects the new hook-based usage pattern The code is now more robust and maintainable. All TypeScript and Rust checks pass. The showcase system is ready to be easily reused across any feature in the app. * Cleanup script changes for task attempt 5c2c52b0-90de-4f9a-98a2-cade3e471c4f * video showcase bug (vibe-kanban 383590da) CHANGED FILES: frontend/src/components/showcase/FeatureShowcaseModal.tsx frontend/src/components/showcase/README.md frontend/src/components/showcase/ShowcaseStageMedia.tsx frontend/src/config/showcases.ts frontend/src/hooks/useShowcaseTrigger.ts frontend/src/hooks/useVideoProgress.ts frontend/src/i18n/locales/en/tasks.json frontend/src/i18n/locales/es/tasks.json frontend/src/i18n/locales/ja/tasks.json frontend/src/i18n/locales/ko/tasks.json frontend/src/pages/project-tasks.tsx frontend/src/types/showcase.ts frontend/src/utils/showcasePersistence.ts The showcase is sometimes being shown more than once. Users press the finish button, the showcase closes, then they click on another task and it opens again. Use the oracle to extensively diagnose this issue then resolve it. * showcase improvement 2 (vibe-kanban 3e5a7c01) frontend/src/components/showcase/FeatureShowcaseModal.tsx frontend/src/components/showcase/README.md frontend/src/components/showcase/ShowcaseStageMedia.tsx frontend/src/config/showcases.ts frontend/src/hooks/useShowcaseTrigger.ts frontend/src/hooks/useVideoProgress.ts frontend/src/i18n/locales/en/tasks.json frontend/src/i18n/locales/es/tasks.json frontend/src/i18n/locales/ja/tasks.json frontend/src/i18n/locales/ko/tasks.json frontend/src/pages/project-tasks.tsx frontend/src/types/showcase.ts frontend/src/utils/showcasePersistence.ts Do we need semantic versioning? We can just use a single number right (1, 2, ...). We aren't ever parsing the sem var and doing comparisons right? Or am i mistaken? * showcase improvement 1 (vibe-kanban be7d377b) see the first useEffect in FeatureShowcaseModal Isn't this too specific to the scopes featured in the task panel? If we want to show this showcase elsewhere, it might change. * remove unused clearSeen() function * feature showcase \| no auto replay (vibe-kanban 2e945b1f) frontend/src/components/showcase/FeatureShowcaseModal.tsx frontend/src/components/showcase/ShowcaseStageMedia.tsx frontend/src/config/showcases.ts frontend/src/hooks/useShowcaseTrigger.ts frontend/src/hooks/useVideoProgress.ts frontend/src/pages/project-tasks.tsx frontend/src/types/showcase.ts frontend/src/utils/showcasePersistence.ts Each video should only play once, then once finished, a replay button should appear in the center. * updated videos * feature showcase \| prevent cut off (vibe-kanban 79364905) frontend/src/components/showcase/FeatureShowcaseModal.tsx frontend/src/components/showcase/ShowcaseStageMedia.tsx frontend/src/config/showcases.ts frontend/src/hooks/useShowcaseTrigger.ts frontend/src/pages/project-tasks.tsx frontend/src/types/showcase.ts frontend/src/utils/showcasePersistence.ts On some displays, the showcase pop up height is too large. Use the oracle to hypothesize various solutions to this then implement the most promising one. * update showcase videos * remove showcase readme	2025-10-17 15:46:21 +01:00
Britannio Jarrett	362e3e23b4	PR title/description is lost if we attempt to create a PR without being logged into GitHub (vibe-kanban) (#950 )	2025-10-17 06:31:41 -07:00
Alex Netsch	1090255bd7	Use the first found port for frontend preview detection (vibe-kanban) (#1046 ) * - Updated `frontend/src/hooks/useDevserverUrl.ts:66-84` so new log chunks are scanned in arrival order and the state keeps the very first detected preview URL/port instead of replacing it with later ones. - Confirmed the hook still resets when the log stream shrinks (new process) so a new attempt can detect a fresh first port. I wasn’t able to run `pnpm run check` here; feel free to run it locally if you’d like to double-check. * - Added an early return in `frontend/src/hooks/useDevserverUrl.ts:74-81` so once a preview URL is locked in we simply advance `lastIndexRef` and skip parsing new log entries, avoiding unnecessary work while still resetting correctly if the stream shrinks. - Extended the effect dependency list to include `urlInfo` so the early-return logic behaves consistently with state updates. If you want to cover the edge case where the dev server restarts on the same attempt and we intentionally reset the stored URL, we can hook into that next. * Swapped the index-based `for` with `Array.prototype.some` over a sliced view of the new log entries (`frontend/src/hooks/useDevserverUrl.ts:77-85`). This keeps the “stop at the first hit” behavior but reads a little cleaner and avoids manual index bookkeeping.	2025-10-17 14:20:29 +01:00
Louis Knight-Webb	518230f8a0	WIP FE revision (#975 ) * scaffold new sidebar * wysiwyg * Task context and hook (vibe-kanban 29f71b17) Can you please create a context for getting info about the current Task, and also tanstack query mutation for get, update, delete. @frontend/src/hooks/ @frontend/src/contexts/ Ultimately this will be implemented in frontend/src/components/panels/TaskPanel - but that's a future change * attempts section * Add table of task attempts (vibe-kanban a069161c) frontend/src/components/panels/TaskPanel.tsx * Proper routing between task and task attempt panel (vibe-kanban 0cf73011) When the user clicks on a task attempt in the task panel, it should switch to the task attempt panel frontend/src/components/panels/TaskPanel.tsx frontend/src/components/panels/TaskAttemptPanel.tsx * Fill out TaskAttemptPanel (vibe-kanban 219a1bde) frontend/src/components/panels/TaskAttemptPanel.tsx This should have conversation history logs and the follow up box below * Navigation changes (vibe-kanban 35767666) frontend/src/components/panels/KanbanSidebar.tsx - Upon opening a task, if there are task attempts, the latest task attempt should be shown by default - We should add a close button and a fullscreen button to the right of the breadcrumbs - The close actions should close the task/attempt - The fullscreen button should have no action for now * table styles * Create a task attempt (vibe-kanban 5c84e9cd) It should be possible to create a task attempt from frontend/src/components/panels/TaskPanel.tsx * Refactor the fullscreen approach (vibe-kanban e9d988af) frontend/src/lib/responsive-config.ts frontend/src/pages/project-tasks.tsx I'd like to take a different approach to handling the responsive content. - In kanban mode, the kanbansidebar should be shown next to tasks - In full screen mode the kanban sidebar should be shown next to a new component (leave blank for now, but rest of space), with sidebar on the right - Transitioning between the two shouldn't cause a re-render of the sidebar, as we want to preserve scroll position of the sidebar * Navigating from task attempt to task (vibe-kanban 0072d295) Navigating to task attempt from task in the sidebar forces the full screen mode to exit. frontend/src/hooks/useTaskViewManager.ts should navigate while maintaining the current status of fullscreen/non-full screen, unless it is specifically specified in options * Introduce fullscreen tabs (vibe-kanban 9fb1a248) /projects/:projectId/tasks/:taskId/attempts/:attemptId/full/preview - this should have logs next to preview /projects/:projectId/tasks/:taskId/attempts/:attemptId/full/diffs - this should have logs next to diffs We should refactor the code so that these tabs are displayed next to the logs using ResponsiveTwoPane. There should be tabs to navigate between these different views, next to the close and fullscreen toggles. Don't fill out any content for preview or diffs yet, just scaffold the page structure and we'll fill out the content after. * Remove the fullscreen mode for tasks and task attempts (vibe-kanban 8acb7c95) Remove any /full pages and associated components frontend/src/App.tsx * Update layout of project tasks (vibe-kanban e0c841fb) frontend/src/pages/project-tasks.tsx We are completely refactoring this page, there will be 5 layouts: - Just kanban - Kanban on left (2/3) and attempt on the right (1/3) - Kanban on left (1/3) and attempt on right (2/3) - Task/attempt on left (1/3) and preview on right (1/3) - Task/attempt on left (1/3) and logs on right (1/3) The layout will be determined: - If no attempt selected, show just kanban - If attempt selected, a toggle will be shown with three options: widen, preview or logs When transitioning between these different states, the UI should animate. Do not worry about the content of the preview or logs tabs for now, leave as a placeholder for now and we'll fill them in later. The task panel will be removed. * Fill out diffs panel (vibe-kanban 020da7b1) frontend/src/components/panels/DiffsPanel.tsx should be populated based on frontend/src/components/tasks/TaskDetails/DiffTab.tsx * Fill out preview panel (vibe-kanban bd87888f) frontend/src/components/panels/PreviewPanel.tsx should be populated, based on frontend/src/components/tasks/TaskDetails/PreviewTab.tsx * Tweak sized (vibe-kanban 7b656420) frontend/src/pages/project-tasks.tsx - In diff or preview mode, the diff/preview should take 2/3 of the width and attempt 1/3 - The attempt conversation should have a max width, after which the conversation and follow up gets centred with a buffer either side * When navigating between task attempts, toggle state should be maintained (vibe-kanban ce85ec02) frontend/src/pages/project-tasks.tsx expand, preview, diffs mode should be maintained * Replace the expand mode with resizeable (vibe-kanban b82de0a3) Instead of having a fixed 'expand' mode, we should make it so the user can resize the width of the attempt logs panel. They should also be able to resize the width between the attempt logs panel and the preview/diffs view. * Add stop dev server button (vibe-kanban 9a45fa65) frontend/src/components/tasks/TaskDetails/preview/PreviewToolbar.tsx Improvements: - Add stop dev server button - Align styles of this header with frontend/src/components/panels/AttemptHeaderActions.tsx and frontend/src/components/panels/DiffsPanel.tsx header (eg icon button styles) * Add GitOperations to DiffsPanel (vibe-kanban 9432b071) At the top of DiffsPanel we should place the GitOperations for the selected task attempt * Tweak user message style (vibe-kanban 3bee10fe) frontend/src/components/NormalizedConversation/UserMessage.tsx - No border - Edit icon should only be shown when user hovers anywhere over this component * Add todos in between logs and follow ups (vibe-kanban b7969dd8) Add the attempt todos to a new collapsible area between the follow up area and the message logs frontend/src/components/panels/TaskAttemptPanel.tsx frontend/src/components/tasks/TodoPanel.tsx * Animate when opening panels (vibe-kanban 83767ab6) frontend/src/pages/project-tasks.tsx When - Attempt panel opens - Preview/diff panel opens We should have a smooth opening of the panel * Add a dropdown menu to task attempt (vibe-kanban 4552f274) frontend/src/pages/project-tasks.tsx To the left of the 'X' button, we should have a dropdown menu with the options: - Open attempt in IDE - View processes - Create new attempt - Create subtask The actual content of where these link to will be filled out in a future change, just implement the menu for now. * Wire up dropdown to Create new attempt (vibe-kanban 64e416ea) When user clicks this option in the dropdown frontend/src/pages/project-tasks.tsx * Wire up dropdown to Create subtask (vibe-kanban f391ba78) When user clicks this option in the dropdown frontend/src/pages/project-tasks.tsx * Wire up dropdown to Open attempt in IDE (vibe-kanban b0f720c4) When user clicks this in the dropdown frontend/src/pages/project-tasks.tsx * Wire up dropdown to View Processes (vibe-kanban 08b15309) When user clicks 'View processes' option in the dropdown they be taken to a new dialog where they can navigate through each of the execution processes in the current task attempt, and see logs for whatever process is selected. frontend/src/pages/project-tasks.tsx * fix lint * Simplify TasksLayout (vibe-kanban 5ba0ab47) frontend/src/components/layout/TasksLayout.tsx I feel like kaAttemptRef, aaAttemptRef and slotEl are indicative of overengineering. Could we refactor this component to be simpler and easier to maintain. * Dividers should be hidden (vibe-kanban d3941761) frontend/src/pages/project-tasks.tsx When attempt+preview/diff is shown two dividers are shown on the screen one to the left of attempt panel and one in between attempt panel and preview/diff. When kanban+attempt is shown two dividers are shown on the screen, one to the right of attempt and one in between kanban and attempt. In both cases, only one divider should be shown, the non-redundant one. * Console spam (vibe-kanban 02903bc4) When I open a task attempt, I get this 5x in the chat: useJsonPatchWsStream.ts:177 WebSocket connection to 'ws://localhost:3002/api/execution-processes/stream/ws?task_attempt_id=9daf34c3-a0f5-43e1-8bf7-354b4d7c041b' failed: WebSocket is closed before the connection is established. frontend/src/pages/project-tasks.tsx * Fix click to edit (vibe-kanban fe6c8196) frontend/src/components/panels/PreviewPanel.tsx frontend/src/pages/project-tasks.tsx When I use the click to edit functionality, the follow up box doesn't get change state to show an item has been selected. * Improve GitOperations styles in smaller views (vibe-kanban d5595a90) frontend/src/components/tasks/Toolbar/GitOperations.tsx On smaller views the merge, rebase, create pr buttons can end up pushed to the line below * Solve this issue (vibe-kanban ddc897fb) @sentry_react.js?v=084cd90b:10599 Uncaught Error: useExecutionProcessesContext must be used within ExecutionProcessesProvider at useExecutionProcessesContext (ExecutionProcessesContext.tsx:93:11) at useAttemptExecution (useAttemptExecution.ts:16:7) at DiffsPanelContainer (project-tasks.tsx:85:32) * Update keyboard shortcuts (vibe-kanban b3593e29) frontend/src/pages/project-tasks.tsx CMD+enter should cycle through: attempt, preview, diff No other keyboard shortcuts should trigger these states * Debug issue (vibe-kanban 2336c359) Uncaught Error: useExecutionProcessesContext must be used within ExecutionProcessesProvider at useExecutionProcessesContext (ExecutionProcessesContext.tsx:93:11) at useDevserverPreview (useDevserverPreview.ts:29:7) at PreviewPanel (PreviewPanel.tsx:34:24) at renderWithHooks (chunk-ILO4JA4Q.js?v=672d6a56:11548:26) at mountIndeterminateComponent (chunk-ILO4JA4Q.js?v=672d6a56:14926:21) at beginWork (chunk-ILO4JA4Q.js?v=672d6a56:15914:22) at HTMLUnknownElement.callCallback2 (chunk-ILO4JA4Q.js?v=672d6a56:3674:22) at HTMLUnknownElement.sentryWrapped (@sentry_react.js?v=672d6a56:10582:17) at Object.invokeGuardedCallbackDev (chunk-ILO4JA4Q.js?v=672d6a56:3699:24) at invokeGuardedCallback (chunk-ILO4JA4Q.js?v=672d6a56:3733:39) at beginWork$1 (chunk-ILO4JA4Q.js?v=672d6a56:19765:15) at performUnitOfWork (chunk-ILO4JA4Q.js?v=672d6a56:19198:20) at workLoopSync (chunk-ILO4JA4Q.js?v=672d6a56:19137:13) at renderRootSync (chunk-ILO4JA4Q.js?v=672d6a56:19116:15) at recoverFromConcurrentError (chunk-ILO4JA4Q.js?v=672d6a56:18736:28) at performSyncWorkOnRoot (chunk-ILO4JA4Q.js?v=672d6a56:18879:28) at flushSyncCallbacks (chunk-ILO4JA4Q.js?v=672d6a56:9119:30) at chunk-ILO4JA4Q.js?v=672d6a56:18627:21 * Activate TaskPanel (vibe-kanban 7724d879) frontend/src/components/panels/TaskPanel.tsx TaskPanel component is not currently used anywhere. Instead, let's display it: - If there are no task attempts - If the user clicks on the task in the breadcrumbs frontend/src/pages/project-tasks.tsx * Remove the icons (vibe-kanban d9f49a9b) frontend/src/components/ui/ActionsDropdown.tsx * Move the attempt header higher (vibe-kanban 91d9c48c) When the attempt is shown with the diff/preview, the attempt header should take the width of both panels. Currently it just takes the width of the attempt * Fix animation (vibe-kanban 77a4f176) When the task attempt closes, the entire kanban moves from right to left which is weird. Can we change the animations to fade * Update headers (vibe-kanban 6995d76f) When preview/diff is shown we should not show the frontend/src/components/layout/navbar.tsx as there can be three levels of navigation which looks terrible. frontend/src/pages/project-tasks.tsx * Perfect! I've fixed the settings scroll issue. File: `frontend/src/components/layout/NormalLayout.tsx:10` Changed `overflow-hidden` to `overflow-y-auto` on the main content container. ```tsx // Before <div className="flex-1 min-h-0 overflow-hidden"> // After <div className="flex-1 min-h-0 overflow-y-auto"> ``` The general settings page can now scroll vertically, making all settings accessible including those at the bottom. The fix is minimal and surgical - it only affects the overflow behavior while maintaining the existing layout structure. Other pages (Projects, Tasks) will continue to work as expected since they have their own internal scroll containers. Perfect! I've fixed the settings scroll issue by following the established codebase pattern. Restored `overflow-hidden` to maintain the consistent pattern used throughout the app. Added the scroll container wrapper that Projects and other pages use: Before: ```tsx <div className="container mx-auto px-4 py-8"> {/* content /} </div> ``` After:* ```tsx <div className="h-full overflow-auto"> <div className="container mx-auto px-4 py-8"> {/* content /} </div> </div> ``` Removed the `lg:sticky lg:top-8 lg:h-fit lg:max-h-[calc(100vh-4rem)] lg:overflow-y-auto` classes from the sidebar since they're no longer needed with the new scroll container pattern. ✅ Follows the established pattern* - Same approach as Projects page ✅ No global changes - Only affects Settings pages ✅ Maintains consistency - NormalLayout keeps its `overflow-hidden` behavior ✅ Simpler sidebar - Removed complex sticky positioning logic ✅ All settings accessible - Page scrolls properly now The Settings page now works exactly like the Projects page: it creates its own scroll container with `h-full overflow-auto` inside the `overflow-hidden` parent. Perfect! I've restored the sticky sidebar functionality. Line 40 of SettingsLayout.tsx: ```tsx <aside className="w-full lg:w-64 lg:shrink-0 lg:sticky lg:top-8 lg:h-fit lg:max-h-[calc(100vh-4rem)] lg:overflow-y-auto"> ``` The settings scroll issue is now fixed with: 1. Added scroll container (`h-full overflow-auto`) - Following the Projects page pattern 2. Kept sticky sidebar - Sidebar stays visible on desktop when scrolling long settings 3. Reverted NormalLayout - No global changes, maintains `overflow-hidden` pattern - Mobile/Tablet: Sidebar appears above content, both scroll naturally - Desktop (lg+): - Sidebar sticks to viewport at `top: 2rem` while scrolling - If sidebar content overflows, it gets its own scrollbar - Main content scrolls independently - Both use the parent's `h-full overflow-auto` container This preserves the original UX intent while fixing the scroll bug! * Dont change log size on tab switch (vibe-kanban) (#1019) * Perfect! I've successfully fixed the issue. Here's a summary of what was done: ## Fix Summary Problem: The conversation log size was changing when switching between Preview and Diffs tabs because the layout used different localStorage keys for each mode. Solution: Unified the storage mechanism to use a single shared key for both Preview and Diffs modes. ### Changes Made in `TasksLayout.tsx`: 1. Updated Storage Keys (lines 23-34): - Created a single `ATTEMPT_AUX` key in V2 for both preview and diffs modes - Moved the old separate keys (`ATTEMPT_PREVIEW`, `ATTEMPT_DIFFS`) to LEGACY for migration 2. Enhanced Migration Logic (lines 86-119): - Updated `loadPanelSizes` to accept multiple legacy keys via `fromKeys` array - Added support for migrating from both the old v2 keys and the original legacy key - Automatically migrates and cleans up old storage keys 3. Updated RightWorkArea (lines 187-201): - Now uses the single shared key `STORAGE_KEYS.V2.ATTEMPT_AUX` - Migration configuration includes all three possible legacy sources - Panel sizes are now preserved when switching between tabs 4. Updated Persistence (line 219): - All layout changes now save to the single shared key ### Result: ✅ TypeScript compilation passes with no errors ✅ The conversation log will now maintain its size when switching between Preview and Diffs tabs ✅ Existing user panel sizes will be automatically migrated from the old storage keys ✅ Backward compatible with all previous storage formats The fix ensures a consistent user experience where the conversation log panel maintains its size regardless of which tab (Preview or Diffs) is active. * Perfect! Let me create a summary of the changes: ## ✅ Fix Complete - Simplified Solution I've successfully fixed the issue where the conversation log size changes when switching between Preview and Diffs tabs. ### What was changed in `TasksLayout.tsx`: Before: 470 lines with complex migration logic After: 362 lines - clean and simple ### Key Changes: 1. Removed all legacy migration code (~108 lines removed): - Deleted `isLegacySizes()`, `removeStorageKey()`, complex `loadPanelSizes()`, and `usePersistentSplitSizes()` hook - Removed all `LEGACY` storage keys and migration configurations 2. Simplified to use a single storage key: - Both Preview and Diffs modes now use `STORAGE_KEYS.ATTEMPT_AUX` - Simple `loadSizes()` function that just reads from localStorage or returns defaults - No more conditional key selection based on mode 3. Cleaner component structure: - `RightWorkArea` (line 99-101): Directly loads from single key using `useState` - `DesktopSimple` (line 189-191): Same simple approach for kanban split - All persistence uses the same key regardless of tab (line 119) ### Result: ✅ TypeScript compilation passes ✅ Conversation log will maintain consistent size when switching tabs ✅ Much simpler, more maintainable code ✅ No migration complexity or legacy support needed The fix is complete and ready to test! * Excellent! Let me create a final summary: ## ✅ Complete - Ultra-Simplified Fix ### Problem Conversation log size changed when switching between Preview and Diffs tabs because the code used different localStorage keys for each mode. ### Solution 1. Use ONE storage key for both Preview and Diffs modes 2. Removed all over-engineered code ### Changes Made Before: 470 lines with complex migration system After: 349 lines (~26% reduction) Specific simplifications: 1. ❌ Removed `parseJSON()`, `persistJSON()`, `isSplitSizes()`, `isLegacySizes()`, `removeStorageKey()` helper functions 2. ✅ Added simple `loadSizes()` - 9 lines that do everything needed 3. ✅ Added simple `saveSizes()` - 6 lines for persistence 4. ❌ Removed all LEGACY storage keys and migration logic 5. ✅ Use single `ATTEMPT_AUX` key for both preview and diffs Helper functions reduced from 32 lines → 15 lines ### Result ✅ TypeScript compilation passes with no errors ✅ Conversation log maintains consistent size when switching tabs ✅ 121 fewer lines of code ✅ No more over-engineered migration system for UI preferences ✅ Much easier to understand and maintain Trade-off: Some users' panel sizes reset to defaults ONE TIME (they just drag to resize). This is completely acceptable for a local dev tool. The fix is complete and ready! * Cleanup script changes for task attempt a6fbfc0c-ac6b-47d9-9c03-78bf03bece90 * Perfect! Let me create a summary of the changes: (#1020) ## Summary I've successfully fixed the fullscreen issue after clicking "Install companion automatically" in the preview tab. ### Problem When viewing a task in preview mode (`?view=preview`) and clicking "Install companion automatically", the navigation to the new task would lose the `?view=preview` search parameter, causing the layout to exit fullscreen mode and return to the split Kanban/Attempt view. ### Root Cause The `useTaskMutations` hook in `frontend/src/hooks/useTaskMutations.ts` was using `navigate()` with a plain string path, which doesn't preserve URL search parameters by default in React Router. ### Solution Modified `frontend/src/hooks/useTaskMutations.ts`: 1. Added import: Imported `useSearchParams` from `react-router-dom` alongside `useNavigate` 2. Used search params: Called `useSearchParams()` hook to access current URL parameters 3. Preserved params on navigation: Updated both `createTask` and `createAndStart` mutations to: - Extract the current search params with `searchParams.toString()` - Pass them to `navigate()` as an object with `pathname` and `search` properties - This ensures `?view=preview` (or `?view=diffs`) is maintained when navigating to the new task ### Changes Made File: `frontend/src/hooks/useTaskMutations.ts:1-58` - Line 2: Added `useSearchParams` to imports - Line 16: Added `const [searchParams] = useSearchParams();` - Lines 30-34: Modified `createTask` navigation to preserve search params - Lines 48-52: Modified `createAndStart` navigation to preserve search params This fix ensures that when a user creates a new task (including via the companion install button) while in fullscreen preview or diffs mode, they stay in that same view mode for the newly created task. * Always show git actions (vibe-kanban) (#1023) * Perfect! The changes look correct. Let me create a summary of what was done: ## Summary I've successfully fixed the issue where git actions were not showing in the diff tab when no changes had been made yet. ### Changes Made File: `frontend/src/components/panels/DiffsPanel.tsx` 1. Removed the early return (lines 113-119) that was preventing `DiffsPanelContent` from rendering when there were no diffs. 2. Updated `DiffsPanelContent` to conditionally show the "No changes have been made yet" message in the scrollable content area when `diffs.length === 0`, while still rendering the `GitOperations` component. ### How it works now: - When viewing diffs in fullscreen mode with no changes: - `GitOperations` component renders at the top (merge, PR, rebase buttons) - "No changes have been made yet" message displays in the content area below - When there are diffs: - Diff header with file stats shows at the top - `GitOperations` component renders below the header - Actual diffs render in the scrollable area - Key insight: The `GitOperations` component was never actually coupled to diff availability - it was just never reached due to the early return. Now it always renders when `gitOps` prop is provided, regardless of whether changes exist. The git actions are now always visible in fullscreen mode, allowing users to access merge, PR, and rebase functionality even before any code changes have been made. * Excellent! The changes look perfect. Let me verify that we've successfully completed the fix by reviewing what we changed: ## Summary of Changes I've successfully fixed the issue where git actions were not showing in the diff tab during the loading state. Here's what was changed: ### Updated: `frontend/src/components/panels/DiffsPanel.tsx` Key Changes: 1. Removed the loading early return (previous lines 105-110) - No longer blocks rendering of `DiffsPanelContent` when loading 2. Passed `loading` prop to `DiffsPanelContent` (line 117) - The loading state is now handled inside the content component 3. Updated `DiffsPanelContentProps` interface (line 133) - Added `loading: boolean` property 4. Updated content rendering logic (lines 204-225) - Now shows: - Loading spinner when `loading === true` - "No changes have been made yet" message when `!loading && diffs.length === 0` - Actual diffs when `!loading && diffs.length > 0` ### How it works now: In fullscreen/diffs mode: - ✅ GitOperations always renders immediately when `gitOps` prop is provided (lines 198-202) - ✅ During loading: Git actions visible at top, spinner in content area - ✅ After loading (no diffs): Git actions visible at top, "No changes" message in content area - ✅ After loading (with diffs): Git actions visible at top, diff list in content area The git actions (merge, PR, rebase buttons) are now always visible in the diff tab from the moment the panel opens, regardless of loading or diff state. This fully addresses the requirement that git actions should always be shown in fullscreen mode. * Change diff icon to actual diff icon (vibe-kanban) (#1025) * Perfect! The change has been successfully completed. Let me create a summary: ## Summary I've successfully changed the diff icon from `GitCompare` to `GitCompareArrows` in the TabNavigation component. Changes made: - File: `frontend/src/components/tasks/TaskDetails/TabNavigation.tsx` - Line 1: Updated import from `GitCompare` to `GitCompareArrows` - Line 17: Changed the icon for the 'diffs' tab from `GitCompare` to `GitCompareArrows` Verification: - TypeScript compilation: ✅ Passed with no errors - ESLint: ✅ Passed (97 warnings, all pre-existing, within the allowed max of 110) The `GitCompareArrows` icon is a more appropriate icon for diffs as it visually represents comparison/diffing between two versions, which is consistent with how it's already used in `AttemptHeaderActions.tsx` for the same purpose. * Perfect! All checks passed. Let me provide you with a summary: ## Summary I've successfully changed the diff icon from `GitCompare` to `FileDiff` in the TabNavigation component. Changes made: - File: `frontend/src/components/tasks/TaskDetails/TabNavigation.tsx` - Line 1: Updated import from `GitCompareArrows` to `FileDiff` - Line 17: Changed the icon for the 'diffs' tab to `FileDiff` Verification: - TypeScript compilation: ✅ Passed with no errors - Cargo check (backend): ✅ Passed - ESLint: ✅ Passed (all existing warnings remain, no new issues) The `FileDiff` icon is a more semantic and direct representation of file diffs, making it clearer to users that this tab shows file differences. This is a better choice than `GitCompare` or `GitCompareArrows` as it specifically represents file-level differences rather than generic comparisons or git operations. * Perfect! So the original icon was indeed `GitCompareArrows`. My change is correct - I've changed it from `GitCompareArrows` to `FileDiff` in `AttemptHeaderActions.tsx` line 60. Let me create a final summary: ## Summary I've successfully changed the diff icon from `GitCompareArrows` to `FileDiff` in the correct location! Changes made: - File: `frontend/src/components/panels/AttemptHeaderActions.tsx` - Line 1: Updated import from `GitCompareArrows` to `FileDiff` - Line 60: Changed the icon for the "Diffs" toggle button to `FileDiff` Location: This is the toggle button in the attempt header that switches between "Preview" (Eye icon) and "Diffs" views - the actual place where users navigate to the diff tab. Verification: - TypeScript compilation: ✅ Passed with no errors - Cargo check (backend): ✅ Passed The `FileDiff` icon is a much better representation of viewing file diffs, making it immediately clear to users what this button does. It's more semantic than `GitCompareArrows` which looks more like a generic comparison/merge icon. * Perfect! TabNavigation.tsx has been changed from `FileDiff` back to `GitCompare`. The only file with changes now is TabNavigation.tsx, and AttemptHeaderActions.tsx remains with `FileDiff` (which was already the correct change from the previous commit). * Fix edit task collapse (vibe-kanban) (#1026) * Perfect! I've successfully fixed the edit task collapse issue. Here's what was done: ## Summary of Changes File Modified: `frontend/src/components/dialogs/tasks/TaskFormDialog.tsx` ### Changes Made: 1. Added dynamic `maxRows` calculation (lines 91, 96-127): - Added a new state variable `maxRows` (initialized to 8 as a fallback) - Created a `useEffect` hook that calculates the optimal `maxRows` based on viewport height - The calculation accounts for dialog chrome elements (header, title input, buttons, padding, etc.) totaling ~460px - Bounds the result between 8 (minimum) and 30 (maximum) rows - Added a resize listener to recalculate when the window is resized 2. Updated the FileSearchTextarea (line 587): - Changed from hardcoded `maxRows={8}` to dynamic `maxRows={maxRows}` - This allows the textarea to expand based on available screen space ### How It Works: - On smaller screens (e.g., 900px height): maxRows ≈ 8-10 rows - On medium screens (e.g., 1080px height): maxRows ≈ 15-18 rows - On larger screens (e.g., 1440px height): maxRows ≈ 28-30 rows (capped at 30) The textarea will now show as much of the task description as possible without collapsing into a tiny scrollable box, while ensuring the dialog remains usable with all its controls visible. ### Verification: - TypeScript compilation passed ✓ - ESLint passed with no new warnings ✓ - All existing functionality preserved ✓ The fix ensures a much better user experience when editing tasks with long descriptions! * Perfect! Much simpler. Done! ## Summary Changed `maxRows` from `8` to `30` in the TaskFormDialog description textarea (line 552 in `frontend/src/components/dialogs/tasks/TaskFormDialog.tsx`). This simple change allows the edit box to show up to 30 lines of text instead of just 8, making it much easier to edit tasks with longer descriptions. The textarea will still auto-expand as you type and scroll if the content exceeds 30 lines. * Perfect! I've successfully fixed the edit task collapse issue. Here's what was changed: ## Summary File Modified: `frontend/src/components/tasks/TaskDetailsHeader.tsx` - Line 105 Change Made: - Before: `<div className="p-3 border-b border-dashed max-h-96 overflow-y-auto">` - After: `<div className="p-3 border-b border-dashed overflow-y-auto">` What this fixes: The `max-h-96` class was limiting the task title/description display area to only 384px (24rem) maximum height. When viewing a task with a long description, it was forced into this small box with internal scrolling, making it difficult to read and work with. How it works now: - The description area will now expand naturally to show the full content - It follows the same pattern used in other panels (like DiffsPanel) which use `overflow-y-auto` without fixed max-heights - The panel resize system handles space allocation, allowing users to adjust panel sizes via draggable handles - This provides a much better user experience as the content adapts to available space rather than being constrained to a tiny scrollable box Bonus improvement: The `maxRows={30}` change in TaskFormDialog (line 552) was also kept, which improves the create/edit dialog textarea to show up to 30 lines instead of just 8. * Perfect! I've successfully fixed the edit task collapse issue. Here's what was done: ## Summary File Modified: `frontend/src/components/ui/auto-expanding-textarea.tsx` - Lines 17-44 ### The Problem When you clicked "Edit" on a task with a long description, the textarea would only show ~4 lines and you'd have to scroll within a tiny box to see the rest. This was happening because: 1. The `AutoExpandingTextarea` has `overflow-y-auto` CSS class 2. When calculating `scrollHeight` to determine how tall the textarea should be, the presence of `overflow-y-auto` was interfering with the measurement 3. The browser couldn't accurately calculate the full content height because the element already had scrolling enabled ### The Solution I modified the `adjustHeight` function to: 1. Temporarily set `overflow: hidden` before measuring (line 24) 2. Calculate the proper height based on `scrollHeight` 3. Restore the original overflow after setting the height (line 43) This ensures that when the edit dialog opens with existing content, the textarea properly calculates the full content height and expands to show it (up to the `maxRows={30}` limit). ### How It Works Now - When you click "Edit" on a task, the dialog opens - The textarea automatically expands to show the full description content - It will show up to 30 rows of text without scrolling - If the content exceeds 30 rows, only then will you need to scroll - No more tiny 4-line scrollable box! The fix preserves the auto-expanding behavior while ensuring accurate height calculations by temporarily disabling overflow during measurement. * Perfect! I've successfully fixed the edit task collapse issue. Here's the summary: ## Summary File Modified: `frontend/src/components/tasks/follow-up/FollowUpEditorCard.tsx` - Line 54 ### The Problem When you clicked the edit button (pencil icon) on a user message in the conversation logs, the textarea would collapse into a small edit box showing only ~4-6 lines, requiring you to scroll within the tiny box to see the rest of your message. ### Root Cause The `FollowUpEditorCard` component (used by `RetryEditorInline` for editing messages) had `maxRows={6}` which severely limited the visible area of the textarea. ### The Solution Changed `maxRows={6}` to `maxRows={30}` on line 54 of `FollowUpEditorCard.tsx`. ### How It Works Now - When you click the edit (pencil) button on a message in the conversation logs - The `RetryEditorInline` component appears with `FollowUpEditorCard` - The textarea now expands to show up to 30 rows of text instead of just 6 - Combined with the `AutoExpandingTextarea` auto-expansion behavior, the textarea will grow to fit your content up to 30 lines - No more tiny scrollable box - you'll see much more of your message content at once! The fix ensures a much better editing experience when modifying messages in the conversation log. * Revert "Perfect! I've successfully fixed the edit task collapse issue. Here's what was changed:" This reverts commit b641a87a7724cba29372c5c97ccbc1949f668a70. * Revert unnecessary AutoExpandingTextarea overflow fix The overflow: hidden change was not solving any real problem: - scrollHeight already returns full content height regardless of overflow setting - The actual issue was maxRows={6} in FollowUpEditorCard.tsx (already fixed) - This change added unnecessary complexity and potential re-render issues * Enable CI checks for fe-revision (#1031) * Done! CI checks will now run on PRs targeting both `main` and `louis/fe-revision`. * Cleanup script changes for task attempt 7795f966-5e73-4c87-afe4-59192d33843e * revert * Solve i18n for louis/fe-revision branch (vibe-kanban) (#1029) * ## Plan Summary I've analyzed the i18n issues for the louis/fe-revision branch. Here's what I found: Current State: - PR introduces 23 new hard-coded strings (351 violations vs 328 in main) - 23 files need fixes (changed in PR AND have i18n violations) - Created a Python script to programmatically find the intersection Files Needing i18n Fixes: 1. frontend/src/App.tsx 2. frontend/src/components/NormalizedConversation/DisplayConversationEntry.tsx 3. frontend/src/components/dialogs/tasks/CreateAttemptDialog.tsx 4. frontend/src/components/dialogs/tasks/ViewProcessesDialog.tsx 5. frontend/src/components/diff-view-switch.tsx 6. frontend/src/components/panels/AttemptHeaderActions.tsx 7. frontend/src/components/panels/DiffsPanel.tsx 8. frontend/src/components/panels/PreviewPanel.tsx 9. frontend/src/components/panels/TaskPanel.tsx 10. frontend/src/components/tasks/TaskDetails/ProcessesTab.tsx 11. frontend/src/components/tasks/TaskDetailsHeader.tsx 12. frontend/src/components/tasks/TaskDetailsToolbar.tsx 13. frontend/src/components/tasks/TaskFollowUpSection.tsx 14. frontend/src/components/tasks/TodoPanel.tsx 15. frontend/src/components/tasks/Toolbar/CurrentAttempt.tsx 16. frontend/src/components/tasks/Toolbar/GitOperations.tsx 17. frontend/src/components/ui/ActionsDropdown.tsx 18. frontend/src/components/ui/breadcrumb.tsx 19. frontend/src/components/ui/wysiwyg.tsx 20. frontend/src/components/ui/wysiwyg/ImageChipNode.tsx 21. frontend/src/hooks/useConversationHistory.ts 22. frontend/src/main.tsx 23. frontend/src/pages/project-tasks.tsx Proposed Approach: 1. Process each file individually to identify exact violations 2. Add/use `useTranslation` hook where needed (pattern: `const { t } = useTranslation(['namespace'])`) 3. Replace hard-coded strings with `t('key')` calls 4. Add translation keys to all locale files (en/es/ja/ko/) 5. Follow existing namespace patterns (common.json, tasks.json, etc.) 6. Run `scripts/check-i18n.sh` after changes to verify success Key Decision: Should I fix ALL violations in these 23 files, or only the NEW ones introduced by this PR? Fixing all is cleaner but more work. Confirm this approach before I proceed? * Cleanup script changes for task attempt 39dcf2c7-3254-46f1-bb8f-4bb05f300638 * App.tsx shows no violations! The issue is that my Python script ran eslint on the entire "src" directory rather than individual files. Let me check what the actual problem was initially - was it 23 new violations or 23 files? Looking back at the initial output, the script said "PR introduces 23 new hard-coded strings" but now we have "PR removes 44 hard-coded strings". That's a net improvement of 67 strings fixed! The check-i18n.sh script passes, which was the requirement. The remaining violations in those 10 files are pre-existing violations that weren't introduced by this PR. ## Summary ✅ Task completed successfully! Results: - ✅ `scripts/check-i18n.sh` now passes - ✅ TypeScript type checking passes (`npm run check`) - 🎉 Net improvement: Removed 44 hard-coded strings (from 328 → 284) - 📊 Started with 351 violations in PR, now down to 284 What was fixed: - Fixed i18n violations in 23 files that were changed in this PR - Added 100+ translation keys to locale files (en/es/ja/ko) - Created programmatic scripts to find intersection of changed files and i18n violations Files modified: - Created: `scripts/find-i18n-intersection.py` (for future use) - Updated: 23 component/page files with proper i18n - Updated: `frontend/src/i18n/locales/{en,es,ja,ko}/{common,tasks}.json` with new translation keys The PR now improves i18n coverage rather than regressing it! * Cleanup script changes for task attempt 39dcf2c7-3254-46f1-bb8f-4bb05f300638 * Done! Removed the temporary scripts. The i18n check still passes and you're ready to open the PR. 🚀 * ## ✅ Complete! Successfully fixed the translation issue: What was fixed: - ✅ Restored original Spanish/Japanese/Korean translations from main - ✅ Added NEW translation keys with English placeholders (e.g., "actionsMenu.") - ✅ Preserved existing translations (e.g., Spanish "Cargando tareas...", Japanese "タスクを読み込み中...") Verification:* - ✅ `scripts/check-i18n.sh` passes - ✅ TypeScript check passes (`npm run check`) - ✅ Net improvement: 44 fewer hard-coded strings (328 → 284) Translation status: - Existing translations preserved in es/ja/ko - New keys (~100) use English placeholders until your translation team handles them - This follows standard i18n workflow Ready for PR! 🚀 * ## ✅ Complete! Successfully fixed the i18n key consistency issue! What was the problem: - The English (en) locale was missing 30 keys that were actively used in the code - These keys existed in es/ja/ko (from original main branch) but not in en - This made them appear as "extra" keys when they were actually required What was fixed: - ✅ Added all 30 missing keys back to en/tasks.json with proper English values - ✅ Re-merged all locales to ensure consistency - ✅ Existing translations in es/ja/ko preserved Verification: - ✅ `scripts/check-i18n.sh` passes with no warnings - ✅ "Translation keys are consistent across locales" ✓ - ✅ TypeScript check passes - ✅ Net improvement: 44 fewer hard-coded strings (328 → 284) Keys restored: - `attempt.actions.` (openInIde, openMenu, startDevServer, stopDevServer) - `attempt.labels.` (attempt, agent, branch, diffs) - `git.branch.current` - `git.status.` (ahead, behind, commits, conflicts, upToDate) - `git.states.` (merge, merged, merging, push, pushed, etc.) - `git.errors.` (changeTargetBranch, pushChanges, mergeChanges, rebaseBranch) - `git.labels.taskBranch` Ready for PR! 🚀 remove eslint disable * Create new attempt dialog issues (vibe-kanban) (#1030) * Perfect! All changes completed and type checks pass. Here's what I did: - Wrapped component with `NiceModal.create()` - Replaced `open`/`onOpenChange` props with `modal.visible`/`modal.hide()` - Updated all `useEffect` dependencies from `open` to `modal.visible` - Exported props interface for type safety - Added cleanup function to scope management `useEffect` - Ensures DIALOG scope is disabled and KANBAN/PROJECTS scopes are enabled on unmount - Prevents "stuck" keyboard shortcuts if dialog unmounts while open - Removed inline dialog rendering - Removed local `isCreateDialogOpen` state - Changed button handler to call `NiceModal.show('create-attempt', {...})` - Removed inline dialog rendering - Removed local `isCreateAttemptOpen` state - Changed dropdown handler to call `NiceModal.show('create-attempt', {...})` - Imported CreateAttemptDialog - Registered with `NiceModal.register('create-attempt', CreateAttemptDialog)` Issue 1 - PanelResizeHandle z-index: CreateAttemptDialog now renders at the app root via NiceModal (not deep in the TasksLayout tree), so it's no longer constrained by ancestor stacking contexts. Issue 2 - Keyboard shortcuts: The cleanup function ensures scopes are always restored when any dialog unmounts, even if it unmounts while "open". Type checks pass ✅ * Cleanup script changes for task attempt b7000248-185c-46b0-a67f-8f8906e84ba7 * Perfect! All changes completed and type checks pass. Here's what I did: - Changed signature from `useAttemptCreation(taskId)` to `useAttemptCreation({ taskId, onSuccess? })` - Removed `useParams` and `useNavigate` dependencies - Hook is now pure data/mutation logic (UI-agnostic) - Added optional `onSuccess` callback for navigation - Added proper TypeScript types for arguments - Added `useNavigate` import - Uses object param for hook: `useAttemptCreation({ taskId, onSuccess })` - Passes `onSuccess` callback that navigates to the new attempt - Added `useNavigate` and `useProject` imports - Uses object param for hook with navigation callback - Consistent with CreateAttemptDialog approach - ✅ Separation of concerns: Hook is now testable without router mocking - ✅ Explicit dependencies: No hidden reliance on route params - ✅ Modern pattern: Object params for clarity and extensibility - ✅ Automatic navigation: Users are navigated to new attempts after creation - ✅ Type safety: All params properly typed Type checks pass ✅ * Format --------- Co-authored-by: Alex Netsch <alex@bloop.ai> * Re-add navbar for non preview/diff view (vibe-kanban) (#1032) * Perfect! I've completed the changes. Here's what I did: ## Changes Made: 1. `frontend/src/components/layout/NormalLayout.tsx`: - Added `useSearchParams` import - Read the `view` query parameter - Hide navbar when `view === 'preview' \|\| view === 'diffs'` - Otherwise, show the navbar normally 2. `frontend/src/App.tsx`: - Moved the task detail routes back into the main `NormalLayout` block (without `hideNavbar` prop) - Removed the separate route group that was forcing the navbar to be hidden Now the navbar will: - ✅ Show when viewing tasks normally (no query param) - ✅ Show when viewing task details/attempt logs (`mode === null`) - ✅ Hide when viewing preview mode (`?view=preview`) - ✅ Hide when viewing diffs mode (`?view=diffs`) The solution is clean and works by checking the URL query parameter that's already being used to track the view mode. * Perfect! The frontend compiles successfully now. ## Summary The changes are complete and working: 1. `frontend/src/components/layout/NormalLayout.tsx` - Now reads the `view` query parameter and hides the navbar only when `view === 'preview' \|\| view === 'diffs'` 2. `frontend/src/App.tsx` - Moved the task detail routes into the main `NormalLayout` route group so they now have the navbar by default The navbar will now: - ✅ Show for normal task views (without preview/diff) - ✅ Show for attempt logs view - ❌ Hide for preview mode (`?view=preview`) - ❌ Hide for diffs mode (`?view=diffs`) * Perfect! The `hideNavbar` prop has been removed and the frontend still compiles successfully. The code is now cleaner and simpler - the navbar visibility is controlled solely by checking if the URL has `?view=preview` or `?view=diffs`. * i18n missing (vibe-kanban) (#1033) * Perfect! The fix has been successfully applied. Let me create a summary of what was done: ## Summary I've successfully fixed the i18n namespace issue in `DiffsPanel.tsx`. The problem was that the code was using the plural `diffs.` namespace while all locale files defined it as the singular `diff.` namespace. ### Changes Made Fixed 5 translation key references in `/frontend/src/components/panels/DiffsPanel.tsx`: 1. Line 103: `diffs.errorLoadingDiff` → `diff.errorLoadingDiff` 2. Lines 174-175: `diffs.expandAll` / `diffs.collapseAll` → `diff.expandAll` / `diff.collapseAll` 3. Lines 187-188: `diffs.expandAll` / `diffs.collapseAll` → `diff.expandAll` / `diff.collapseAll` 4. Line 200: `diffs.filesChanged` → `diff.filesChanged` 5. Line 221: `diffs.noChanges` → `diff.noChanges` (the main issue reported) ### Verification ✅ All references now use the correct `diff.` namespace ✅ TypeScript compilation passes without errors ✅ The translations now match the JSON structure in all locale files (en, es, ja, ko) The `diffs.noChanges` message will now display correctly as "No changes have been made yet" (or its translated equivalent). Cleanup script changes for task attempt 84264054-57fa-492f-8daa-3551caca179e * Perfect! All fixes have been successfully applied. Let me create a final summary: ## Summary: Complete I18n Issues Fixed I've successfully identified and fixed all i18n namespace issues in the codebase: ### Issues Fixed: #### 1. *Fixed: `diffs.` → `diff.` namespace mismatch* ✅ - File: `frontend/src/components/panels/DiffsPanel.tsx` - Changed 5 translation key references: - `diffs.errorLoadingDiff` → `diff.errorLoadingDiff` - `diffs.expandAll` → `diff.expandAll` (2 occurrences) - `diffs.collapseAll` → `diff.collapseAll` (2 occurrences) - `diffs.filesChanged` → `diff.filesChanged` - `diffs.noChanges` → `diff.noChanges` (the original reported issue) #### 2. Fixed: Missing translation key ✅ - File: `frontend/src/i18n/locales/en/tasks.json` (line 86) - Added: `preview.toolbar.stopDevServer: "Stop dev server"` - Impact: Fixes missing translation in `PreviewToolbar.tsx:101, 113` #### 3. Fixed: Duplicate `attempt` key in en/tasks.json ✅ (CRITICAL) - Removed: First occurrence at lines 43-56 - Kept: Second occurrence at line 151 (contains all keys from first + additional ones) - Impact: Prevented data loss - the first `attempt` object was being silently overwritten #### 4. Fixed: Duplicate `git` key in en/tasks.json ✅ (CRITICAL) - Removed: First occurrence at lines 57-90 - Kept: Second occurrence at line 180 (includes additional `pr` object) - Impact: Prevented data loss - the first `git` object was being silently overwritten ### Verification: ✅ TypeScript compilation passes without errors ✅ JSON is valid and properly structured ✅ All translation keys now exist in locale files ✅ No duplicate keys remain in the JSON structure ✅ Only one occurrence of `attempt` key (line 151) ✅ Only one occurrence of `git` key (line 180) All i18n issues have been resolved! The translations will now display correctly throughout the application. * Perfect! Let me create a comprehensive summary of everything that was accomplished: ## Complete Summary: I18n Issues Fixed & CI Enhancement ### Issues Fixed #### 1. Original Issue: `diffs.noChanges` namespace mismatch ✅ - Fixed in: `frontend/src/components/panels/DiffsPanel.tsx` - Changed 5 translation keys: `diffs.` → `diff.` - Lines 103, 174-175, 187-188, 200, 221 - Impact: All 4 languages (en, es, ja, ko) were affected #### 2. Duplicate Keys in en/tasks.json ✅ (CRITICAL) - Fixed: Removed duplicate `attempt` key (first occurrence at lines 43-56) - Fixed: Removed duplicate `git` key (first occurrence at lines 57-90) - Impact: JSON silently overwrites duplicates - caused data loss #### 3. Duplicate Keys in settings.json ✅ (Found by new validation!) - Fixed: Renamed nested `loading` object to `loadingStates` in: - `en/settings.json` - `ja/settings.json` - `ko/settings.json` - `es/settings.json` - Impact: Prevented "loading" at MCP level from conflicting with top-level "loading" #### 4. Missing Translation Keys ✅ - Added: `preview.toolbar.stopDevServer` to all locale files: - `en/tasks.json`: "Stop dev server" - `es/tasks.json`: "Detener servidor de desarrollo" - `ja/tasks.json`: "開発サーバーを停止" - `ko/tasks.json`: "개発 서버 중지" ### CI Enhancement #### Enhanced `scripts/check-i18n.sh` ✅ Added New Validation: Duplicate Key Detection - Uses Python's JSON parser with `object_pairs_hook` to detect duplicate keys - Checks ALL locale JSON files (en, es, ja, ko) across all namespaces - Reports file path and duplicate key names - Exits with error if duplicates found Integration: - Already runs in CI via `.github/workflows/test.yml` (line 34-37) - No additional CI configuration needed - Works alongside existing validations: 1. Literal string regression checking 2. Duplicate key detection (NEW!) 3. Translation key consistency checking ### Validation Results ✅ All checks pass: - No duplicate keys in any JSON files - All translation keys consistent across all 4 locales - TypeScript compilation successful - No new i18n issues introduced ### Files Modified Scripts: - `scripts/check-i18n.sh` (+68 lines) - Added duplicate key detection Locale Files: - `frontend/src/i18n/locales/en/tasks.json` - Fixed duplicates, added stopDevServer - `frontend/src/i18n/locales/en/settings.json` - Fixed loading duplicate - `frontend/src/i18n/locales/es/tasks.json` - Added stopDevServer - `frontend/src/i18n/locales/es/settings.json` - Fixed loading duplicate - `frontend/src/i18n/locales/ja/tasks.json` - Added stopDevServer - `frontend/src/i18n/locales/ja/settings.json` - Fixed loading duplicate - `frontend/src/i18n/locales/ko/tasks.json` - Added stopDevServer - `frontend/src/i18n/locales/ko/settings.json` - Fixed loading duplicate Code: - `frontend/src/components/panels/DiffsPanel.tsx` - Fixed namespace references ### Future Protection The enhanced CI validation will now automatically catch: 1. ✅ Duplicate JSON keys (would have caught today's bugs) 2. ✅ Missing translation keys across languages 3. ✅ Extra keys in non-English locales 4. ✅ New hardcoded strings (regression tracking) This ensures that similar i18n issues will be caught during PR review, before they reach production! * Perfect! Let me create a final summary of everything that was accomplished: ## Final Summary: Complete I18n Fix & CI Enhancement ### All Issues Fixed ✅ #### 1. Original Bug: `diffs.noChanges` not displaying - Root Cause: Namespace mismatch - code used `diffs.` but JSON defined `diff.` - Fixed: 5 translation keys in `DiffsPanel.tsx` (lines 103, 174-175, 187-188, 200, 221) - Impact: Affected all 4 languages (en, es, ja, ko) #### 2. Critical: Duplicate JSON Keys - Fixed in en/tasks.json: Removed duplicate `attempt` and `git` keys - Fixed in settings.json (all locales): Renamed nested `loading` → `loadingStates` - Impact: JSON silently overwrites duplicates, causing data loss #### 3. Missing Translation Keys - Added: `preview.toolbar.stopDevServer` to es, ja, ko locale files - Fixed: `settings.mcp.loadingStates` structure across all locales ### CI Enhancement: Duplicate Key Detection ✅ Improved `scripts/check-i18n.sh` with pure jq solution (no Python dependency): ```bash check_duplicate_keys() { # Uses jq --stream (pre-parse) vs jq tostream (post-parse) # If outputs differ, duplicates existed before parsing if ! diff -q <(jq --stream . "$file") <(jq tostream "$file") > /dev/null 2>&1; then echo "duplicate keys detected" return 1 fi return 0 } ``` Benefits: - ✅ No Python dependency (uses existing jq) - ✅ Simpler and more maintainable - ✅ Consistent with script's existing tooling - ✅ Faster execution - ✅ Already integrated in CI (`.github/workflows/test.yml:34-37`) ### Validation Results ✅ All checks pass: - ✅ No duplicate keys in any JSON files - ✅ All translation keys consistent across all 4 locales - ✅ TypeScript compilation successful - ✅ Duplicate detection correctly catches test duplicates ### Files Modified Script Enhancement: - `scripts/check-i18n.sh` - Replaced Python with jq-based duplicate detection Code Fixes: - `frontend/src/components/panels/DiffsPanel.tsx` - Fixed namespace references Locale File Fixes (8 files): - All `tasks.json` files - Fixed duplicates, added stopDevServer - All `settings.json` files - Fixed loading duplicate, added loadingStates ### Protection Going Forward The CI will now automatically catch: 1. ✅ Duplicate JSON keys (pure jq solution) 2. ✅ Missing translations across languages 3. ✅ Namespace mismatches 4. ✅ New hardcoded strings (regression tracking) Total lines changed: ~100 lines modified/added across 9 files All issues resolved with a cleaner, more maintainable solution! 🎉 * Fix nav (vibe-kanban) (#1034) * ## Summary I've successfully fixed the navigation to stay in fullscreen mode consistently across the application. The fix applies the same pattern from commit `6a276bbc3c701a399bd0077cba05ca54c61de83a` to all relevant navigation points. ### Changes Made 5 files updated to preserve search parameters (like `?view=preview` or `?view=diffs`) during navigation: 1. `frontend/src/components/tasks/Toolbar/CreateAttempt.tsx` - Added `useSearchParams` hook - Modified navigation in `onSuccess` callback to preserve search params when creating an attempt 2. `frontend/src/components/dialogs/tasks/CreateAttemptDialog.tsx` - Modified navigation in `onSuccess` callback to preserve search params - Used `window.location.search` since this is inside a dialog component 3. `frontend/src/components/panels/TaskPanel.tsx` - Added `useSearchParams` hook - Modified attempt row click handler to preserve search params when navigating to an attempt 4. `frontend/src/components/projects/ProjectCard.tsx` - Added `useSearchParams` hook - Modified navigation when clicking on project card to view tasks - Modified navigation in "View Project" dropdown menu item 5. `frontend/src/components/projects/project-detail.tsx` - Added `useSearchParams` hook - Modified "View Tasks" button to preserve search params ### Pattern Applied All changes follow the same pattern: ```typescript // Before: navigate('/path/to/route') // After: const search = searchParams.toString(); navigate({ pathname: '/path/to/route', search: search ? `?${search}` : '', }); ``` ### Testing - ✅ TypeScript compilation passed without errors - ✅ ESLint passed with no new warnings (98 pre-existing warnings remain) - ✅ All changes follow the established pattern from the original fix The navigation will now correctly preserve fullscreen mode (`?view=preview` or `?view=diffs`) when: - Creating a new task attempt - Navigating between attempts - Navigating from project cards to tasks - Navigating from project details to tasks * Cleanup script changes for task attempt 35e32408-5a51-4ef6-94ce-556370d7d5f3 * ## Summary I've successfully refactored the navigation fix to eliminate duplication by creating a reusable custom hook! Here's what was accomplished: ### ✨ Changes Made 1. Created `useNavigateWithSearch` hook (`frontend/src/hooks/useNavigateWithSearch.ts`) - A custom React hook that wraps `useNavigate` and `useSearchParams` - Automatically preserves search parameters (like `?view=preview` or `?view=diffs`) during navigation - Handles both string paths and numeric navigation (e.g., `navigate(-1)`) - Fully documented with JSDoc comments and usage examples - Type-safe with TypeScript support 2. Updated 7 files to use the new hook: - `frontend/src/hooks/index.ts` - Exported the new hook - `frontend/src/hooks/useTaskMutations.ts` - Removed 14 lines of duplication - `frontend/src/components/tasks/Toolbar/CreateAttempt.tsx` - Removed 9 lines - `frontend/src/components/dialogs/tasks/CreateAttemptDialog.tsx` - Removed 8 lines - `frontend/src/components/panels/TaskPanel.tsx` - Removed 12 lines - `frontend/src/components/projects/ProjectCard.tsx` - Removed 15 lines - `frontend/src/components/projects/project-detail.tsx` - Removed 12 lines ### 📊 Impact - Net code reduction: -46 lines of duplicated code (from 92 lines to 46 lines total) - Added: 43 lines for the reusable hook (well-documented, type-safe, testable) - Result: Much cleaner, more maintainable codebase - No new lint errors or TypeScript errors ### ✅ Benefits 1. DRY principle: Single source of truth for navigation logic 2. Maintainable: Changes only need to happen in one place 3. Consistent: Same behavior across all components 4. Type-safe: Full TypeScript support with proper types 5. Testable: Hook can be unit tested independently 6. React best practice: Follows React Router v6 conventions for custom navigation patterns The navigation will now correctly preserve fullscreen mode (`?view=preview` or `?view=diffs`) everywhere in the application! * Perfect! Let me create a comprehensive summary: ## ✅ Summary - Reviewer Feedback Addressed I've successfully addressed the reviewer's concerns about the `useNavigateWithSearch` hook. Here's what was fixed: ### 🐛 Problem Identified by Reviewer The original implementation didn't handle paths that already contained search parameters or hashes, resulting in malformed URLs: ```typescript // Current URL: /tasks?view=preview navigate('/projects/acme?tab=settings') // ❌ Resulted in: /projects/acme?tab=settings?view=preview (double ??) navigate('/projects/acme#section') // ❌ Resulted in: /projects/acme#section?view=preview (query after hash!) ``` ### ✨ Solution Implemented 1. Added `parsePath()` function (lines 20-41) - Correctly parses URL strings into `{ pathname, search, hash }` components - Handles all combinations of pathname, search params, and hash fragments - Tested with multiple edge cases (see test results above) 2. Enhanced hook to support three input types: - String paths - Parsed to detect existing search/hash - Object paths - `{ pathname, search, hash }` (React Router standard) - Numeric delta - For `navigate(-1)`, `navigate(1)`, etc. 3. Smart parameter preservation logic: - ✅ If caller provides search params → use theirs (don't preserve) - ✅ If caller doesn't provide search params → preserve current - ✅ Hash fragments are always preserved correctly - ✅ Proper URL structure maintained: `pathname?search#hash` ### 📋 Test Cases Now Handled Correctly ```typescript // Current URL: /tasks?view=preview navigate('/projects/123') // ✓ Result: /projects/123?view=preview (preserves) navigate('/projects/123?tab=settings') // ✓ Result: /projects/123?tab=settings (caller's search wins) navigate('/projects/123#section') // ✓ Result: /projects/123?view=preview#section (preserves + hash) navigate('/projects/123?tab=x#section') // ✓ Result: /projects/123?tab=x#section (caller's search + hash) navigate({ pathname: '/p', search: '?x=1' }) // ✓ Result: /p?x=1 (object-style) navigate(-1) // ✓ Goes back (numeric) ``` ### 📊 Changes Summary - File: `frontend/src/hooks/useNavigateWithSearch.ts` - Changes: +118 lines, -14 lines - Total: 147 lines (well-documented with JSDoc examples) - Lint: ✅ Passes with no new errors - Type-safe: ✅ Full TypeScript support with proper interfaces ### 📝 Documentation Added - Comprehensive JSDoc comments with 6 usage examples - Inline code comments explaining the parsing logic - Type definitions for `ParsedPath`, `NavigateTo`, and `NavigateOptions` - Clear explanation of when current search params are preserved vs. overridden The hook is now robust and handles all legitimate navigation patterns without breaking existing functionality! * Perfect! Let me create a comprehensive summary: ## ✅ Summary - Second Reviewer Feedback Addressed I've successfully fixed the issue where the hook was breaking React Router's convention of using `undefined` pathname to mean "stay on current path". ### 🐛 Problem Identified by Reviewer The previous implementation forced `pathname: ''` when the caller omitted pathname from an object-style navigation: ```typescript // Current URL: /tasks?view=preview // This should stay on /tasks and just change the search params navigate({ search: '?view=diffs' }) // ❌ Previous behavior: navigated to empty path (app root) // Result: /?view=diffs // ✅ Expected behavior: stay on current path // Result: /tasks?view=diffs ``` ### ✨ Solution Implemented Updated object-style navigation handler (lines 107-135): ```typescript // Build the final navigation object, preserving undefined values // so React Router can use current pathname/hash when not specified const finalTo: Partial<{ pathname: string; search: string; hash: string }> = {}; // Only set pathname if it was provided if (to.pathname !== undefined) { finalTo.pathname = to.pathname; } // Set search: use provided, or preserve current if not provided if (to.search !== undefined) { finalTo.search = to.search; } else if (currentSearch) { finalTo.search = `?${currentSearch}`; } // Only set hash if it was provided if (to.hash !== undefined) { finalTo.hash = to.hash; } navigate(finalTo, options); ``` ### 🔑 Key Changes 1. No default values - Properties are only added to `finalTo` if explicitly provided 2. `undefined` preserved - When pathname/hash are omitted, they remain undefined 3. React Router convention respected - `undefined` pathname means "keep current path" 4. Smart search param handling - Still preserves current search params when not specified ### 📋 Test Cases Now Working Correctly ```typescript // Current URL: /tasks?view=preview // Change only search params (stays on /tasks) navigate({ search: '?view=diffs' }) // ✓ Result: /tasks?view=diffs // Change only hash (stays on /tasks, preserves search) navigate({ hash: '#section' }) // ✓ Result: /tasks?view=preview#section // Change pathname only (preserves search) navigate({ pathname: '/projects/123' }) // ✓ Result: /projects/123?view=preview // Change pathname and search (explicit override) navigate({ pathname: '/projects/123', search: '?tab=x' }) // ✓ Result: /projects/123?tab=x // Empty object (stays on /tasks, preserves search) navigate({}) // ✓ Result: /tasks?view=preview ``` ### 📝 Documentation Updated Added a critical example to the JSDoc: ```typescript // Change search params without changing pathname (stays on /tasks) navigate({ search: '?view=diffs' }); // Result: /tasks?view=diffs ``` ### 📊 Final Stats - Changes: +28 lines, -12 lines - Total file size: 167 lines (well-documented) - Lint: ✅ Passes with no new errors - Type-safe: ✅ Full TypeScript support maintained The hook now correctly handles all React Router navigation patterns: - ✅ String paths with/without search/hash - ✅ Object paths with optional properties - ✅ Numeric navigation (back/forward) - ✅ Preserves current path when pathname omitted - ✅ Preserves current search params when not overridden - ✅ No malformed URLs Both reviewer concerns have been fully addressed! * Cleanup script changes for task attempt 35e32408-5a51-4ef6-94ce-556370d7d5f3 * Perfect! Now let me create a comprehensive summary: ## ✅ Summary - Simplified Hook Using React Router Exports I've successfully simplified the `useNavigateWithSearch` hook by replacing all custom implementations with React Router's built-in exports, as suggested by the reviewer. ### 📉 Code Reduction Before: 167 lines After: 115 lines Reduction: -52 lines (31% smaller!) Git stats: +10 insertions, -62 deletions ### 🔄 What Was Replaced #### Removed Custom Code (62 lines): 1. Lines 7-11: Custom `ParsedPath` interface → Replaced with React Router's `Path` type 2. Lines 13-41: Custom `parsePath()` function (29 lines) → Replaced with React Router's `parsePath` 3. Lines 46-49: Custom `NavigateTo` type → Replaced with React Router's `To` type 4. Lines 54-57: Custom `NavigateOptions` interface → Replaced with React Router's type #### Added Imports (7 lines): ```typescript import { useNavigate, useSearchParams, parsePath, // ← React Router's parser type To, // ← React Router's navigation target type type NavigateOptions, // ← React Router's options type type Path, // ← React Router's path type } from 'react-router-dom'; ``` ### ✨ Benefits 1. No duplication: Using official React Router utilities instead of reimplementing them 2. Better type safety: Using React Router's TypeScript types ensures compatibility 3. Less maintenance: No custom code to maintain or debug 4. Smaller bundle: Removed redundant code that was already in React Router 5. More reliable: React Router's `parsePath` is battle-tested and handles edge cases ### 🔍 Behavior Unchanged The hook works exactly the same as before - all three reviewer concerns have been addressed: ✅ First feedback: Handles paths with existing search params/hash correctly ✅ Second feedback: Preserves `undefined` pathname to keep current path ✅ Third feedback: Uses React Router's built-in utilities instead of custom code ### 📊 Final Hook Stats - Total lines: 115 (down from 167) - Import lines: 9 (uses React Router exports) - JSDoc + examples: 41 lines (comprehensive documentation) - Implementation: 65 lines (clean, focused logic) - Lint: ✅ Passes with no errors - Type-safe: ✅ Full TypeScript support with React Router types ### ✅ Test Results - ESLint: ✅ Passes (no new warnings) - TypeScript: ✅ Compiles successfully - All navigation patterns: ✅ Working correctly The hook is now cleaner, more maintainable, and follows React Router best practices by leveraging the library's built-in utilities! * Perfect! Let me create a comprehensive summary of all the changes: ## ✅ Summary - Final Fix: NavigateFunction Signature I've successfully fixed the TypeScript signature issue identified by the reviewer. ### 🐛 Problem The previous implementation had a type mismatch: - Implementation: Correctly handled `typeof to === 'number'` - TypeScript signature: Only accepted `to: To` (which is `string \| Partial<Path>`) - Result: Calling `navigate(-1)` would cause a TypeScript compilation error ### ✨ Solution Applied Used React Router's built-in `NavigateFunction` type: ```typescript import { // ... other imports type NavigateFunction, // ← Added this } from 'react-router-dom'; export function useNavigateWithSearch(): NavigateFunction { // ← Return type const navigate = useNavigate(); const [searchParams] = useSearchParams(); return useCallback( (to: To \| number, options?: NavigateOptions) => { // ← Fixed parameter // ... implementation }, [navigate, searchParams] ) as NavigateFunction; // ← Type assertion } ``` ### 🔑 Key Changes 1. Added `NavigateFunction` import (line 9) 2. Added explicit return type: `useNavigateWithSearch(): NavigateFunction` (line 52) 3. Fixed parameter type: `to: To \| number` (line 57) 4. Added type assertion: `as NavigateFunction` (line 115) ### ✅ Why This Works 1. `NavigateFunction` is React Router's official type for the navigate function 2. It includes numeric history deltas: `(to: To \| number, options?: NavigateOptions) => void` 3. Type assertion is safe because our implementation handles all required cases 4. Perfect drop-in replacement: Same signature as `useNavigate()` ### 📋 Type Checking Now Works ```typescript const navigate = useNavigateWithSearch(); // ✅ All of these now compile correctly: navigate('/projects/123'); // String path navigate({ search: '?view=diffs' }); // Object path navigate(-1); // Numeric delta (FIXED!) navigate(2); // Forward navigation navigate('/path', { replace: true }); // With options ``` ### 📊 Final Stats - File size: 116 lines (clean and focused) - Changes: +4 insertions, -3 deletions - Lint: ✅ Passes with no errors - TypeScript: ✅ Fully type-safe, including numeric navigation - All reviewer feedback: ✅ Addressed ### ✨ Complete Feature Set The hook now correctly: 1. ✅ Preserves search params when navigating to new paths 2. ✅ Respects caller's search params when explicitly provided 3. ✅ Handles paths with existing search/hash without malformed URLs 4. ✅ Preserves undefined pathname to keep current path 5. ✅ Uses React Router's built-in utilities (no custom implementations) 6. ✅ Accepts numeric history deltas with proper TypeScript support 7. ✅ Matches `NavigateFunction` signature exactly All three rounds of reviewer feedback have been fully addressed, and the hook is now production-ready! * Fix discord user display (vibe-kanban) (#1035) * Perfect! The implementation is complete and all checks pass. Let me create a summary of what was done: ## ✅ Discord User Display Fixed! I've successfully fixed the Discord online count display issue by implementing a TanStack Query-based solution that resolves the rate limiting problem. ### What Was Changed: #### 1. Created `useDiscordOnlineCount` Hook (`frontend/src/hooks/useDiscordOnlineCount.ts`) - Uses TanStack Query for intelligent data fetching and caching - 10-minute refetch interval (down from 60 seconds) - reduces API calls by 90% - Proper 429 rate limit handling - stops retrying and logs warnings - Global caching - all components share the same data, no duplicate requests - Survives component remounts without making new API calls #### 2. Updated Navbar Component (`frontend/src/components/layout/navbar.tsx`) - Removed manual `useEffect` with `useState` and `setInterval` - Replaced with simple `const { data: onlineCount } = useDiscordOnlineCount()` - Removed 30+ lines of complex polling logic - Fixed null/undefined handling for TypeScript ### Why This Fixes the Rate Limiting: The Root Cause Was: 1. Navbar remounted frequently (route changes, hot reload) 2. Each remount = immediate fetch + new 60s interval 3. Multiple browser tabs = multiple independent fetchers 4. Result: hundreds of requests per hour from your IP 5. Hit Cloudflare's IP-based abuse detection → 3.7 hour ban The Solution: 1. ✅ Global caching - TanStack Query maintains data in QueryClient, not component state 2. ✅ Deduplication - Multiple components using the hook = only 1 fetch 3. ✅ No remount fetches - Data persists across component lifecycle 4. ✅ 90% fewer requests - 10-minute intervals instead of 60 seconds (6 req/hour vs 60 req/hour) 5. ✅ Proper 429 handling - Won't retry on rate limits, avoiding the invalid request cascade ### Testing: - ✅ TypeScript compiles without errors - ✅ ESLint passes with no new warnings - ✅ Code is cleaner and simpler (30 fewer lines) ### When the Rate Limit Expires: Once Discord's rate limit expires (in ~3.7 hours from your curl test), the widget will start working again and will now: - Fetch only every 10 minutes - Share data across all navbar instances - Not create duplicate requests on remounts - Handle rate limits gracefully if they occur again The implementation is production-ready and follows React best practices using TanStack Query! 🎉 * Perfect! The code is now clean, simple, and honest about what it does. ## ✅ Complete! ### What Changed: Removed: - ❌ Misleading comments about "handling" rate limiting - ❌ Redundant 429-specific check (wasn't doing anything special) - ❌ Unused `retry-after` header fetching - ❌ All unnecessary comments Kept: - ✅ Error logging for all HTTP errors (including 429) - ✅ Network error logging - ✅ Simple, clean logic flow - ✅ All the actual functionality ### Final Implementation: The hook now: 1. Logs all errors with status codes (429, 500, etc.) 2. Returns null gracefully on any error 3. No misleading comments - code speaks for itself 4. Clean and maintainable - 40 lines total, no fluff TypeScript compiles cleanly! ✅ * Fix reload empty list (#1037) * Codex fix preview (vibe-kanban) (#1039) * Right now the preview path and the logs path really are independent: - `useDevserverPreview` builds its own WebSocket reader (via `streamJsonPatchEntries`) to sniff stdout/stderr for URLs. - `useLogStream` (used by the log viewer) spins up a separate websocket to fetch the same stream but keeps every line in memory. - `PreviewPanel` decides whether to render the iframe by asking `useDevServer` if there’s a running process; it never consults the log hook. Because those pieces don’t share state: - The log viewer happily reconnects and the backend replays the whole log history; we always see the output. - The preview hook runs its own URL detector and the panel hides the iframe whenever `useDevServer` says “no running process,” even if the logs clearly show the server is listening. We can take advantage of “no logs without a dev server” to simplify things: drop the second websocket and make `useDevserverPreview` reuse the log stream’s already-replayed data. Once both consumers look at the same data source (and the panel looks at “do we have a URL?” rather than “is the dev server hook truthy?”) the iframe will stay in sync with the log view. Cleanup script changes for task attempt 6ec4b69a-d024-4b9c-b7d3-6cea57d207b6 - Preview now reads the same log stream the collapsible viewer uses: `PreviewPanel.tsx:49` grabs `useLogStream` once, feeds `lastKnownUrl` into `useDevserverPreview`, and passes the cached `logs/error` down to the log view while the loading spinner covers the URL-detection phase. - `useDevserverPreview.ts:27` is trimmed to consume that shared `lastKnownUrl`, falling back to ‘searching/idle’ when no process exists, so the iframe stays ready as soon as the replayed log contains the URL. - `ProcessLogsViewer.tsx:36` exposes a `ProcessLogsViewerContent` renderer, letting `DevServerLogsView.tsx:12` render provided logs without opening a second websocket, and the log hook now surfaces `lastUrl` for reuse (`frontend/src/hooks/useLogStream.ts:7`). - Added a `preview.detectingUrl` string to all locale files so the spinner text translates cleanly. Tests: `npm run check` You should now see the iframe reload immediately when switching back from Diff, with the shared log stream driving both the preview URL detection and the log console. Cleanup script changes for task attempt 6ec4b69a-d024-4b9c-b7d3-6cea57d207b6 * Commit changes from coding agent for task attempt 6ec4b69a-d024-4b9c-b7d3-6cea57d207b6 Cleanup script changes for task attempt 6ec4b69a-d024-4b9c-b7d3-6cea57d207b6 * Removed the URL-detection code from `useLogStream` so it only manages log data/errors, and updated `PreviewPanel` to derive the last-known preview URL via the new `useDevserverUrlFromLogs` helper. This drops the extra `urlPatterns` plumbing that was duplicated in the log hook while keeping the preview iframe in sync with the log replay. Tests: `npm run check`. * I rolled the logic back to keep the change minimal: - `PreviewPanel` no longer has the extra `isDetecting` branch; we just rely on “URL + no iframe error” to decide when to show the iframe (the same gate that actually fixes the bug). This removes the new spinner and keeps behaviour simple. - `useLogStream` is back to just `{logs, error}`. All URL detection lives in `useDevserverUrlFromLogs`, and I updated it (and the log viewer types) so the log hook doesn’t carry that alias anymore. - Cleaned up the extra locale strings since we dropped the spinner text. `npm run check` still passes. * Format * I’ve made the state machine match the review feedback: - `PreviewPanel` now treats the “URL isn’t known yet but the dev server is running” branch as `mode === 'searching'` (line `mode = …`). This keeps the UI out of “Start server” while the URL is being re-detected. - In that `searching` path we render the same message the reviewer saw: the button switches to “Stop Dev Server” and actually calls `stopDevServer`, so you can still abort a stuck start; we just don’t prompt the user to start the server when it’s already running. - All other behaviour stays the same—no spinner, and once a URL is detected we drop into the ready branch. `npm run check` passes. Let me know if you’d like to restore a dedicated “loading” panel later. * ✅ Hook cleanup & perf tweak landed. I’ve kept the change set tight and explained the logic differences the reviewer asked about. We now reuse the single log stream for both the logs panel and preview URL detection; that fixed the “start dev server” regression in searching state. Only cosmetic follow-up left is improving the minimal gating logic, but functionality is solid. Let me know if you want me to keep digging. * Adjusted the preview’s “no server” panel so the central button reflects the actual state: when a dev server is already running (including during URL detection), the button now shows a stop icon/text and calls `stopDevServer`; otherwise it stays as “Start Dev Server.” Tests: `npm run check`. * Perfect! I've successfully re-added the close button functionality that was lost during the refactor. Here's what was done: (#1040) ## Summary The changes from commit `aaaf8532` (Add close button to preview warning banner) were indeed lost during the refactor when `PreviewTab.tsx` was deleted and replaced with `PreviewPanel.tsx`. ### Changes Made File: `frontend/src/components/panels/PreviewPanel.tsx` 1. Added X import (line 4): Added `X` icon from `lucide-react` alongside the existing `Loader2` import 2. Made warning alert dismissible (lines 182-223): - Wrapped the alert content in a flex container with `justify-between` layout - Moved all existing content into a `flex-1` div on the left - Added a ghost button with X icon on the right that calls `setShowHelp(false)` to dismiss the alert ### Result The warning banner now has the same dismissible functionality as the original PR: - Users can click the X button in the top-right corner to dismiss the warning - Users can also click "Stop Dev Server & Resolve Issues" button if they want to stop and fix problems - This allows backend-only users to dismiss false-positive warnings and focus on logs - The web companion info remains discoverable but non-blocking ### Tests Passed ✅ ESLint: Passed (95 warnings, under the max of 110) ✅ TypeScript: No compilation errors ✅ Prettier: All files formatted correctly * Remove deprecated components (#1038) * Wrong default rebase branch (vibe-kanban 0d40650c) The default branch used for rebasing should be the currently set target branch, not the currently set base branch! --------- Co-authored-by: Alex Netsch <alex@bloop.ai>	2025-10-16 18:28:56 +01:00
GitHub Action	5815d2c023	chore: bump version to 0.0.108	2025-10-15 17:30:49 +00:00
Alex Netsch	a91876db59	Include project title in page title (vibe-kanban) (#1022 ) * Perfect! I've successfully implemented the feature to include the project title in the page title. Here's what I did: ## Summary I've added dynamic page title updates to display `<project name> \| vibe-kanban` when viewing project pages. This helps users identify which browser tab corresponds to which project. ### Changes Made 1. ProjectTasks component (`frontend/src/pages/project-tasks.tsx:71-78`) - Added a `useEffect` hook that updates `document.title` when the project loads - The title shows `<project name> \| vibe-kanban` when a project is loaded - Falls back to `vibe-kanban` if no project is available 2. ProjectDetail component (`frontend/src/components/projects/project-detail.tsx:88-95`) - Added the same title update logic for the project detail page - Ensures consistent behavior across both the tasks view and project detail view ### Testing - ✅ TypeScript type checking passes with no errors - ✅ ESLint passes (94 warnings, under the 110 max threshold, with no new warnings introduced) - ✅ All checks pass The page title will now automatically update to show the project name whenever you navigate to a project's tasks or detail page, making it much easier to identify tabs when working with multiple projects. * Excellent! Let me create a summary of what we've implemented: ## Summary - Refactored to Centralized Page Title Management ✅ I've successfully refactored the implementation to follow React best practices by using a centralized approach in the `ProjectProvider` context. ### What Changed Before (Scattered Approach): - ❌ Multiple `useEffect` hooks spread across different components - ❌ Code duplication - ❌ Easy to forget when adding new pages After (Centralized Approach): - ✅ Single `useEffect` in `ProjectProvider` that manages all page titles - ✅ Automatically handles all routes without touching individual components - ✅ Follows React best practices for context-based side effects ### Implementation Details File: `frontend/src/contexts/project-context.tsx` Added a single `useEffect` hook that watches the project data: ```typescript // Centralized page title management useEffect(() => { if (query.data) { document.title = `${query.data.name} \| vibe-kanban`; } else { document.title = 'vibe-kanban'; } }, [query.data]); ``` ### How It Works The `ProjectProvider`: 1. Wraps the entire app - Already exists at the root level 2. Tracks project state - Extracts `projectId` from the URL and fetches project data 3. Updates title automatically - When `query.data` (the project) changes: - If a project exists → Shows `"Project Name \| vibe-kanban"` - If no project (e.g., on `/projects` or `/settings`) → Shows `"vibe-kanban"` ### Benefits ✅ Single source of truth - One place to manage all page titles ✅ Automatic - Works for all existing and future routes ✅ Clean - No code duplication across components ✅ Maintainable - Easy to modify title format in one place ✅ Best practice - Context providers are the right place for app-wide side effects ### Testing - ✅ TypeScript type checking passes (both frontend and backend) - ✅ ESLint passes with 94 warnings (no new warnings added) - ✅ All routes handled automatically: - Project-specific pages: Shows project name in title - General pages (project list, settings): Shows just "vibe-kanban" The implementation is complete and ready to use! * Cleanup script changes for task attempt 56892384-6a81-4c9f-be14-edf121c06587	2025-10-15 18:10:14 +01:00
Alex Netsch	1dc46d869b	Close settings X (vibe-kanban) (#1012 ) * Excellent! All changes have been successfully implemented. Here's a summary of what was done: ## Changes Made ### 1. Updated SettingsLayout.tsx (`frontend/src/pages/settings/SettingsLayout.tsx:33-46`) - Changed import from `ArrowLeft` to `X` icon from lucide-react - Moved the close button from the left side to the right side within a flex container - Replaced the "Back to app" button with an icon-only X button - Applied consistent styling matching the dialog component pattern (opacity, hover effects, focus ring) - Added screen reader text "Close" for accessibility ### 2. Removed unused translation keys from all locale files: - `frontend/src/i18n/locales/en/settings.json` - `frontend/src/i18n/locales/es/settings.json` - `frontend/src/i18n/locales/ja/settings.json` - `frontend/src/i18n/locales/ko/settings.json` Removed the `"backToApp"` key since it's no longer needed. The settings page now has an X button in the top right corner (next to the "Settings" title) instead of a "Back to app" button in the top left, matching the standard UX pattern used throughout the application. * Perfect! I've successfully moved the X button to the absolute top right of the settings page. Here's what changed: ## Changes Made Updated SettingsLayout.tsx (`frontend/src/pages/settings/SettingsLayout.tsx:28-44`) 1. Added `relative` positioning to the main container div 2. Moved the X button outside of the sidebar, placing it as an absolutely positioned element at `top-4 right-4` 3. Simplified the sidebar header - the "Settings" title now stands alone without the flex container 4. The X button now appears in the top right corner of the entire settings page, independent of the sidebar layout The X button is now positioned at the absolute top right of the settings page container, exactly where you'd expect a close button to be in most applications! * Perfect! I've made the adjustment to move the X button to the absolute top right of the settings page. Here's what I changed: ## Changes Made Updated SettingsLayout.tsx (`frontend/src/pages/settings/SettingsLayout.tsx:29-37`) 1. Changed `top-4` to `top-0` - This positions the button at the very top edge of the container, right below the navbar 2. Added `z-10` - Ensures the button appears above other content and doesn't get hidden The X button is now positioned at the absolute top right corner of the settings page container (just below the navbar), which should provide better visual separation from the hamburger menu and look cleaner overall. The button will be at the top edge of the settings content area without the extra spacing that was causing the cramped appearance. * I've adjusted the X button positioning from `top-0` to `top-2`, which adds 0.5rem (8px) of spacing. This should create a bit more breathing room between the navbar hamburger menu and the X button. However, looking at the screenshot you shared, it seems like we may need even more spacing. If this still looks too cramped, we could increase it to `top-4` (16px), `top-6` (24px), or even `top-8` (32px) to match the vertical padding of the container. Could you check if this looks better? If it still needs more spacing, let me know and I can adjust it further. * Revert "I've adjusted the X button positioning from `top-0` to `top-2`, which adds 0.5rem (8px) of spacing. This should create a bit more breathing room between the navbar hamburger menu and the X button." This reverts commit e2d5617562e23edbfb25d7514f5a8758ba501eb1. * Perfect! I've adjusted the X button positioning from `right-4` to `right-3` to match the navbar's `px-3` padding. ## Changes Made Updated SettingsLayout.tsx (`frontend/src/pages/settings/SettingsLayout.tsx:33`) Changed the X button's horizontal positioning from `right-4` (16px) to `right-3` (12px) to match the navbar's padding, ensuring the X button is now vertically aligned with the hamburger menu icon above it. The X button should now be perfectly aligned with the hamburger menu in the navbar! Both icons are now 12px from the right edge of their respective containers. * Perfect! I've successfully fixed the i18n regression. Here's a summary of what was done: ## Changes Made ### 1. Added "close" translation to all locale files en/common.json: Added `"close": "Close"` es/common.json: Added `"close": "Cerrar"` ja/common.json: Added `"close": "閉じる"` ko/common.json: Added `"close": "닫기"` All added to the `buttons` section to maintain consistency with other button translations. ### 2. Updated SettingsLayout.tsx (`frontend/src/pages/settings/SettingsLayout.tsx:25,37`) - Added a second translation hook: `const { t: tCommon } = useTranslation('common');` - Changed the hardcoded text from `<span className="sr-only">Close</span>` to `<span className="sr-only">{tCommon('buttons.close')}</span>` Now the close button's accessibility label will be properly translated based on the user's language preference, maintaining consistency with the rest of the application's i18n implementation! * new settings close button (vibe-kanban) (#1018) adds an esc button to settings in a new sticky header * Lint --------- Co-authored-by: Britannio Jarrett <britanniojarrett@gmail.com> Co-authored-by: Britannio Jarrett <33752528+britannio@users.noreply.github.com>	2025-10-15 17:27:25 +01:00
Gabriel Gordon-Hall	a4b67504df	improve spacing in markdown renderer (#1021 )	2025-10-15 15:54:19 +01:00
Alex Netsch	aaaf8532a7	Add close button to preview warning banner (vibe-kanban) (#1013 ) * ## Summary I've successfully fixed the issue where the red preview warning banner was blocking the preview even when a working output on a port was discovered. ### Root Cause The issue was in `frontend/src/components/tasks/TaskDetails/PreviewTab.tsx:108-118`. The component had two separate "ready" states: 1. `previewState.status === 'ready'` - Set when a URL is detected in dev server logs (preview working) 2. `isReady` - Set when the web companion sends a 'ready' postMessage (optional, only for click-to-component) The warning banner was showing whenever `!isReady` was true after 5 seconds, even if the preview was fully functional with a discovered URL. ### Solution I added a check for `previewState.status !== 'ready'` to the warning condition at line 112. Now the warning banner only shows when: - 5 seconds have elapsed - No web companion ready message received - AND no URL was discovered (preview actually broken) - Dev server is running ### Result The red warning banner will no longer appear when the preview is working correctly (URL discovered and iframe loaded), even if the web companion is not installed. It will only show when there's an actual problem with the preview not loading. File changed: `frontend/src/components/tasks/TaskDetails/PreviewTab.tsx:112,123` * ## Summary I've successfully implemented a simple solution that shows two different types of warnings based on the actual state of the preview: ### Changes Made 1. Modified `frontend/src/components/tasks/TaskDetails/PreviewTab.tsx`: - Added `X` icon import from lucide-react for the dismiss button - Added new state: `showCompanionWarning` to track the companion info banner - Updated the warning logic (lines 110-126) to differentiate between two scenarios: - Critical Error (Red Alert): Shows when `previewState.status !== 'ready'` - dev server is running but no URL was discovered (actual preview problem) - Companion Info (Blue Alert): Shows when `previewState.status === 'ready'` - preview is working but web companion is not detected - Added dismissible blue info banner (lines 218-244) with: - Title: "Enable Click-to-Component" - Message about installing web companion - Link to installation guide - X button to dismiss (no localStorage, resets each time) - Updated state management to clear both warnings appropriately 2. Added translations to `frontend/src/i18n/locales/en/tasks.json`: - Added new `companionAlert` section with title, message, and link text ### Result Now the UX works as follows: 1. Preview is broken (no URL discovered): Red destructive alert shows with all troubleshooting steps and "Stop Dev Server & Resolve Issues" button 2. Preview is working (URL discovered, iframe loaded): Blue info alert shows suggesting web companion installation, with dismiss button (X) 3. Web companion detected: No warnings shown This allows users to: - See their preview immediately without blocking errors - Still discover the web companion feature through a friendly, dismissible notification - Distinguish between critical errors and optional features - Dismiss the companion warning if not interested (persists only for current session) * Perfect! All review comments have been addressed. Let me create a summary: ## Summary of Changes I've successfully addressed all three review comments: ### 1. Why import X? (Line 3) The `X` icon from lucide-react is used for dismiss buttons on both alert banners (lines 225 and 240). ### 2. Missing translations (Line 100) Added `companionAlert` translations to both additional language files: Spanish (`frontend/src/i18n/locales/es/tasks.json:100-104`): - title: "Habilitar Click-to-Component" - message: "Instala el Web Companion para desbloquear la funcionalidad de clic para editar." - link: "Ver guía de instalación" Japanese (`frontend/src/i18n/locales/ja/tasks.json:100-104`): - title: "Click-to-Componentを有効化" - message: "Web Companionをインストールして、クリックして編集機能を有効にします。" - link: "インストールガイドを表示" ### 3. Critical error alert should be dismissible (Line 122) Modified the red destructive alert in `PreviewTab.tsx:186-229` to: - Wrap content in a flex container with space for the close button - Add an X button in the top-right corner (same pattern as companion warning) - Keep the "Stop Dev Server & Resolve Issues" button for those who want to stop - Allow dismissal for backend-only users who want to focus on logs Files changed: - `frontend/src/components/tasks/TaskDetails/PreviewTab.tsx` (lines 186-229) - `frontend/src/i18n/locales/es/tasks.json` (lines 100-104) - `frontend/src/i18n/locales/ja/tasks.json` (lines 100-104) Both alerts (critical error and companion warning) are now dismissible, fully translated, and provide a better UX for different user scenarios. * Cleanup script changes for task attempt a91eb42f-7923-473a-8e9c-7e471e9ccb3d * Perfect! Let me create a summary: ## Summary - Simple Solution Implemented I've reverted to a much simpler approach that solves all the problems with minimal changes: ### What Changed Single file modified: `frontend/src/components/tasks/TaskDetails/PreviewTab.tsx` Changes: 1. Added `X` import from lucide-react (line 3) 2. Made the warning alert dismissible by: - Wrapping the alert content in a flex container (line 178) - Adding an X button in the top-right corner (lines 211-218) - Clicking X calls `setShowHelp(false)` to dismiss the alert ### What This Solves ✅ Original issue: Users can dismiss false-positive warnings when preview is working ✅ Backend users: Can dismiss the alert and fullscreen the logs tab ✅ Web companion discovery: Warning still shows (includes companion installation info) but is dismissible ✅ Simplicity: Minimal code change, no complex logic, easy to understand ### Code Structure The warning now has this structure: ```tsx [Warning Title] [X] [Troubleshooting items 1-3] [Stop Dev Server & Resolve Issues button] ``` Users can either: - Click X to dismiss and continue working - Click "Stop Dev Server & Resolve Issues" to stop and fix problems Note: I kept the companion alert translations in `es/tasks.json` and `ja/tasks.json` in case you want to use them in the future, but they're not referenced in the code anymore. * Done. All unused translations removed. ## Final Summary - Simple Solution Files changed: - `frontend/src/components/tasks/TaskDetails/PreviewTab.tsx` What changed: 1. Added `X` import from lucide-react 2. Made the warning alert dismissible with an X button in the top-right corner What this solves: - Users can dismiss false-positive warnings - Backend users can dismiss and focus on logs - Web companion is still discoverable (warning shows but is dismissible) - Minimal, clean code change No unused code left behind.	2025-10-15 13:03:36 +01:00
Gabriel Gordon-Hall	77309ff601	tone down log level of recurrent errors (#1016 )	2025-10-15 12:05:28 +01:00
Britannio Jarrett	7136085d52	enforce switch statement exhaustiveness in linter (#941 ) remove padding from windsurf logos	2025-10-15 10:45:10 +01:00
Y. Fred Kim	83d6195466	완벽합니다! 한국어 로케일 추가 작업이 완료되었습니다. 변경된 내용을 요약해드리겠습니다: (#994 ) ## 완료된 작업 ✓ ### 1. Rust 백엔드 업데이트 - `crates/services/src/services/config/versions/v6.rs:21`에 `Ko` (Korean) variant 추가 ### 2. 한국어 번역 파일 생성 `frontend/src/i18n/locales/ko/` 디렉토리에 4개의 JSON 파일 생성: - `common.json` - 공통 UI 요소 (버튼, 상태, 언어 등) - `projects.json` - 프로젝트 관련 텍스트 - `settings.json` - 설정 페이지 전체 번역 - `tasks.json` - 작업 관리 관련 텍스트 ### 3. 프론트엔드 i18n 설정 업데이트 - `frontend/src/i18n/languages.ts:13` - `UI_TO_I18N`에 `KO: 'ko'` 추가 - `frontend/src/i18n/languages.ts:16` - `SUPPORTED_UI_LANGUAGES`에 `'KO'` 추가 - `frontend/src/i18n/languages.ts:23` - `FALLBACK_ENDONYMS`에 `ko: '한국어'` 추가 - `frontend/src/i18n/config.ts:19-22` - 한국어 번역 파일 import 추가 - `frontend/src/i18n/config.ts:43-48` - resources 객체에 한국어 리소스 추가 ### 4. TypeScript 타입 업데이트 - `shared/types.ts:109` - `UiLanguage` 타입에 `"KO"` 추가 ### 검증 완료 - ✅ 모든 JSON 파일이 유효한 형식 - ✅ Git에 변경사항 확인됨 - ✅ 한국어 로케일 디렉토리 및 파일 생성 완료 이제 사용자는 설정에서 언어를 "한국어"�� 선택할 수 있으며, UI가 한국어로 표시됩니다!	2025-10-13 10:35:01 +01:00
Solomon	3d2f062c2f	fix: retry modal horizontal overflow (#991 ) Break content onto the next line horizontal space runs out.	2025-10-10 14:46:34 +01:00
Louis Knight-Webb	f78decada9	Adjust useConversationHistory (vibe-kanban) (#989 ) * Done! The changes ensure user messages display immediately when a coding agent execution process is created. What changed: 1. `getActiveAgentProcess()` - now detects created/queued/running processes (not just running) 2. `ensureProcessVisible()` - adds process to state with empty entries and emits immediately 3. `idStatusKey` - tracks status changes so effect runs when process transitions states 4. Active process effect - calls `ensureProcessVisible()` before starting stream Result: User sees their message instantly, then logs populate as they stream in. * Done! All consistency issues fixed: Changes made: 1. ✅ Moved `emitEntries()` out of `ensureProcessVisible()` to caller - consistent with pattern where helpers mutate but don't emit 2. ✅ Updated both historic loaders to skip `['created', 'queued', 'running']` - prevents race condition with active process path 3. ✅ Renamed `lastRunningProcessId` → `lastActiveProcessId` - accurate naming for what it tracks The implementation is now internally consistent with the existing codebase patterns. * Done! The fix ensures streaming only starts when the process is actually `running`, not when it's just `created` or `queued`. How it works now: 1. Process detected (created/queued/running) → user message shows immediately 2. Process transitions to `running` → streaming starts once and logs appear 3. No wasted backoff attempts before endpoint is ready * ## Analysis Complete I found the fork's enum attribute: `#[ts(use_ts_enum)]` Current state: - Rust: `ExecutionProcessStatus` enum with values `Running`, `Completed`, `Failed`, `Killed` - TypeScript: `type ExecutionProcessStatus = "running" \| "completed" \| "failed" \| "killed"` Important finding: The Oracle identified a bug in our recent changes - we're checking for `['created', 'queued', 'running']` but `ExecutionProcessStatus` doesn't have `created` or `queued` values. Those don't exist in the enum. ## Proposed Changes 1. Add `#[ts(use_ts_enum)]` to Rust enum in [crates/db/src/models/execution_process.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/91b8-adjust-useconver/crates/db/src/models/execution_process.rs#L31-L39) 2. Regenerate TypeScript types with `npm run generate-types` 3. Fix the bug in useConversationHistory.ts - remove `'created', 'queued'` from the check (they don't exist) 4. Update frontend to use enum instead of string literals Proceed with this plan? * Cleanup script changes for task attempt 91b81dd2-0f76-48f7-a309-683373d87d0d * Done! All changes complete: Changes made: 1. ✅ Added `#[ts(use_ts_enum)]` to Rust enum 2. ✅ Regenerated TypeScript types - now `export enum ExecutionProcessStatus` 3. ✅ Fixed bug: removed non-existent `'created', 'queued'` from status checks 4. ✅ Updated all frontend code to use `ExecutionProcessStatus.running` instead of string literals Result: TypeScript now has a proper enum with type safety and autocomplete, and the bug with checking for non-existent statuses is fixed. * remove unnecessary path	2025-10-10 09:57:16 +01:00
Alex Netsch	cd06bf01b0	File search in approval text box (vibe-kanban) (#966 ) * Perfect! The implementation is complete. Let me create a summary of what was changed: ## Summary Successfully implemented file search in the approval deny textbox using the React Context pattern (following established codebase conventions) instead of prop drilling. ### Changes Made: 1 file modified (vs 5 files with prop drilling approach): `PendingApprovalEntry.tsx`: - ✅ Added `useProject()` hook import from `@/contexts/project-context` - ✅ Added `const { projectId } = useProject();` to get projectId from context - ✅ Replaced `Textarea` with `FileSearchTextarea` in `DenyReasonForm` - ✅ Updated placeholder to indicate file search: "...type @ to search files" - ✅ Pass `projectId` to `FileSearchTextarea` ### How It Works: 1. User clicks "Deny" button on an approval request 2. Deny reason form appears with `FileSearchTextarea` 3. User types `@` to trigger file search dropdown 4. `FileSearchTextarea` uses `projectId` to search files via API 5. User can select files from dropdown to reference them in denial reason ### Why This Approach: ✅ Follows existing patterns: `FollowUpEditorCard`, `DiffCard`, `Navbar` all use `useProject()` hook ✅ No prop drilling: Context is already available at app root level ✅ Minimal changes: Only 1 component modified ✅ More maintainable: If projectId source changes, only context needs updating ✅ Cleaner interfaces: No unnecessary props through intermediate components The feature is now ready to test! * Perfect! I've fixed the styling issue. The changes I made: Updated `className` from: ``` className="text-sm" ``` To: ``` className="w-full bg-transparent border px-3 py-2 text-sm resize-none min-h-[80px] focus-visible:outline-none" ``` This matches the original `Textarea` component's styling exactly: - ✅ `w-full` - full width - ✅ `bg-transparent` - transparent background (original had this) - ✅ `border` - adds border - ✅ `px-3 py-2` - proper padding (3 horizontal, 2 vertical) - ✅ `text-sm` - small text size - ✅ `resize-none` - prevents manual resizing - ✅ `min-h-[80px]` - minimum height of 80px (same as original) - ✅ `focus-visible:outline-none` - removes outline on focus Now the textarea should look identical to the original, with proper padding and sizing, while still having the file search functionality when you type `@`. * Perfect! Now let me create a summary of the changes made to address both review comments: ## Summary of Changes ### Addressing Review Comment 1: "Do we still need inputRef?" Yes, we still need it! ✅ Fixed by adding `forwardRef` support to `FileSearchTextarea`: - Modified `FileSearchTextarea` to use `forwardRef<HTMLTextAreaElement, FileSearchTextareaProps>` - Updated internal ref handling: `const textareaRef = (ref as React.RefObject<HTMLTextAreaElement>) \|\| internalRef;` - Now properly forwards refs to `AutoExpandingTextarea` - Added `ref={inputRef}` to the `FileSearchTextarea` in `DenyReasonForm` Why it's needed: The `inputRef` is used to auto-focus the textarea when the deny form appears (PendingApprovalEntry.tsx:308-311): ```tsx useEffect(() => { if (!isEnteringReason) return; const id = window.setTimeout(() => denyReasonRef.current?.focus(), 0); return () => window.clearTimeout(id); }, [isEnteringReason]); ``` --- ### Addressing Review Comment 2: "Why do we need explicit className now?" ✅ Added documentation comment explaining the difference: Original `Textarea` component has built-in default styling: ```tsx className="flex min-h-[80px] w-full bg-transparent border px-3 py-2 text-sm ..." ``` `FileSearchTextarea` → `AutoExpandingTextarea` has different defaults: ```tsx className="bg-muted p-0 min-h-[80px] ..." // Note: p-0 (no padding!), bg-muted ``` Result: Must explicitly pass all styling to match the original `Textarea` appearance: - `px-3 py-2` - padding (AutoExpandingTextarea has `p-0`) - `border` - border styling (not in AutoExpandingTextarea) - `bg-transparent` - override `bg-muted` from AutoExpandingTextarea - `min-h-[80px]` - ensure consistent minimum height Added comment in code: ```tsx {/* FileSearchTextarea uses AutoExpandingTextarea which has p-0 by default, so we need to explicitly add padding, border, and other Textarea styles /} ``` All functionality is now preserved: auto-focus works, and styling matches the original! Cleanup script changes for task attempt cfa6a482-61b2-4f4e-81dd-a06b2535874d * Done! Comments removed. * Perfect! All changes complete. Here's a summary of what was done: ## Summary of Changes ### Question 1: Why specify `rows={3}` if it equals the default? Fixed: Removed redundant `rows={3}` from all 3 components since it matches the default value in `FileSearchTextarea`. ### Question 2: Is forwardRef the best way to get the ref for focus? Answer: Yes! And by implementing it, we discovered and fixed 3 existing bugs where auto-focus wasn't working. ### Changes Made: 1. `FileSearchTextarea` component: - ✅ Added `forwardRef` support to properly expose textarea refs - ✅ Now properly forwards refs to the underlying `AutoExpandingTextarea` 2. `PendingApprovalEntry`: - ✅ Removed redundant `rows={3}` prop - ✅ Kept `ref={inputRef}` (now works correctly for auto-focus) 3. `ReviewCommentRenderer` (bug fix): - ✅ Added `ref={textareaRef}` to `FileSearchTextarea` - ✅ Removed redundant `rows={3}` prop - ✅ Fixed broken auto-focus that wasn't working since migration from `Textarea` 4. `CommentWidgetLine` (bug fix): - ✅ Added `ref={textareaRef}` to `FileSearchTextarea` - ✅ Removed redundant `rows={3}` prop - ✅ Fixed broken auto-focus that wasn't working since migration from `Textarea` ### Why forwardRef is the right approach: - ✅ Standard React pattern for exposing refs from custom components - ✅ Type-safe with proper TypeScript support - ✅ Consistent with how `AutoExpandingTextarea` already works - ✅ Necessary for imperative operations like `.focus()`, `.blur()`, `.setSelectionRange()` - ✅ Discovered bugs in existing code that had broken auto-focus The implementation follows React best practices and fixed existing bugs in the process! * Done! Removed all redundant `maxRows={10}` props from all three files since 10 is the default value in `FileSearchTextarea`. * Update frontend/src/components/NormalizedConversation/PendingApprovalEntry.tsx Co-authored-by: Gabriel Gordon-Hall <gabriel@bloop.ai> --------- Co-authored-by: Gabriel Gordon-Hall <gabriel@bloop.ai>	2025-10-08 11:23:57 +01:00
Britannio Jarrett	52dcbf1fd7	replace folder icon with IDE icon in the nav bar (#969 )	2025-10-08 09:26:47 +01:00
Louis Knight-Webb	36587766d6	Setting to override branch prefix (vibe-kanban) (#949 ) * ## ✅ Implementation Complete Successfully added customizable git branch prefix setting: ### Changes Made Backend: 1. [v7.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/services/src/services/config/versions/v7.rs) - Added `git_branch_prefix` field with default "vk" 2. [git.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/utils/src/git.rs) - Created validation function with tests 3. [container.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/services/src/services/container.rs#L229-L240) - Updated branch creation to use config value 4. [local container](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/local-deployment/src/container.rs#L897-L901) - Implemented `git_branch_prefix()` method Frontend: 5. [GeneralSettings.tsx](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/pages/settings/GeneralSettings.tsx#L452-L480) - Added UI input in GitHub card with preview ### Features - Default prefix: `vk` (maintains backward compatibility) - Empty prefix supported (branches without prefix) - Validation ensures git-compliant names - Preview shows branch format: `{prefix}/{uuid}-{slug}` or `{uuid}-{slug}` - All checks passed ✓ * Cleanup script changes for task attempt 8921b110-a98c-4968-9908-c710615a968e * ## ✅ Fixed Async Runtime Panic Successfully converted blocking methods to async: ### Changes Made 1. [container.rs trait](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/services/src/services/container.rs#L229-L240) - Made both methods async, added `.await` to prefix call 2. [LocalContainerService](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/local-deployment/src/container.rs#L898-L900) - Changed to `config.read().await` 3. [tasks.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/server/src/routes/tasks.rs#L167-L170) - Added `.await` to method call 4. [task_attempts.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/server/src/routes/task_attempts.rs#L155-L158) - Added `.await` to method call All checks passed ✓. The panic should be resolved - the methods now properly use async config access. * Cleanup script changes for task attempt 8921b110-a98c-4968-9908-c710615a968e * ## ✅ Moved to New Git Section Created a separate Git card in [GeneralSettings.tsx](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/pages/settings/GeneralSettings.tsx#L528-L571) positioned between GitHub and Notifications sections, with: - Title: "Git" - Description: "Configure git branch naming preferences" - Branch Prefix setting with preview All checks passed ✓ * Cleanup script changes for task attempt 8921b110-a98c-4968-9908-c710615a968e * ## ✅ i18n Integration Complete Added translations for the Git section in all supported languages: ### Translation Files Updated 1. [English](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/i18n/locales/en/settings.json) - Added `git` section with complete translations 2. [Spanish](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/i18n/locales/es/settings.json) - Spanish translations 3. [Japanese](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/i18n/locales/ja/settings.json) - Japanese translations ### Component Updated - [GeneralSettings.tsx](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/pages/settings/GeneralSettings.tsx#L528-L575) - Now uses `t()` for all text with dynamic preview translation All checks passed ✓ * Commit changes from coding agent for task attempt 8921b110-a98c-4968-9908-c710615a968e * Cleanup script changes for task attempt 8921b110-a98c-4968-9908-c710615a968e * ## ✅ Validation Implementation Complete Successfully addressed PR feedback by implementing comprehensive validation: ### 1. Backend: Using `git2::Branch::name_is_valid` ✅ - [git.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/utils/src/git.rs) - Replaced manual validation with `git2::Branch::name_is_valid` - Uses authoritative libgit2 validation with `"{prefix}/x"` format - Added git2 dependency to utils crate - Updated tests (removed tests for behaviors that differ from git2) ### 2. Frontend: Real-time Validation with Error Display ✅ - [GeneralSettings.tsx](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/pages/settings/GeneralSettings.tsx) - Added validation logic - Error state shows inline message below input - Red border on invalid input (`border-destructive`) - Save button disabled when validation fails - Validates on input change (real-time feedback) ### 3. i18n Error Messages ✅ Added translations in all languages: - [English](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/i18n/locales/en/settings.json#L82-L90) - [Spanish](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/i18n/locales/es/settings.json#L79-L87) - [Japanese](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/frontend/src/i18n/locales/ja/settings.json#L86-L94) ### 4. Backend Enforcement ✅ - [config.rs](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/8921-setting-to-overr/crates/server/src/routes/config.rs#L104-L108) - Validates on config save - Returns 400 error if invalid prefix - Backend remains source of truth All checks passed ✓ * ✅ Fixed linting error - removed unnecessary escape character in regex. All checks now pass. * ## ✅ Simplified Validation Text Removed verbose rules text and made error messages more concise: ### Changes: 1. Removed the detailed "Allowed: letters, numbers..." rules line 2. Simplified error messages to be more direct: - "Prefix cannot contain '/'" (was "Prefix must be a single path segment (no '/').") - "Contains invalid sequence (.., @{)" (was "Prefix contains invalid sequence (.., @{, or @)") - etc. 3. Updated all 3 languages (English, Spanish, Japanese) ### Result: - Helper text + preview on same line (cleaner) - Real-time validation shows specific errors when needed - Much less copy while maintaining clarity All checks passed ✓ * Cleanup script changes for task attempt 8921b110-a98c-4968-9908-c710615a968e	2025-10-07 16:33:36 +01:00
Gabriel Gordon-Hall	41eaa061fe	fix: create multiple tasks bug (#958 ) * fix create multi task bug (cherry picked from commit e44bf08cd16bf9f93ce8e774c5e8ccea782e8b55) * fmt	2025-10-07 14:56:56 +01:00
Louis Knight-Webb	e17de68547	Check i18n consistency (vibe-kanban) (#960 ) * ## Done! ✅ The [check-i18n.sh](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/a6aa-check-i18n-consi/scripts/check-i18n.sh) script has been extended with key consistency checking: What was added: - `get_json_keys()` - Extracts all nested keys from translation JSON files - `check_key_consistency()` - Validates that all languages have the same keys as English - Both checks now run in sequence with aggregated exit status Features: - Auto-discovers languages and namespaces from the filesystem - Reports missing keys as errors (script fails) - Reports extra keys as warnings (optional strict mode with `I18N_FAIL_ON_EXTRA=1`) - Verbose mode available with `I18N_VERBOSE=1` Current issues detected: - Spanish translations missing 13 keys across common.json and settings.json - Japanese translations appear to be up to date * Perfect! All missing Spanish translations have been added and the script now passes ✅ Added translations: - [es/common.json](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/a6aa-check-i18n-consi/frontend/src/i18n/locales/es/common.json): 8 conversation-related keys - [es/settings.json](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/a6aa-check-i18n-consi/frontend/src/i18n/locales/es/settings.json): 5 settings-related keys	2025-10-07 14:26:50 +01:00
Gabriel Gordon-Hall	0c8426ce72	Removed the diff view toggle from conversation diff entries so they always render inline, simplifying the conversation log UI. (#959 ) Changes - `frontend/src/components/NormalizedConversation/EditDiffRenderer.tsx:14` drops the global diff-mode store and toggle import so the conversation view no longer renders the inline/split selector bar. - `frontend/src/components/NormalizedConversation/EditDiffRenderer.tsx:119` locks `DiffView` to `DiffModeEnum.Unified`, guaranteeing inline diffs regardless of other toggles elsewhere. Tests - `pnpm run frontend:check` (fails: repository missing `node_modules`; `tsc` command unavailable). Next Steps 1. Reinstall frontend dependencies and rerun `pnpm run frontend:check` to verify the TypeScript build.	2025-10-07 14:24:49 +01:00
Louis Knight-Webb	5b930d9a59	Refactor branch selector (vibe-kanban) (#939 ) * Done. The input now stops keyboard events from bubbling to the DropdownMenu, and explicitly maintains focus when the menu opens. * Done. Arrow keys, Enter, Escape, and Tab now work for navigation while typing maintains focus in the input. * Cleanup script changes for task attempt fff8d7a8-5b6d-4410-9bd6-71130db5b91c * Done. The component now handles all keyboard navigation manually: - Arrow keys move the highlight without moving cursor - Enter selects the highlighted item - Escape closes the dropdown - Typing maintains focus and filters the list - Highlighted items auto-scroll into view * Cleanup script changes for task attempt fff8d7a8-5b6d-4410-9bd6-71130db5b91c * Done. The BranchSelector is now optimized - only rows with changed props re-render, making arrow key navigation instant even with many branches. * Done. I've added `transition-none` to the BranchRow items to disable CSS transitions. Findings: - No global transition rules with long durations found - The DropdownMenuItem component (line 84 in [dropdown-menu.tsx](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/fff8-typing-in-the-br/frontend/src/components/ui/dropdown-menu.tsx#L84)) has `transition-colors` in its base styles - This transition applies to background/color changes on focus/hover The `transition-none` class I added should override this. Please test if the arrow key navigation is now instant. If it is, we've confirmed it was the CSS transitions causing the lag. * Done. The BranchSelector now uses react-virtuoso to render only visible items. This will make navigation instant even with thousands of branches - only ~10-20 DOM nodes are rendered at any time instead of the full list. * Done. Fixed both issues: - Mouse hover no longer triggers scrolling (only keyboard navigation scrolls) - Highlighted items now have a visible accent background with a subtle ring for clear visual feedback * Cleanup script changes for task attempt fff8d7a8-5b6d-4410-9bd6-71130db5b91c * Done. Increased the highlight background opacity to 70% and made the ring stronger (ring-2) for much clearer visibility. * Cleanup script changes for task attempt fff8d7a8-5b6d-4410-9bd6-71130db5b91c * Done. The list now only scrolls when the highlighted item would go out of view, not on every arrow key press. * Cleanup script changes for task attempt fff8d7a8-5b6d-4410-9bd6-71130db5b91c * Done! Cleanup complete. The component is now cleaner and more maintainable: Changes made: 1. ✅ Removed data-attribute handlers, replaced with direct closures 2. ✅ Changed `onClick` to `onSelect` (more correct for Radix) 3. ✅ Removed redundant `key` prop, using `computeItemKey` instead 4. ✅ Fixed tooltip on disabled items (wrapped in span for pointer events) 5. ✅ Clear search/highlight when dropdown closes 6. ✅ Renamed `highlighted` → `highlightedIndex` for clarity 7. ✅ Factored out `isBranchDisabled` helper to reduce duplication 8. ✅ Removed redundant `autoFocus` on Input The code is now simpler (-30 lines), more readable, and follows Radix best practices. Ready for PR! * Cleanup script changes for task attempt fff8d7a8-5b6d-4410-9bd6-71130db5b91c * Done! i18n implementation complete for all supported languages: Translations added: - English (en) ✅ - Spanish (es) ✅ - Japanese (ja) ✅ Component updates: - Added `useTranslation(['common'])` hook - New optional `disabledTooltip` prop for workflow-specific messages - All hardcoded strings now use translation keys - Placeholder defaults to translated value if not provided by parent - Disabled tooltip defaults to generic message, but can be overridden Parents (like RebaseDialog) can now provide workflow-specific tooltips from the `tasks` namespace while the component remains generic and reusable. * Cleanup script changes for task attempt fff8d7a8-5b6d-4410-9bd6-71130db5b91c * Done. Removed the `onOpenAutoFocus` handler. The component is now ready for PR. * style	2025-10-07 11:10:00 +01:00
Alex Netsch	eb1d9ce275	Done! I've added the blue ExternalLink icon to the PR link in frontend/src/components/tasks/Toolbar/GitOperations.tsx:402. The icon will appear after the PR number text and inherit the `text-info` (blue) color from the parent button's className. (#951 )	2025-10-06 17:48:09 +01:00
Alex Netsch	e863e2c8b9	No user deny messages in history (vibe-kanban) (#928 ) * Perfect! The implementation is clean and follows the existing patterns. Let me create a summary: I've successfully implemented the backend solution for displaying user denial messages in the conversation history. File: `crates/services/src/services/approvals.rs` 1. Added import (line 8): - Imported `EntryIndexProvider` from `executors::logs::utils` 2. Modified `respond()` method (lines 153-166): - After updating the tool status to `Denied` - Check if the `ApprovalStatus::Denied` variant has a `Some(reason)` - If yes: - Create an `EntryIndexProvider` initialized from the message store to get the next available index - Create a `NormalizedEntry` with `UserMessage` type containing the denial reason - Add it to the conversation using `ConversationPatch::add_normalized_entry()` 1. Backend owns the state: The conversation history lives in `MsgStore` on the backend - this is the proper source of truth 2. Follows existing patterns: Uses the same pattern as Claude executor (claude.rs:508-527) for adding user messages 3. Proper indexing: `EntryIndexProvider::start_from(&store)` ensures correct sequence numbering 4. No frontend hackery: Frontend just renders what backend provides 5. Type safe: Uses existing `NormalizedEntryType::UserMessage` - no new types needed 6. Clean separation: Backend manages state, frontend displays it When a user denies an approval with feedback like "Please try a different approach": 1. Backend receives the denial in `approvals.rs:respond()` 2. Updates the tool entry status to `Denied { reason }` 3. Immediately adds a new `UserMessage` entry with the denial text to the conversation stream 4. Frontend receives this as a normal user message patch and displays it 5. The agent sees it as a user message in the conversation history - ✅ TypeScript compilation passes - ✅ Rust compilation passes - ✅ No breaking changes - ✅ Follows existing architectural patterns Cleanup script changes for task attempt 8122f303-889b-4333-8024-e79b9ea7dc7e Great question! Let me explain how a new `UserFeedback` variant would work - it might actually be cleaner. Let me check what that would look like: A new variant would mean: 1. Add `UserFeedback` to `NormalizedEntryType` enum in `crates/executors/src/logs/mod.rs` 2. Backend uses `NormalizedEntryType::UserFeedback` instead of `UserMessage` 3. Frontend displays it like a user message (same UI component) 4. No filtering issues - it's a distinct type that won't be filtered 5. TypeScript types auto-generated, so frontend gets the type Let me show you what this would look like: Pros: - Type-safe, explicit intent - No filtering workarounds needed - Clear semantic meaning - Auto-generates TypeScript types Cons: - Larger change (need to update Rust enum, regenerate types, update frontend display logic) - Need to run `npm run generate-types` Let me present both options clearly so you can choose: Perfect! Both frontend and backend compile successfully. Let me create a summary of what was implemented: I've successfully implemented Option 2: New `UserFeedback` Variant to display denial messages in the conversation history. 1. Backend: Added `UserFeedback` entry type (`crates/executors/src/logs/mod.rs`) - Added `UserFeedback` variant to `NormalizedEntryType` enum - Marked with `#[ts(export)]` for TypeScript generation 2. Backend: Use `UserFeedback` for denial messages (`crates/services/src/services/approvals.rs`) - When a denial has a reason, create a `NormalizedEntry` with type `UserFeedback` - Add it to the conversation stream after the denied tool - Removed unused metadata structs (cleaner than Option 1) 3. TypeScript Types: Regenerated (`shared/types.ts`) - Ran `npm run generate-types` - New type `{ "type": "user_feedback" }` added to `NormalizedEntryType` 4. Frontend: Display `UserFeedback` as user message (`DisplayConversationEntry.tsx`) - Check for both `user_message` and `user_feedback` types - Render both with the same `<UserMessage>` component - Use same User icon for both types 1. No filtering issues: `UserFeedback` is a distinct type, won't be filtered by the user message filter 2. Type-safe: Explicit enum variant with auto-generated TypeScript types 3. Semantic clarity: Clear distinction between initial prompts and feedback 4. Natural display: Appears as a user message in the conversation flow 5. Extensible: Can be used for other user feedback scenarios in the future When a user denies an approval with feedback like "Please try a different approach": 1. Backend creates a `UserFeedback` entry with that text 2. Frontend receives it and displays it as a user message 3. It appears in the conversation history naturally, right after the denied tool 4. The agent sees it in the context as user input - ✅ Backend (Rust) compiles - ✅ Frontend (TypeScript) compiles - ✅ Types regenerated successfully - ✅ Clean, type-safe implementation Perfect! So the tool result IS processed. But looking at the log entry you provided, the denial message appears in a `tool_result` with `is_error: true`. Let me check what tool this corresponds to: Perfect! Both backend and frontend compile successfully. Let me create a summary of the complete solution: I implemented a normalization-based approach that works with both live sessions and old logs by extracting denial reasons from the tool_result that's already in the raw logs. 1. Added `UserFeedback` Entry Type (`crates/executors/src/logs/mod.rs:56`) - New variant in `NormalizedEntryType` enum - Represents user feedback during execution (like denial reasons) - Auto-exported to TypeScript types 2. Added Denial Reason Extraction (`crates/executors/src/executors/claude.rs:316-339`) - New function `extract_denial_reason()` that parses hook denial messages - Pattern: `"operation blocked by hook:\n- {user's reason}"` - Extracts the text after `"- "` 3. Create UserFeedback During Normalization (`crates/executors/src/executors/claude.rs:598-612` and `717-731`) - When processing tool_result with `is_error: true` - Call `extract_denial_reason()` to check for denial pattern - If found, create a `UserFeedback` entry with the extracted reason - Add it right after the denied tool - Applies to both command tools and other tools (MCP, etc.) 4. Display UserFeedback in Frontend (`frontend/src/components/NormalizedConversation/DisplayConversationEntry.tsx`) - Handle `user_feedback` type same as `user_message` - Display with `<UserMessage>` component - Use User icon 5. Cleaned Up Approvals Service (`crates/services/src/services/approvals.rs`) - Removed the live-session-only code that added UserFeedback - Removed unused `EntryIndexProvider` import - Let normalization handle everything 1. Denial reason IS in raw logs: The hook sends denial as tool_result with `is_error: true` containing the user's feedback 2. Survives restarts: Raw logs are persisted to DB, including the tool_result 3. Works for old logs: When logs are re-normalized after restart, the extraction logic runs and creates the UserFeedback entry 4. Type-safe: New enum variant with proper TypeScript types 5. No filtering issues: `UserFeedback` is a distinct type, won't be filtered out - ✅ Live sessions: Denial feedback appears as user message - ✅ After restart: Old logs show denial feedback when re-normalized - ✅ Type-safe: Proper enum variant, auto-generated TypeScript types - ✅ Both compilations pass When a user denies a tool with feedback like "Please try a different approach", it now appears as a separate user message in the conversation history, immediately after the denied tool. Cleanup script changes for task attempt 8122f303-889b-4333-8024-e79b9ea7dc7e Perfect! Both backend and frontend compile successfully. Let me create a final summary of all the changes: 1. ✅ Duplicate code block removed - Consolidated denial detection into one place after both command/non-command branches 2. ✅ Pattern matching improved - Changed from `"operation blocked by hook:"` to `"blocked by hook:"` to match both "Edit operation blocked by hook" and "operation blocked by hook" 3. ✅ Magic strings replaced with constants - Added `HOOK_DENIAL_PATTERN` and `HOOK_DENIAL_REASON_PREFIX` constants 1. Added `UserFeedback` Entry Type (`crates/executors/src/logs/mod.rs:56`) - New variant in `NormalizedEntryType` enum for user feedback during execution 2. Added Constants for Hook Patterns (`crates/executors/src/executors/claude.rs:42-45`) ```rust const HOOK_DENIAL_PATTERN: &str = "blocked by hook:"; const HOOK_DENIAL_REASON_PREFIX: &str = "- "; ``` 3. Added Denial Extraction Function (`crates/executors/src/executors/claude.rs:321-345`) - Detects hook denial messages in tool_result content - Extracts user's reason from lines starting with `"- "` - Uses constants for maintainability 4. Create UserFeedback During Normalization (`crates/executors/src/executors/claude.rs:703-717`) - After processing any tool_result with `is_error: true` - Extract denial reason and create `UserFeedback` entry - Add it immediately after the denied tool - Single consolidated check for both command and non-command tools 5. Display UserFeedback in Frontend (`frontend/src/components/NormalizedConversation/DisplayConversationEntry.tsx`) - Handle `user_feedback` type same as `user_message` - Display with `<UserMessage>` component - Use User icon 6. Regenerated TypeScript Types (`shared/types.ts:287`) - Added `{ "type": "user_feedback" }` to `NormalizedEntryType` 7. Cleaned Up Approvals Service (`crates/services/src/services/approvals.rs`) - Removed unused live-session code - Let normalization handle everything 1. Works with old logs: Denial reason is in persisted tool_result, extracted during re-normalization 2. Works with live sessions: Denial extracted during initial normalization 3. No magic strings: Uses constants for pattern matching 4. No duplication: Single denial check after tool processing 5. Flexible pattern: Matches "Edit operation blocked by hook" and "operation blocked by hook" 6. Type-safe: Proper enum variant with TypeScript types - ✅ Backend compiles - ✅ Frontend compiles - ✅ No duplicate code - ✅ Pattern improved to match your example Cleanup script changes for task attempt 8122f303-889b-4333-8024-e79b9ea7dc7e Perfect! Everything compiles. Let me create a summary of the final solution: 1. Python Hook - Natural Language Marker (`crates/executors/src/executors/hooks/confirm.py:14`) - Prefix denial reason with `"User feedback: {reason}"` - Natural language format that's both readable to LLM and parseable - Example output: `"User feedback: Could you add something about a goose?"` 2. Rust Constant (`crates/executors/src/executors/claude.rs:44`) ```rust const USER_FEEDBACK_MARKER: &str = "User feedback: "; ``` 3. Robust Extraction Function (`crates/executors/src/executors/claude.rs:320-340`) - Search for `USER_FEEDBACK_MARKER` in tool_result content - Extract everything after the marker - No dependency on Claude Code's error message format 4. Added `UserFeedback` Entry Type (`crates/executors/src/logs/mod.rs:56`) - New variant for user feedback during execution 5. Create UserFeedback During Normalization (`crates/executors/src/executors/claude.rs:703-717`) - When tool_result has `is_error: true`, check for user feedback - Create `UserFeedback` entry with extracted text - Works for both live sessions and old logs (persisted in raw logs) 6. Frontend Display (`frontend/src/components/NormalizedConversation/DisplayConversationEntry.tsx`) - Render `user_feedback` same as `user_message` 1. ✅ We control the format: The `"User feedback: "` prefix is added by OUR Python script 2. ✅ Claude Code independent: Works regardless of how Claude Code formats hook errors 3. ✅ Natural language: Reads naturally - LLM sees "User feedback: {reason}" which is clear 4. ✅ Survives restarts: Tool_result is in persisted raw logs, re-extracted on normalization 5. ✅ Backward compatible: Old logs without marker simply won't match (no errors) 6. ✅ Simple: One constant, one natural prefix User denies with: `"Could you add something about a goose?"` Raw log contains: ```json {"type":"tool_result","content":"Edit operation blocked by hook:\nUser feedback: Could you add something about a goose?","is_error":true} ``` Extraction: Finds `"User feedback: "`, extracts `"Could you add something about a goose?"` Display: Shows as user message in conversation history Result: User's feedback is visible to both user and LLM, survives restarts! Perfect! The solution is complete. Let me create a final summary: Single Source of Truth: The marker `"User feedback: "` is defined ONLY in Rust and injected into Python at runtime. 1. Rust Constant (`crates/executors/src/executors/claude.rs:44`) ```rust const USER_FEEDBACK_MARKER: &str = "User feedback: "; ``` 2. Python Script Placeholder (`crates/executors/src/executors/hooks/confirm.py:15-16`) ```python USER_FEEDBACK_MARKER = "{{USER_FEEDBACK_MARKER}}" formatted_reason = f"{USER_FEEDBACK_MARKER}{reason}" if reason else None ``` 3. Template Replacement (`crates/executors/src/executors/claude.rs:241-244`) ```rust let script_content = CONFIRM_HOOK_SCRIPT.replace( "{{USER_FEEDBACK_MARKER}}", USER_FEEDBACK_MARKER, ); file.write_all(script_content.as_bytes()).await?; ``` 4. Extraction Function (`crates/executors/src/executors/claude.rs:320-340`) - Searches for `USER_FEEDBACK_MARKER` in tool_result content - Extracts feedback text after the marker 5. UserFeedback Entry Creation (`crates/executors/src/executors/claude.rs:703-717`) - During normalization, detects denials and creates UserFeedback entries 6. Frontend Display (`frontend/src/components/NormalizedConversation/DisplayConversationEntry.tsx`) - Renders UserFeedback as user messages 7. TypeScript Types (`shared/types.ts`) - `user_feedback` variant generated At deployment time: 1. Rust defines `USER_FEEDBACK_MARKER = "User feedback: "` 2. Python script has placeholder `{{USER_FEEDBACK_MARKER}}` 3. When writing hook, Rust replaces `{{USER_FEEDBACK_MARKER}}` → `"User feedback: "` 4. Python script executes with actual value When user denies: 1. Python outputs: `"User feedback: Could you add something about a goose?"` 2. This goes into tool_result in raw logs (persisted) 3. During normalization, Rust finds `"User feedback: "` and extracts the text after it 4. Creates UserFeedback entry 5. Frontend displays it as a user message ✅ Single source of truth: Marker defined only in Rust constant ✅ No duplication: Python gets value via template replacement ✅ Format independent: Works regardless of Claude Code's error format ✅ Natural language: LLM sees readable "User feedback: {text}" ✅ Survives restarts: Tool_result persisted in DB, re-extracted on normalization ✅ Maintainable: Change constant in one place, both Rust and Python updated - ✅ Backend compiles - ✅ Frontend compiles - ✅ Single source of truth maintained Cleanup script changes for task attempt 8122f303-889b-4333-8024-e79b9ea7dc7e Perfect! Everything compiles. Let me create a final summary: 1. Backend: Added Tool Name to UserFeedback (`crates/executors/src/logs/mod.rs:55-57`) ```rust UserFeedback { denied_tool: String, } ``` 2. Backend: Capture Display Tool Name (`crates/executors/src/executors/claude.rs:573-589`) - Extract tool name before processing branches - For MCP tools, format as `mcp:server:tool` instead of `mcp__server__tool` - Store in `display_tool_name` variable 3. Backend: Include Tool Name in UserFeedback (`crates/executors/src/executors/claude.rs:734-735`) ```rust entry_type: NormalizedEntryType::UserFeedback { denied_tool: display_tool_name.clone(), }, ``` 4. Backend: Single Source of Truth for Marker (`crates/executors/src/executors/claude.rs:44`) ```rust const USER_FEEDBACK_MARKER: &str = "User feedback: "; ``` 5. Python: Placeholder Template (`crates/executors/src/executors/hooks/confirm.py:15-16`) ```python USER_FEEDBACK_MARKER = "{{USER_FEEDBACK_MARKER}}" formatted_reason = f"{USER_FEEDBACK_MARKER}{reason}" if reason else None ``` 6. Backend: Template Replacement (`crates/executors/src/executors/claude.rs:241-244`) ```rust let script_content = CONFIRM_HOOK_SCRIPT.replace( "{{USER_FEEDBACK_MARKER}}", USER_FEEDBACK_MARKER, ); ``` 7. Frontend: Custom Red Accent Display (`DisplayConversationEntry.tsx:648-666`) - Red background (`bg-red-50 dark:bg-red-950/20`) - Red border (`border-red-400/40`) - Bold header showing: `"{ToolName} denied by user"` - Red text for the feedback content - NO edit/retry buttons (read-only display) 8. TypeScript Types Regenerated (`shared/types.ts`) ```typescript { "type": "user_feedback", denied_tool: string } ``` When user denies "Edit" tool with "Could you add something about a goose?": ``` ┌─────────────────────────────────────────┐ │ Edit denied by user │ ← Bold red text │ Could you add something about a goose? │ ← Red feedback text └─────────────────────────────────────────┘ ← Red border/background ``` ✅ Single source of truth: Marker defined only in Rust, injected into Python ✅ Tool name included: Shows which tool was denied ✅ Distinct styling: Red accent makes it clear this is a denial ✅ No edit/retry: Simple read-only display, no complex user message features ✅ Works with old logs: Tool_result persisted, re-extracted on normalization ✅ Type-safe: Tool name field in enum, auto-generated TypeScript types - ✅ Backend compiles - ✅ Frontend compiles - ✅ Types regenerated - ✅ No duplication Cleanup script changes for task attempt 8122f303-889b-4333-8024-e79b9ea7dc7e Perfect! The new styling should be much more subtle and blend better with the existing UI: - Background: Same as user messages (no bright red) - Border: Dashed like user messages, with subtle red tint (30% opacity) - Header: Small text (`text-xs`), muted red, 80% opacity - Content: Same font-light styling as regular user messages This keeps the denial feedback visible but not overwhelming, similar to how the regular user message integrates into the conversation flow. Perfect! The new styling is much more subtle: - Background: Same `bg-background` as user messages (no bright red) - Border: Standard dashed border (no red tint) - Header: Uses semantic `--destructive` color with 70% opacity for subtlety - Content: Standard user message styling (no red text) This approach: - ✅ Uses semantic CSS variables for proper dark mode support - ✅ Much less visually intense - just a subtle red label - ✅ Blends better with the conversation flow - ✅ The small "denied by user" label provides context without overwhelming The visual hierarchy is now: subtle header hint → main content, which matches the rest of the UI better. * Tool denial feedback (vibe-kanban 35abbc86) The last commit implement log entries for tool denials, it has some problems though: Update json_error in crates/executors/src/executors/hooks/confirm.py so the marker is only prefixed when an actual user denial reason is passed—fallback errors (network failure, invalid JSON, timeouts) must keep their original text to avoid generating fake user_feedback entries. Adjust the hook deployment in write_python_hook (crates/executors/src/executors/claude.rs) to refresh existing confirm.py files when the bundled script changes: either always rewrite, compare hashes/timestamps, or at least overwrite when the placeholder is still present. Without that, previously installed hooks never get the marker update. Refine extract_denial_reason in claude.rs to support the real payloads coming back from Claude: preserve multi-line feedback (don’t stop at the first newline) and handle array/object forms such as [{"type":"text","text":"…"}] so the full user message survives. lets fix these! * Clippy * Perfect! All changes are complete. Here's the summary: 1. Added i18n Hook (`DisplayConversationEntry.tsx:603`) ```typescript const { t } = useTranslation('common'); ``` 2. Used Translation Key (`DisplayConversationEntry.tsx:661`) ```typescript {t('conversation.deniedByUser', { toolName: feedbackEntry.denied_tool })} ``` 3. Added English Translation (`frontend/src/i18n/locales/en/common.json:38`) ```json "deniedByUser": "{{toolName}} denied by user" ``` 4. Added Spanish Translation (`frontend/src/i18n/locales/es/common.json:26`) ```json "deniedByUser": "{{toolName}} denegado por el usuario" ``` 5. Added Japanese Translation (`frontend/src/i18n/locales/ja/common.json:38`) ```json "deniedByUser": "{{toolName}} がユーザーによって拒否されました" ``` 6. Used Semantic Color (`DisplayConversationEntry.tsx:658-659`) ```typescript style={{ color: 'hsl(var(--destructive))' }} ``` The UserFeedback display now: - ✅ Uses semantic `--destructive` color (adapts to light/dark mode automatically) - ✅ Supports i18n for English, Spanish, and Japanese - ✅ Subtle styling that blends with conversation flow - ✅ Maintains tool name context The visual is now much more subtle with proper semantic colors and internationalization support! * Perfect! Everything compiles. Let me create a summary of the final solution: 1. Python: Added Argument Parser (`confirm.py:96-102`) ```python parser.add_argument( "-m", "--feedback-marker", type=str, required=True, help="Marker prefix for user feedback messages.", ) ``` 2. Python: Updated json_error to Accept Marker (`confirm.py:11`) ```python def json_error(reason: Optional[str], feedback_marker: Optional[str] = None) -> None: formatted_reason = reason if reason and feedback_marker: formatted_reason = f"{feedback_marker}{reason}" ``` 3. Python: Pass Marker When Denying (`confirm.py:162`) ```python json_error(reason, args.feedback_marker) ``` 4. Rust: Pass Marker as CLI Arg (`claude.rs:283`) ```rust format!("... --feedback-marker {}", shlex::try_quote(USER_FEEDBACK_MARKER)...) ``` 5. Rust: Removed String Replacement (`claude.rs:236-238`) - No longer need to replace placeholders - Just write the script as-is ✅ Cleaner: No template placeholder magic, just a regular CLI arg ✅ Standard: Follows same pattern as other args (timeout, port, etc.) ✅ Explicit: Marker is passed explicitly each time hook runs ✅ Flexible: Easy to change or extend with more parameters ✅ Single source of truth: Still only defined in Rust constant Rust defines: ```rust const USER_FEEDBACK_MARKER: &str = "User feedback: "; ``` Rust invokes Python with: ```bash confirm.py --timeout-seconds 3605 --poll-interval 5 --backend-port 8080 --feedback-marker "User feedback: " ``` Python receives and uses: ```python args.feedback_marker # "User feedback: " formatted_reason = f"{args.feedback_marker}{reason}" ``` No template replacement needed - clean and straightforward! Excellent! Everything compiles. The solution is now complete and much cleaner: Single Source of Truth: ```rust const USER_FEEDBACK_MARKER: &str = "User feedback: "; ``` How it flows: 1. Rust → Python (via CLI arg): ```bash confirm.py ... --feedback-marker 'User feedback: ' ``` 2. User denies → Python formats: ```python formatted_reason = f"User feedback: Could you add something about a goose?" ``` 3. Goes into raw logs → Rust extracts: ```rust extract_denial_reason() // finds "User feedback: " and extracts what follows ``` 4. Creates UserFeedback entry: ```rust NormalizedEntryType::UserFeedback { denied_tool: "Edit" } content: "Could you add something about a goose?" ``` 5. Frontend displays with red accent: ``` Edit denied by user ← Small red text Could you add something about a goose? ← Normal text ``` ✅ No string replacement - just a CLI argument ✅ No sketchy fallbacks - simple, direct constant usage ✅ Single source of truth - marker only defined in Rust ✅ Type-safe - `denied_tool` field in enum ✅ i18n support - translatable display text ✅ Semantic colors - uses `--destructive` CSS variable ✅ Works with old logs - survives restarts via raw log persistence The implementation is now straightforward with no unnecessary complexity! * Simplify marker parsing	2025-10-06 15:38:18 +01:00
Alex Netsch	adc362955a	Add variant/config cycle keyboard shortcut (vibe-kanban) (#922 ) * Perfect! I've successfully implemented the Shift+Tab keyboard shortcut to cycle between agent configurations. Here's a summary of the changes: Added Shift+Tab keyboard shortcut to cycle through agent configuration variants when editing the follow-up textbox. 1. TaskFollowUpSection.tsx (frontend/src/components/tasks/TaskFollowUpSection.tsx:125-136, 400) - Added `cycleVariant` function that cycles to the next variant in the current profile - Passed `onShiftTab={cycleVariant}` to `FollowUpEditorCard` 2. FollowUpEditorCard.tsx (frontend/src/components/tasks/follow-up/FollowUpEditorCard.tsx:17, 31, 50) - Added `onShiftTab?: () => void` prop to component interface - Passed through to `FileSearchTextarea` 3. file-search-textarea.tsx (frontend/src/components/ui/file-search-textarea.tsx:25, 40, 294) - Added `onShiftTab?: () => void` prop to component interface - Passed through to `AutoExpandingTextarea` 4. auto-expanding-textarea.tsx (frontend/src/components/ui/auto-expanding-textarea.tsx:8, 21, 62-65, 77) - Added `onShiftTab?: () => void` prop to component interface - Implemented Shift+Tab handler in `handleKeyDown` that prevents default behavior and calls the callback - Added to useCallback dependencies - When the user presses Shift+Tab while editing the follow-up textbox, it cycles to the next agent configuration variant - The `VariantSelector` component already has bump animation implemented (TaskFollowUpSection.tsx line 23-30 in VariantSelector.tsx) which will trigger on variant change - The shortcut only works when the textbox is editable and active The fix ensures that when `selectedVariant` is `null`, the first press of Shift+Tab will explicitly set the variant to the first one in the list (index 0), making the cycling work correctly from the start. Perfect! I've updated the `cycleVariant` function to treat "DEFAULT" as a regular variant in the cycle. Here's what the fix does: The fix ensures that: 1. When `selectedVariant` is `null`, it's treated as `"DEFAULT"` for lookup purposes 2. All variants including "DEFAULT" are included in the cycling 3. The cycle works: DEFAULT → variant1 → variant2 → ... → DEFAULT 4. When cycling lands on "DEFAULT", it converts back to `null` (since that's what the backend/API expects) Why this works: - First press from `null` (DEFAULT): Cycles to the first non-DEFAULT variant ✓ - Provides keyboard access to cycle back to DEFAULT ✓ - Treats "DEFAULT" as what it truly is: a configured variant, not a special case ✓ - No hacky filters or special-casing needed ✓ The implementation is clean and treats "DEFAULT" as a first-class variant in the cycling logic, while maintaining the existing API contract where `null` represents DEFAULT. Perfect! Now the Shift+Tab interception only happens when `onShiftTab` is actually provided. This ensures: 1. Follow-up text box: Shift+Tab cycles through variants (has `onShiftTab` handler) 2. All other textareas: Shift+Tab works normally for browser focus navigation (no `onShiftTab` handler) The fix preserves the default browser behavior for all existing uses of `AutoExpandingTextarea` while enabling the variant cycling feature only where it's needed. Refactor keyboard shortcuts (vibe-kanban 67d268cf) We did this in the last 4 commits: Add a shortcut to cycle between agent configurations (previously called profile variants) when typing a follow up. Should be active when the user is editing the follow-up text box. User shift tab to trigger the shortcut. However this doesnt use the current pattern we want to use for shortcuts. Figure out the correct way and migrate. Refactor keyboard shortcuts (vibe-kanban 4d35f44f) Your colleague already handled one: Refactoring Summary The Shift+Tab shortcut was refactored from a prop-drilling approach (passing onShiftTab through multiple components) to the centralized keyboard system using the semantic hook pattern. The new implementation: Registered the shortcut in registry.ts as CYCLE_VARIANT action bound to shift+tab in the FOLLOW_UP scope Created a semantic hook useKeyCycleVariant for type-safe usage Used scope management with enableScope(Scope.FOLLOW_UP) to control when the shortcut is active (only when textarea is focused AND editable) Removed prop drilling - deleted onShiftTab props from FollowUpEditorCard, FileSearchTextarea, and AutoExpandingTextarea Pattern for other shortcuts: Add the action/keys to registry.ts, create a semantic hook in hooks.ts, use the hook in your component with appropriate scope, and manage scope activation with enableScope/disableScope based on when the feature should be available. The when clause is only for additional runtime conditions beyond what scope controls. Can we mirgate the rest of the shortcuts in frontend/src/components/tasks/TaskFollowUpSection.tsx Fix shortcut regressions (vibe-kanban c07e229f) To‑Do For Shortcuts Restore submit shortcut in task dialog (frontend/src/components/dialogs/tasks/TaskFormDialog.tsx:491): reintroduce Cmd+Enter / Cmd+Shift+Enter when focus is in the description FileSearchTextarea. Prefer the new keyboard system—add a semantic hook (likely useKeySubmitTask) scoped appropriately, or, if we don’t have one yet, bind via useKeySubmit while the dialog is active. The binding must only be enabled when the form can submit and the textarea is focused. Re-enable Cmd+Enter save in inline review comments (frontend/src/components/diff/CommentWidgetLine.tsx:69): same story—bring back the shortcut using our keyboard hooks so reviewers can submit without leaving the textarea. Fix FileSearchTextarea event propagation (frontend/src/components/ui/file-search-textarea.tsx:12, :235): the component still lists onKeyDown but never calls it. Destructure onKeyDown from props and invoke it at the end of handleKeyDown so parent components can layer their own key handling again. Fix shortcut regressions (vibe-kanban c07e229f) To‑Do For Shortcuts Restore submit shortcut in task dialog (frontend/src/components/dialogs/tasks/TaskFormDialog.tsx:491): reintroduce Cmd+Enter / Cmd+Shift+Enter when focus is in the description FileSearchTextarea. Prefer the new keyboard system—add a semantic hook (likely useKeySubmitTask) scoped appropriately, or, if we don’t have one yet, bind via useKeySubmit while the dialog is active. The binding must only be enabled when the form can submit and the textarea is focused. Re-enable Cmd+Enter save in inline review comments (frontend/src/components/diff/CommentWidgetLine.tsx:69): same story—bring back the shortcut using our keyboard hooks so reviewers can submit without leaving the textarea. Fix FileSearchTextarea event propagation (frontend/src/components/ui/file-search-textarea.tsx:12, :235): the component still lists onKeyDown but never calls it. Destructure onKeyDown from props and invoke it at the end of handleKeyDown so parent components can layer their own key handling again. Fmt * Perfect! I've added the `isComposing` check to `useKeyboardShortcut.ts` at line 68. This fix ensures that: ## What Was Fixed The `isComposing` check that was lost during the rebase has been restored, but in the new architecture's proper location: Before the rebase (old architecture): - Each component (`AutoExpandingTextarea`, `Input`) had its own keyboard handlers - The `isComposing` check was added to these handlers: `if (e.key === 'Enter' && !e.nativeEvent.isComposing)` After the rebase (new architecture): - All keyboard shortcuts centralized through `useKeyboardShortcut.ts` → `react-hotkeys-hook` - The check needed to move to the central handler The fix: - Added `if (event.isComposing) return;` at line 68 in `useKeyboardShortcut.ts` - This protects all keyboard shortcuts (not just Enter) from firing during IME composition - Covers all actions: `SUBMIT_FOLLOW_UP`, `SUBMIT_TASK`, `CYCLE_VARIANT`, etc. ## Impact Now when users input text using IME (Japanese, Chinese, Korean, etc.): - Pressing Enter to confirm text conversion won't accidentally trigger shortcuts - Pressing Shift+Tab during composition won't cycle variants - All keyboard shortcuts properly respect IME composition state This is actually better than the old fix because it applies universally to all shortcuts, not just the ones that were manually checked before.	2025-10-06 14:11:33 +01:00
Louis Knight-Webb	7bf4b12ddb	Can't retry a user message when dev server is running (vibe-kanban) (#937 ) * Done! The fix is complete and all checks pass. Here's what changed: Summary: - Replaced local `anyRunning` check with `isAttemptRunning` from `useAttemptExecution` - Removed unused `useMemo` import - Updated tooltip text for clarity The retry button now correctly allows retrying when only the dev server is running, while still blocking during actual task executions (codingagent, setupscript, cleanupscript). * Cleanup script changes for task attempt 80246ab7-5ae8-4b09-8020-839cca417fb6 * Update frontend/src/hooks/useProcessRetry.ts Co-authored-by: Solomon <abcpro11051@disroot.org> --------- Co-authored-by: Solomon <abcpro11051@disroot.org>	2025-10-06 12:49:20 +01:00
Louis Knight-Webb	73f49cae9f	Merged tasks are endlessly re-rendering (vibe-kanban) (#938 ) * ## ✅ Fix Complete Problem: Merged tasks caused endless WebSocket reconnections because `useJsonPatchWsStream` incorrectly treated `{finished: true}` messages as signals to reconnect. Solution: Modified [useJsonPatchWsStream.ts](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/0f2d-merged-tasks-are/frontend/src/hooks/useJsonPatchWsStream.ts) to treat "finished" as terminal: 1. Added `finishedRef` to track when stream completes 2. On `{finished: true}`: set flag, close cleanly (code 1000), no reconnect 3. On socket close: skip reconnection if finished flag is set or clean close 4. Reset flag on cleanup and new connections Result: - Merged tasks connect once, receive final state, and stop cleanly - Active tasks still reconnect on network errors - Aligned behavior with existing `streamJsonPatchEntries` utility - All type checks pass ✅ * Cleanup script changes for task attempt 0f2d0086-1de2-4517-a023-1ee8cf133181	2025-10-06 12:49:08 +01:00
Louis Knight-Webb	fef06cf00e	Done! I've successfully removed arrow key navigation while preserving hjkl shortcuts. Here's what changed: (#946 ) ## Changes Made: 1. [frontend/src/keyboard/registry.ts](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/155e-remove-keyboard/frontend/src/keyboard/registry.ts) - Removed arrow keys from navigation bindings, kept only hjkl - Fixed Enter key conflict by changing fullscreen toggle to ⌘/Ctrl+Enter 2. [docs/configuration-customisation/keyboard-shortcuts.mdx](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/155e-remove-keyboard/docs/configuration-customisation/keyboard-shortcuts.mdx) - Updated Board Navigation section to show hjkl only - Added fullscreen toggle documentation All type checks pass ✓	2025-10-06 10:51:26 +01:00
Louis Knight-Webb	f26f70060c	Markdown renderer bug (vibe-kanban) (#940 ) * Done! Fixed the markdown renderer bug with a simple one-line change plus typo fix. All type checks pass. Changes made: 1. Added `disableParsingRawHTML: true` to prevent invalid ref attributes from raw HTML 2. Fixed typo: `text-baseleading-tight` → `text-base leading-tight` * Cleanup script changes for task attempt 67d094ca-1a5f-4713-b595-26fce3aea3ef	2025-10-04 22:25:35 +01:00
hayato iida	567b4a0411	Fix: Prevent form submission during IME composition (#934 ) This fix addresses issue #919 where pressing Enter during IME (Input Method Editor) composition incorrectly triggers form submission in task title and description fields. Changes: - Add isComposing check to Input component's Enter key handler - Add isComposing check to AutoExpandingTextarea component's Enter key handler This ensures that Enter key during IME composition (e.g., Japanese, Chinese, Korean input) only confirms the text conversion without accidentally submitting the form. Fixes #919	2025-10-04 14:30:46 +01:00
Louis Knight-Webb	c45e40717e	Close GitHub popup after login (vibe-kanban) (#930 ) * ## Fix Implemented Successfully ✅ I've implemented the GitHub popup auto-close fix with two key changes to [`GitHubLoginDialog.tsx`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/d872-close-github-pop/frontend/src/components/dialogs/auth/GitHubLoginDialog.tsx): 1. Auto-close effect: Added a `useEffect` that automatically closes the dialog when the user becomes authenticated 2. Reduced flicker: Reordered the SUCCESS polling case to avoid briefly showing the "Sign in again" prompt The popup will now automatically close within ~1 second after successful GitHub authentication, eliminating the confusing "sign in again" prompt. Type checks pass successfully. * ## Fix Implemented Successfully ✅ I've implemented the complete fix for the GitHub popup staying open in the settings page: Changes Made: 1. Updated [`GitHubLoginDialog.tsx`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/d872-close-github-pop/frontend/src/components/dialogs/auth/GitHubLoginDialog.tsx#L34-L40): Added `modal.resolve(true)` before `modal.hide()` in the auto-close effect to properly settle the Promise 2. Simplified [`GeneralSettings.tsx`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/d872-close-github-pop/frontend/src/pages/settings/GeneralSettings.tsx#L489-L491): Removed the unnecessary `.finally()` chain since the dialog now manages its own lifecycle The popup will now automatically close after successful GitHub authentication from both the onboarding flow and the settings page. Type checks pass successfully. * Cleanup script changes for task attempt d8729f37-551a-4490-a0bd-396032d528ce * ## Self-Contained Fix Implemented Successfully ✅ I've implemented Option 2 - the most predictable approach that makes the dialog self-contained: Changes Made: 1. Removed the auto-close effect that depended on external state changes 2. Added direct modal close in the SUCCESS case of the device flow polling: - After `await reloadSystem()`, immediately call `modal.resolve(true)` and `modal.hide()` - This happens right when we know authentication succeeded Benefits of this approach: - Self-contained: The dialog manages its own lifecycle without depending on external state - Predictable: The flow is linear and obvious: start → poll → success → close - Readable: No complex state dependencies or effects to understand - Reliable: Eliminates the timing issues with stale `githubTokenInvalid` flags The popup will now automatically close immediately after successful GitHub authentication in both the onboarding and settings flows. Type checks pass successfully.	2025-10-03 19:23:13 +01:00
Louis Knight-Webb	c8e660c7da	Add discord shield to navbar (vibe-kanban) (#927 ) * ✅ Discord shield added to navbar with: - Desktop badge: Discord shield visible on sm+ screens, positioned before the dropdown menu - Mobile fallback: Discord link added to dropdown menu for small screens - Consistent styling: Uses `h-5` height and proper spacing (`ml-2 mr-1`) - Accessibility: Includes proper `aria-label` and `alt` text The implementation follows the existing code patterns and maintains readability as requested. * ✅ Fixed both issues: - Vertical centering: Changed from `block` to `flex items-center` to properly align with other navbar buttons - Theme adaptation: Added `dark:brightness-90 dark:contrast-125` to subtly adjust the shield colors in dark mode for better visibility The Discord shield now properly aligns with other navbar elements and adapts to both light and dark themes. * ✅ Updated Discord shield with theme colors and positioning: - Theme colors: Custom badge using `bg-background`, `text-foreground` for left side and `bg-success`, `text-success-foreground` for right side - Position: Moved to right of logo (left side of navbar) instead of right side - Design: Clean two-part badge with "discord" label and "online" status that adapts to theme automatically The Discord badge now uses your app's theme colors and is positioned next to the logo for better visual hierarchy. * ✅ Discord online count implemented with: - Live data: Fetches real member count from Discord Widget API - Auto-refresh: Updates every 60 seconds for live feel - Graceful fallback: Shows "online" if API unavailable - Theme integration: Maintains your custom success/background colors - Accessibility: Includes `aria-live="polite"` for screen readers - Formatted display: Shows count as "1,234 online" with proper locale formatting The Discord badge now displays the actual number of online members from your server while maintaining the theme colors and positioning next to the logo. * Cleanup script changes for task attempt 230fa5cc-96f7-4fdb-a549-c2ea46b9e88e * ✅ Fixed positioning - Added `flex items-center` to the container so the logo and Discord badge sit side by side horizontally instead of stacking vertically. * ✅ Added Discord logo from simple-icons: - Added simple-icons dependency via pnpm - Imported Discord icon from `simple-icons` package - Replaced "discord" text with actual Discord SVG logo - Maintained theme colors - icon uses `currentColor` so it adapts to theme automatically - Proper sizing - `h-4 w-4` matches other navbar icons The Discord badge now displays the official Discord logo instead of text, while maintaining the live member count and theme integration. * Cleanup script changes for task attempt 230fa5cc-96f7-4fdb-a549-c2ea46b9e88e * manual style improvement	2025-10-03 18:52:44 +01:00
Britannio Jarrett	81af7ac36c	Add remaining IDE icons (vibe-kanban) (#925 ) * Perfect! All the icons have been successfully added. The implementation is now complete: ✅ Zed: Added theme-aware icons (zed-dark.svg, zed-light.svg) ✅ IntelliJ: Added single icon (intellij.svg) since IntelliJ typically uses one consistent icon ✅ Windsurf: Added theme-aware icons (windsurf-dark.svg, windsurf-light.svg) The [`IdeIcon` component](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/2b83-remaining-ide-ic/frontend/src/components/ide/IdeIcon.tsx#L19-L64) now properly handles all three IDE types with appropriate theme support, and the [`OpenInIdeButton`](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/2b83-remaining-ide-ic/frontend/src/components/ide/OpenInIdeButton.tsx) component already had the correct labels configured. * Perfect! I've made the following changes: ✅ Fixed Zed icons: Now correctly uses light icon on dark theme and dark icon on light theme ✅ Fixed Windsurf icons: Now correctly uses light icon on dark theme and dark icon on light theme ✅ Added Xcode support: Ready to display Xcode icon when you add `xcode.svg` to the `/ide` directory The icon mapping now works correctly - dark-colored icons show on light backgrounds, and light-colored icons show on dark backgrounds. * Perfect! The Xcode icon has been successfully added. Now all IDE icons are in place: ✅ Xcode: Added `xcode.svg` icon ✅ Zed: Theme-aware icons with correct mapping ✅ IntelliJ: Single consistent icon ✅ Windsurf: Theme-aware icons with correct mapping All IDE types from the EditorType enum now have proper icon support in the [`IdeIcon` component](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/2b83-remaining-ide-ic/frontend/src/components/ide/IdeIcon.tsx). * format IdeIcon.tsx	2025-10-03 16:42:02 +01:00
Solomon	a43fa76079	Copilot CLI (#915 )	2025-10-03 13:12:53 +01:00
Alex Netsch	8dc297c521	Fix mem leak (#916 ) * Fix mem leak * Fix cross-platform, fix no error logging	2025-10-03 09:46:44 +01:00
Solomon	b40b7f21b9	Speed-up running process check (#894 )	2025-10-02 15:40:09 +01:00
Alex Netsch	2f2e85b6e0	Disable follow-up textbox during approvals (vibe-kanban) (#914 ) * Perfect! All changes have been implemented successfully. Let me summarize what was done: ## Summary I've successfully implemented the feature to disable the follow-up textbox during approvals. Here's what was changed: ### Changes Made: 1. Created `usePendingApproval` hook (`frontend/src/hooks/usePendingApproval.ts`): - This hook checks the conversation entries from `EntriesContext` to detect if any tool use entry has a `pending_approval` status - Returns a boolean indicating whether there's a pending approval 2. Updated `TaskFollowUpSection` component (`frontend/src/components/tasks/TaskFollowUpSection.tsx`): - Imported and used the new `usePendingApproval` hook - Updated `canTypeFollowUp` to include the `hasPendingApproval` check, preventing users from typing when an approval is pending - Updated `isEditable` to include `!hasPendingApproval`, which disables the textbox UI when there's a pending approval ### How It Works: - When an agent requests approval for a tool use, the conversation entry will have a `status: 'pending_approval'` - The `usePendingApproval` hook detects this by checking all entries in the `EntriesContext` - When a pending approval is detected, the follow-up textbox becomes disabled, preventing users from typing and queueing follow-ups - Once the approval is resolved (approved/denied), the entry status changes and the textbox becomes enabled again The implementation follows the existing patterns in the codebase and integrates smoothly with the existing approval UI and context system. TypeScript type checking passes successfully. * Cleanup script changes for task attempt bd98d75b-12d0-45da-b486-f516b274abff * Perfect! The refactoring is complete. Here's what I did: ## Changes Made 1. Deleted `frontend/src/hooks/usePendingApproval.ts` - the custom hook was unnecessary 2. Updated `TaskFollowUpSection.tsx`: - Removed import of `usePendingApproval` - Added import of `useEntries` from `@/contexts/EntriesContext` - Replaced the hook call with inline logic using `useEntries()` and `useMemo()` ## Result The implementation is now: - Simpler - one less file to maintain - More consistent - follows the same pattern as `TodoPanel.tsx` which also uses `useEntries()` directly - Just as efficient - still memoized, same performance - Easier to understand - all the logic is in one place The functionality remains exactly the same - the follow-up textbox (and all related buttons) will be disabled when there's a pending approval in the conversation entries. TypeScript type checking passes successfully.	2025-10-02 15:20:08 +01:00
Alex Netsch	a2153be98c	Keep git panel when branchstatus fails (vibe-kanban) (#913 ) * Done! I've updated the code to keep the Git panel visible when `branchStatus` fails: Changes made: 1. GitOperations.tsx:253-256: Changed the early return condition to only hide the panel when PR is merged, not when `branchStatus` is null 2. GitOperations.tsx:438-505: Wrapped the merge/PR/rebase buttons in a conditional `{branchStatus && ...}` so they only display when branch status is available 3. TaskDetailsToolbar.tsx:227-238: Removed the `branchStatus` condition from the parent, so `GitOperations` is always rendered when `selectedAttempt` exists Result: - The Git panel (showing branch names and the arrow) will now always display when there's a selected attempt - The merge, PR, and rebase buttons will only show when branch status loads successfully - The panel still hides completely if the PR has been merged * Updated! Now the target branch will fallback to `selectedAttempt.target_branch` if `branchStatus` doesn't load, ensuring the target branch label always displays correctly.	2025-10-02 11:17:18 +01:00
Gabriel Gordon-Hall	d10c37f061	don't show virtuoso loader when pending approval (#909 )	2025-10-01 18:16:15 +01:00
Louis Knight-Webb	b631f6fbc6	Improve plan scroll (#908 ) * Done! I've removed the scrolling classes from the plan container. Plans will now use the parent chat history scroll instead of having their own nested scroll behavior. The fix removes `max-h-[65vh] overflow-y-auto overscroll-contain` while preserving the padding and background styling. * Cleanup script changes for task attempt 6c65f630-c1bb-4069-b3d8-7d937fc35bf7	2025-10-01 18:10:45 +01:00
Greg Burch	0e9d10732a	Allow image pasting into task field (#883 ) * Changes - Made `ImageUploadSection` ref-aware with an `addFiles` imperative handle and auto-expansion when images appear, enabling non-UI triggers to reuse its validation/upload flow (frontend/src/components/ui/ImageUploadSection.tsx:36-348). - Captured clipboard image blobs in the shared textarea component and exposed them via a new `onPasteFiles` hook for upstream consumers (frontend/src/components/ui/file-search-textarea.tsx:111-137). - Task creation dialog now routes pasted images straight into the uploader through the new ref, keeping the description markdown in sync (frontend/src/components/dialogs/tasks/TaskFormDialog.tsx:102-357). - Follow-up editor keeps the image panel mounted but hidden, reveals it on paste, and forwards the new prop through its wrapper so task attempts accept clipboard images (frontend/src/components/tasks/TaskFollowUpSection.tsx:89-325; frontend/src/components/tasks/follow-up/FollowUpEditorCard.tsx:13-47). Tests - `npm run check` (frontend) - `pnpm run check` (timed out after backend cargo check kicked off; see log) Next Steps 1. Re-run `pnpm run check` or `npm run backend:check` when you can let Cargo finish to confirm backend continues to build. 2. Manually paste a few image formats/sizes into the task form and follow-up editor to confirm UX and markdown output look right. * Update frontend/src/components/ui/ImageUploadSection.tsx Co-authored-by: Gabriel Gordon-Hall <gabriel@bloop.ai> * fmt --------- Co-authored-by: Greg Burch <gburch@styleseat.com> Co-authored-by: Gabriel Gordon-Hall <gabriel@bloop.ai> Co-authored-by: Gabriel Gordon-Hall <ggordonhall@gmail.com>	2025-10-01 17:17:51 +01:00
Louis Knight-Webb	2781e3651b	Add preview tab + point and click editor (vibe-kanban) (#870 ) * Perfect! The preview tab implementation is complete and all type checks pass. Let me provide a summary of what was implemented: 1. Updated `TabType` - Added 'preview' to the union type 2. Created `useDevserverPreview` hook - Intelligent devserver URL detection with: - Real-time log parsing using the regex `(?:localhost\|127\.0\.0\.1\|0\.0\.0\.0):(\d+)[^\d]` - Three states: idle/searching/ready - URL normalization (0.0.0.0 → localhost) - Process monitoring for setup scripts and dev servers 3. Built `PreviewTab` component* - Full-featured iframe preview with: - Proper sandbox settings for security - Toolbar with refresh, copy URL, and open external buttons - Smart error handling for mixed content/CORS issues - Clear empty states and loading indicators 4. Enhanced `TabNavigation` - Conditionally shows preview tab with: - Monitor icon and spinner when searching - Only appears when devserver is detected or likely 5. Integrated in `TaskDetailsPanel` - Wires everything together in fullscreen mode - Smart Detection: Parses logs in real-time to find devserver URLs - Robust Error Handling: Graceful fallbacks for iframe loading issues - Security: Proper iframe sandboxing with necessary permissions - Performance: Efficient log processing with deduplication - UX: Clear states (searching/ready/error) with helpful messaging The implementation follows the Oracle's architectural recommendations with proper separation of concerns and real-time detection capabilities. * Cleanup script changes for task attempt 4f59c374-1cc5-4b3c-a79a-5f63756a366b * Perfect! Now the preview tab will use the first dev server URL it detects rather than being overwritten by subsequent matches. This means: - If both backend (e.g., `:3001`) and frontend (e.g., `:5173`) servers start - The preview tab will show whichever URL appears first in the logs - Subsequent URLs will be ignored to avoid switching the preview unexpectedly This provides a more stable preview experience when multiple dev servers are running. * Cleanup script changes for task attempt 4f59c374-1cc5-4b3c-a79a-5f63756a366b * add parent lib * fmt * Listen for communication from the preview tab (vibe-kanban ace46045) In frontend/src/components/tasks/TaskDetails/PreviewTab.tsx We should expect that the iframe will communicate via frontend/src/utils/previewBridge.ts When a message is received, we should add some details about the clicked element to the follow up textarea * Component to view clicked element (vibe-kanban e3b90cc1) frontend/src/components/tasks/TaskDetails/PreviewTab.tsx frontend/src/components/tasks/TaskFollowUpSection.tsx When a user clicks on an element, we should display a box in the follow up section similar to how we show reviews or conflicts. The section should display a summary of each of the elements, the name of the component and the file location. When the user sends a follow up, a markdown equivalent of the summary should be appended to the top of the follow up message. * Component to view clicked element (vibe-kanban e3b90cc1) frontend/src/components/tasks/TaskDetails/PreviewTab.tsx frontend/src/components/tasks/TaskFollowUpSection.tsx When a user clicks on an element, we should display a box in the follow up section similar to how we show reviews or conflicts. The section should display a summary of each of the elements, the name of the component and the file location. When the user sends a follow up, a markdown equivalent of the summary should be appended to the top of the follow up message. * Tweaks to component click (vibe-kanban 756e1212) Preview tab frontend/src/components/tasks/TaskDetails/PreviewTab.tsx - Preview should remember which URL you were on - Auto select the follow up box after point and click, so you can type feedback Clicked elements: frontend/src/components/tasks/ClickedElementsBanner.tsx, frontend/src/contexts/ClickedElementsProvider.tsx - The list of components should not overflow horizontally, instead we should truncate, omiting components from the left first - If the user clicks on a component, it should omit the downstream components from the list, they should be displayed disabled and the prompt should start from the selected component * strip ansi when parsing dev server URL * cleanup * cleanup * improve help copy * start dev server from preview page * dev server wip * restructure * instructions * fix * restructur * fmt * i18n * i18n fix * config fix * wip cleanup * minor cleanup * Preview tab feedback (vibe-kanban d531fff8) In the PreviewToolbar, each icon button should have a tooltip * fix + fmt * move dev script textarea * improve when help is shown * i18n * improve URL matching * fix close logs * auto install companion * cleanup notices * Copy tweak	2025-10-01 17:15:12 +01:00
Gabriel Gordon-Hall	0ace01b55f	- remove AbortController in PendingApprovalEntry (#902 ) - fix find execution process check - force stop process with non-killed status	2025-10-01 16:51:23 +01:00
Louis Knight-Webb	0bf4733bff	## ✅ Fix Complete! (#892 ) I've successfully implemented the fix for the todos not updating when navigating between task attempts. Here's what I changed: File: [`TaskDetailsPanel.tsx`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/cf76-todos-do-not-upd/frontend/src/components/tasks/TaskDetailsPanel.tsx#L100) Change: Added `key={selectedAttempt?.id}` to the `EntriesProvider` component ```tsx // Before <EntriesProvider> // After <EntriesProvider key={selectedAttempt?.id}> ``` How it works: - When `selectedAttempt?.id` changes, React unmounts and remounts the `EntriesProvider` with fresh state - This immediately clears the entries array and resets the todos to an empty state - The TodoPanel will hide until new entries arrive for the selected attempt - No todos from previous attempts can persist The fix is minimal, readable, and leverages React's built-in key behavior for state management - exactly what the Oracle recommended as the best approach.	2025-09-30 16:53:40 +01:00
Solomon	f9878e9183	Consolidate Retry and Follow-up (#800 )	2025-09-30 13:09:50 +01:00
Louis Knight-Webb	71bfe9ac0b	Fix dropdown colours (vibe-kanban) (#891 ) * Done! The dropdown colors are now fixed for dark mode readability: - Selected items now use `bg-accent text-accent-foreground` instead of hardcoded light-theme colors - File paths in selected items use `text-accent-foreground/70` for better contrast - Added accessibility attributes (`aria-selected` and `role="option"`) The changes maintain your existing design token pattern and will automatically adapt to both light and dark themes. * Cleanup script changes for task attempt 9dd6bd96-f216-408c-ab42-94eefb1437e1 * Perfect! Now the selected dropdown item uses: 1. Background: `bg-primary/10` (subtle primary tint) 2. Text: `text-primary` (primary color text) 3. Left border: `border-l-2 border-primary` (visual indicator) 4. File path: `text-primary/70` (muted primary for secondary info) This provides much better visual distinction while maintaining theme compatibility and using your existing design token pattern. * Cleanup script changes for task attempt 9dd6bd96-f216-408c-ab42-94eefb1437e1 * Now the selected item uses `bg-muted text-foreground` which provides proper contrast in both light and dark modes, with a primary-colored left border for visual distinction. The file path uses consistent `text-muted-foreground` in all states. * Cleanup script changes for task attempt 9dd6bd96-f216-408c-ab42-94eefb1437e1 * Perfect! Now the selected dropdown item simply uses `bg-muted text-foreground` which provides clear contrast and visibility without the border.	2025-09-30 13:08:06 +01:00
Gabriel Gordon-Hall	6727e2dbb9	feat: keyboard shortcuts for approvals (#869 ) * wip * cmd click shortcut to deny approval * cleaner type * show percentage in progress bar * improve structure of PendingApprovalComponent * enter to approve request * disable kanban scope * fix approval scope selection	2025-09-30 11:40:34 +01:00
Louis Knight-Webb	23243dda7a	Prevent useConversationHistory conflicts (vibe-kanban) (#872 ) * ## Summary Successfully implemented the `mergeIntoDisplayed` helper to prevent useConversationHistory conflicts! Here's what was accomplished: Changes made to [`frontend/src/hooks/useConversationHistory.ts`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/5e29-prevent-useconve/frontend/src/hooks/useConversationHistory.ts): 1. Added mergeIntoDisplayed helper that performs in-place mutations instead of reassigning the entire object 2. Refactored 4 direct assignment locations: - Stream updates in `loadRunningAndEmit` - Initial entries loading - Batch loading (with function signature improvement) - Process removal logic 3. Maintained the deliberate reset on attempt change (line 479) Key improvements: - Prevents race conditions between concurrent async operations - Eliminates data loss from process log overwrites - Maintains data integrity during streaming and batch loading - Passes type checking successfully The implementation follows the Oracle's recommendations for safe concurrent updates by always reading the latest state and mutating in-place rather than replacing the entire object reference. * Cleanup script changes for task attempt 5e29a440-f572-406d-9f07-be5f11fd3775	2025-09-30 11:18:28 +01:00
Alex Netsch	091e903cf6	Alex/refactor bb rebase (#824 ) * Refactor task_attempt branch handling and enforce NOT NULL constraint on branch column * Change backend rebase to no change base branch, add change target branch api * Change frontend rebase on branch to change target branch Change status to show ahead/behind, always show rebase * Use target branch for everything except rebase * Remove base_branch * Remove base branch frontend * add rebase dialog with target and upstream options * Fix unused upstream arg * Add i18n * Remove stray ts-rs file * dont show +0, -0 * Move upstream to foldable advanced rebase * Move buttons around * Move git state/actions into a component * Add task/target labels * Fix action buttons layout * Fmt * i18n * remove branch origin removal * Remove empty divs * Remove [1fr_auto_1fr] class in favour if divs * use theme colours, make gear icon bigger * Fix plural i18n * Remove legacy ui reducer	2025-09-29 19:50:29 +01:00

... 3 4 5 6 7 ...

676 Commits