V0.11.0rc #475
V0.11.0rc #475
Conversation
…endpoints - apps/server/src/providers/claude-provider.ts Add ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN to the environment variable allowlist, enabling use of LLM gateways (LiteLLM, Helicone) and Anthropic- compatible providers (GLM 4.7, Minimax M2.1, etc.). Closes #338
…hrough - apps/server/tests/unit/providers/claude-provider.test.ts Verify custom endpoint environment variables are passed to the SDK.
This commit fixes several edge cases when resuming features stuck in pipeline steps: - Detect if feature is stuck in a pipeline step during resume - Handle case where context file is missing (restart from beginning) - Handle case where pipeline step no longer exists in config - Add dedicated resumePipelineFeature() method for pipeline-specific resume logic - Add detectPipelineStatus() to extract and validate pipeline step information - Add resumeFromPipelineStep() to resume from a specific pipeline step index - Update board view to check context availability for features with pipeline status Edge cases handled: 1. No context file → restart entire pipeline from beginning 2. Step no longer exists in config → complete feature without pipeline 3. Valid step exists → resume from the crashed step 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Reduce redundant file reads by loading the feature object once and passing it down the call chain instead of reloading it multiple times. Changes: - Pass feature object to resumePipelineFeature() instead of featureId - Pass feature object to resumeFromPipelineStep() instead of featureId - Remove redundant loadFeature() calls from these methods - Add FeatureStatusWithPipeline import for type safety This improves performance by eliminating unnecessary file I/O operations and makes the data flow clearer. Co-authored-by: gemini-code-assist bot 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Remove confusing and unnecessary delete calls from resumeFeature() and resumePipelineFeature() methods. These were leftovers from a previous implementation where temporary entries were added to runningFeatures. The resumeFeature() method already ensures the feature is not running at the start (via has() check that throws if already running), so these delete calls serve no purpose and only add confusion about state management. Removed delete calls from: - resumeFeature() non-pipeline flow (line 748) - resumePipelineFeature() no-context case (line 798) - resumePipelineFeature() step-not-found case (line 822) Co-authored-by: gemini-code-assist bot 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
…cation Define a dedicated PipelineStatusInfo interface and use it consistently in both resumePipelineFeature() parameter and detectPipelineStatus() return type. This eliminates duplicate inline type definitions and improves maintainability by ensuring both locations always stay in sync. Any future changes to the pipeline status structure only need to be made in one place. Changes: - Add PipelineStatusInfo interface definition - Replace inline type in resumePipelineFeature() with PipelineStatusInfo - Replace inline return type in detectPipelineStatus() with PipelineStatusInfo Co-authored-by: gemini-code-assist bot 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Remove unnecessary call to pipelineService.getStep() which was causing a redundant file read of pipeline.json. The config is already loaded at line 2807, so we can find the step directly from the in-memory config. Changes: - Sort config.steps first - Find stepIndex using findIndex() - Get step directly from sortedSteps[stepIndex] instead of calling getStep() - Simplify null check to only check !step instead of stepIndex === -1 || !step This optimization reduces file I/O operations and improves performance when resuming pipeline features. Co-authored-by: gemini-code-assist bot 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Enable the Resume button to appear for features with pipeline status (e.g., 'pipeline_step_xyz') in addition to 'in_progress' status. Previously, features that crashed during pipeline execution would show a 'testing' status badge but no Resume button, making it impossible to resume them from the UI. Changes: - Update card-actions.tsx condition to include pipeline_ status check - Resume button now shows for both in_progress and pipeline_step_* statuses - Maintains all existing behavior for other feature states This fixes the UX issue where users could see a feature was stuck in a pipeline step but had no way to resume it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Resolved conflict in card-actions.tsx by:
- Keeping pipeline_status check from our branch (supports pipeline_step_* statuses)
- Adopting simplified Resume button logic from main (removed hasContext check and onVerify fallback)
The Resume button now appears for features with:
- status === 'in_progress'
- status.startsWith('pipeline_')
This combines our pipeline support fix with main's simplified button rendering logic.
Re-add the onVerify fallback for in_progress/pipeline features without context, but fix the misleading UX issue where the button said 'Resume' but executed verification (tests/build). Changes: - Restore onVerify fallback as 3rd option after skipTests Verify and Resume - Change button label from 'Resume' to 'Verify' (honest!) - Change icon from PlayCircle to CheckCircle2 (matches action) - Keep same green styling for consistency This makes sense because if a feature is in_progress but has no context, it likely completed execution but the context was deleted. User should be able to verify it (run tests/build) rather than having no action available. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Auto-format all files to fix format-check CI failure. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Add detailed JSDoc documentation to meet 80% docstring coverage requirement: - PipelineStatusInfo interface: Document all properties with types and descriptions - resumePipelineFeature(): Document edge case handling and parameters - resumeFromPipelineStep(): Document complete pipeline resume workflow - detectPipelineStatus(): Document pipeline status detection scenarios Each docstring includes: - Clear method purpose and behavior - All parameters with types and descriptions - Return value documentation - Error conditions and exceptions - @Private tags for internal methods This improves code maintainability and helps developers understand the complex pipeline resume logic. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Add UID and GID build arguments to Dockerfiles to allow matching the container user to the host user. This fixes file permission issues when mounting host directories as volumes. Default remains 1001 for backward compatibility. To match host user: UID=$(id -u) GID=$(id -g) docker-compose build Co-Authored-By: Claude Opus 4.5 <[email protected]>
- Sidebar now uses overlay pattern on mobile (fixed position when open) - Added backdrop overlay that dismisses sidebar on tap - Made collapse toggle button visible on all screen sizes - Made project options menu visible on all screen sizes Previously the sidebar was forced to collapsed width (w-16) on mobile even when sidebarOpen was true, and the toggle/options buttons were hidden with `hidden lg:flex`.
Integrate Claude Haiku to automatically generate commit messages when committing worktree changes. Shows a sparkle animation while generating and auto-populates the commit message field. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
…provider auth initialization
- Implemented a new endpoint to generate commit messages based on git diffs. - Updated worktree routes to include the AI commit message generation functionality. - Enhanced the UI to support automatic generation of commit messages when the commit dialog opens, based on user settings. - Added settings for enabling/disabling AI-generated commit messages and configuring the model used for generation.
- Added a new section in the UI for customizing commit message prompts. - Integrated a system prompt for AI-generated commit messages, allowing users to define their own instructions. - Updated the backend to merge custom prompts with default settings for commit message generation. - Enhanced the commit message generation logic to utilize the effective system prompt based on user settings.
…alSettings interface - Eliminated unused properties related to notification commands and ntfy.sh integration from the GlobalSettings interface. - Updated default global settings to reflect the removal of these properties.
|
Important Review skippedToo many files! 22 files out of 172 files are above the max files limit of 150. You can disable this status message by setting the Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary of ChangesHello @Shironex, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the project's development workflow, AI integration, and user interface. It formalizes a Release Candidate branching strategy, streamlines AI model interactions through a new unified query service, and adds a powerful AI-driven Git commit message generation feature. The UI receives updates for project customization with icons and a new list view for features, alongside improved dev server log streaming. Docker configurations are also refined to prevent common file permission issues. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a significant set of features and refactorings for version 0.11.0rc. Key changes include a new RC-based branching strategy, a major UI overhaul with a new project switcher and a list view for the board, and substantial backend refactoring to abstract AI provider interactions into a unified simple-query-service. The Dockerfiles have also been improved for better user permission handling and to include new tools like the OpenCode CLI. Additionally, the auto-mode service is now more robust with pipeline resume capabilities, and the dev server has enhanced logging with real-time streaming. Overall, this is a very impressive update that improves maintainability, adds powerful new features, and enhances the user experience. I have a couple of suggestions to improve security and maintainability further.
| RUN curl -fsSL https://opencode.ai/install | bash && \ | ||
| echo "=== Checking OpenCode CLI installation ===" && \ | ||
| ls -la /home/automaker/.local/bin/ && \ | ||
| (which opencode && opencode --version) || echo "opencode installed (may need auth setup)" |
There was a problem hiding this comment.
Piping the output of curl directly to bash can be a security risk, as it executes a remote script without verification. A safer approach is to download the script first, optionally verify its checksum if one is provided, and then execute it. This prevents the execution of a potentially malicious script if the download source is compromised or a man-in-the-middle attack occurs.
| // Route to appropriate provider based on model type | ||
| if (isCursorModel(model)) { | ||
| // Use Cursor provider for Cursor models | ||
| logger.info(`Using Cursor provider for model: ${model}`); | ||
|
|
||
| const provider = ProviderFactory.getProviderForModel(model); | ||
| const bareModel = stripProviderPrefix(model); | ||
|
|
||
| const cursorPrompt = `${systemPrompt}\n\n${userPrompt}`; | ||
|
|
||
| let responseText = ''; | ||
| const cursorStream = provider.executeQuery({ | ||
| prompt: cursorPrompt, | ||
| model: bareModel, | ||
| cwd: worktreePath, | ||
| maxTurns: 1, | ||
| allowedTools: [], | ||
| readOnly: true, | ||
| }); | ||
|
|
||
| // Wrap with timeout to prevent indefinite hangs | ||
| for await (const msg of withTimeout(cursorStream, AI_TIMEOUT_MS)) { | ||
| if (msg.type === 'assistant' && msg.message?.content) { | ||
| for (const block of msg.message.content) { | ||
| if (block.type === 'text' && block.text) { | ||
| responseText += block.text; | ||
| } | ||
| } | ||
| } | ||
| } | ||
|
|
||
| message = responseText.trim(); | ||
| } else { | ||
| // Use Claude SDK for Claude models | ||
| const stream = query({ | ||
| prompt: userPrompt, | ||
| options: { | ||
| model, | ||
| systemPrompt, | ||
| maxTurns: 1, | ||
| allowedTools: [], | ||
| permissionMode: 'default', | ||
| }, | ||
| }); | ||
|
|
||
| // Wrap with timeout to prevent indefinite hangs | ||
| message = await extractTextFromStream(withTimeout(stream, AI_TIMEOUT_MS)); | ||
| } |
There was a problem hiding this comment.
This logic for handling different providers (isCursorModel vs. Claude) is a great candidate for refactoring to use the new simpleQuery service, which was introduced in this PR for this exact purpose. Many other routes have been updated to use it, and doing so here would improve consistency, reduce code duplication by removing the local extractTextFromStream and withTimeout helpers, and make the code easier to maintain.
Note that simpleQuery doesn't currently have a timeout mechanism like the withTimeout helper used here. It might be worth considering adding a timeout to simpleQuery (perhaps via an AbortController) to prevent long-running requests across the application.
- Fix handleResolveConflicts to use origin/${worktree.branch} instead of
hardcoded origin/main for pull and resolve conflicts
- Add defaultBaseBranch prop to CreatePRDialog to use selected branch
- Fix branchCardCounts to use primary worktree branch as default
- Enable PR status and Address PR Comments for main branch tab
- Add automatic PR detection from GitHub for branches without stored metadata
This allows users working on release branches (like v0.11.0rc) to properly
pull from their branch's remote and see PR status for any branch.
Co-Authored-By: Claude Opus 4.5 <[email protected]>
fix: use dynamic branch references instead of hardcoded origin/main
fix: Resolve windows npx spawn errors
- Updated create-pr.ts to improve commit error handling and logging. - Enhanced project-switcher.tsx with new folder opening functionality and state management for project setup. - Expanded icon-picker.tsx to include a comprehensive list of icons organized by category. - Replaced dialog components with popover components for auto mode and plan settings, improving UI responsiveness. - Refactored board-view components to streamline feature management and enhance user experience. - Removed outdated dialog components and replaced them with popover alternatives for better accessibility. These changes aim to improve the overall usability and functionality of the project management interface.
- Add missing system libraries required by Playwright/Chromium in server and dev images\n- Document optional Playwright browser cache volume in docker-compose.override.yml.example
…ereqs chore(docker): add Playwright Chromium prerequisites
fix: follow up prompts
CLI-based providers (OpenCode, etc.) only accept a single prompt via stdin/args and don't support separate system/user message channels like Claude SDK. When systemPrompt is passed to these providers, it was silently dropped, causing: - BacklogPlan JSON parsing failures with OpenCode/GPT-5.2 (missing "output ONLY JSON" formatting instruction) - Loss of critical formatting/schema instructions for structured outputs This fix adds embedSystemPromptIntoPrompt() method to CliProvider base class that: - Prepends systemPrompt to the user prompt before CLI execution - Handles both string and array prompts (vision support) - Handles both string systemPrompt and SystemPromptPreset objects - Uses standard \n\n---\n\n separator (consistent with codebase) - Sets systemPrompt to undefined to prevent double-injection Benefits OpencodeProvider immediately (uses base executeQuery). CursorProvider still uses manual workarounds (overrides executeQuery). Fixes the immediate BacklogPlan + OpenCode bug while maintaining backward compatibility with existing Cursor workarounds. Co-Authored-By: Claude Opus 4.5 <[email protected]>
…ompt fix: embed systemPrompt into prompt for CLI-based providers
fix: ensure npm cache directory has correct permissions
… refactoring Implement per-project theme override capability in the Discord-like layout: - Add theme submenu to project context menu with live preview - Reuse existing theme constants and useThemePreview hook from sidebar - Extract reusable ThemeButton and ThemeColumn components (DRY principle) - Replace magic z-index values with named constants Co-Authored-By: Claude Opus 4.5 <[email protected]>
feat: support ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN for custom endpoints
…13091-hnir feat(ui): Add project theme selection to context menu
…88678-28bn fix: adress pr comments task not respecting worktrees
…16676-kza4 feat: add feature request github template
- Use node-pty on all platforms instead of expect on macOS for more reliable PTY handling
- Use process.cwd() as working directory (project dir is likely already trusted)
- Add detection for new trust prompt text variants ("Ready to code here", "permission to work")
- Add specific error handling for trust prompt pending state
- Show helpful UI message when trust prompt needs manual approval
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Address PR review comment - use process.cwd() for Windows too instead of USERPROFILE/homedir fallback for consistency. Co-Authored-By: Claude Opus 4.5 <[email protected]>
fix: Claude usage parsing for CLI v2.x and trust prompt handling
- Updated the list-branches endpoint to accept an optional parameter for including remote branches. - Implemented logic to fetch and deduplicate remote branches alongside local branches. - Modified the CreatePRDialog component to utilize the updated API for branch selection, allowing users to select from both local and remote branches.
…nch exists The branch listing logic now correctly shows remote branches (e.g., "origin/main") even if a local branch with the same base name exists, since users need remote branches as PR base targets. Also extracted duplicate state reset logic in create-pr-dialog into a reusable function.
…27235-36uf feat: enhance pr dialog base branch selection
No description provided.