Add developer worktree tools for parallel development workflows#445
Merged
Conversation
Adds fvdb-open, fvdb-issue, and fvdb-close scripts that enable: - Managing Git worktrees across fvdb-core and fvdb-reality-capture - Creating worktrees for GitHub issues with AI agent context - Running multiple AI agents on different issues in parallel Includes install.sh for easy setup and comprehensive README documentation. Signed-off-by: Mark Harris <mharris@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: Mark Harris <mharris@nvidia.com> Co-authored-by: Cursor <cursoragent@cursor.com>
d5febb6 to
74f64fc
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a small suite of local developer scripts to manage Git worktrees across fvdb-core and fvdb-reality-capture, aimed at enabling parallel (multi-branch / multi-agent) workflows.
Changes:
- Introduces
devtools/worktree/withfvdb-open,fvdb-issue,fvdb-close, aninstall.sh, and documentation. - Updates
.gitignoreto ignore worktree-specific Cursor agent rule files. - Adjusts repo VS Code settings by commenting out C++/CUDA formatter-on-save blocks.
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 13 comments.
Show a summary per file
| File | Description |
|---|---|
devtools/worktree/install.sh |
Installer/uninstaller for the worktree helper scripts plus config bootstrap. |
devtools/worktree/fvdb-open |
Interactive/direct worktree selector and Cursor multi-root launcher. |
devtools/worktree/fvdb-issue |
Creates issue-based worktrees using gh/jq, generates agent context, launches Cursor/Claude. |
devtools/worktree/fvdb-close |
Interactive/direct worktree removal with optional branch cleanup. |
devtools/worktree/README.md |
User docs for installation, usage, and workflow examples. |
.vscode/settings.json |
Comments out C++/CUDA format-on-save settings. |
.gitignore |
Ignores .cursor/rules/ directory. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Revert accidental .vscode/settings.json change
- Centralize branch-to-worktree-path normalization in fvdb-open
- Parse branch names from [brackets] instead of second column in worktree list
- Check for editor command availability with FVDB_EDITOR_CMD override
- Add early dependency checks (gh, jq, fvdb-open) in fvdb-issue
- Derive default branch via symbolic-ref instead of hardcoding origin/main
- Replace ${var,,} with tr for Bash 3.2 compatibility
- Use grep -F for safe path matching in fvdb-close
- Try worktree remove without --force first, offer force on failure
- Add macOS lsof fallback for in-use detection
- Detect active shell via $SHELL in install.sh
- Document Bash 4+, Linux /proc, claude CLI in README requirements
Signed-off-by: Mark Harris <mharris@nvidia.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
blackencino
approved these changes
Feb 11, 2026
blackencino
left a comment
Contributor
There was a problem hiding this comment.
Because this workflow is not replacing something, and represents a methodology that you've come up with and are using already, we should try it out before requesting changes. Since you've already addressed the copilot suggestions, I think this is great and we should give it a go.
LGTM!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
devtools/worktree/directory with scripts for managing Git worktrees across fvdb-core and fvdb-reality-capturefvdb-open: Interactive launcher for opening worktrees in Cursorfvdb-issue: Creates worktrees for GitHub issues with AI agent contextfvdb-close: Safely removes worktrees with branch cleanupinstall.shfor easy setup and comprehensive README documentationThese tools enable parallel development workflows where multiple AI agents (or developers) can work on different issues simultaneously in separate worktrees.
Test plan
install.sh- creates config file and installs scripts to~/binfvdb-open- interactive worktree selection and Cursor launchfvdb-issue- issue fetching, worktree creation, context file generationfvdb-close- worktree listing and removal with branch deletion promptMade with Cursor