feat(isolation): introduce Git worktree isolation and MCP server#158
Draft
feat(isolation): introduce Git worktree isolation and MCP server#158
Conversation
0a4bc84 to
16f3055
Compare
16f3055 to
13515bd
Compare
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.
Description
This PR introduces an MCP (Model Context Protocol) server to manage isolated Git worktrees and integrates this isolation mechanism into the core Conductor commands.
Changes
MCP Server for Worktree Management:
src/to expose Git worktree operations.create_worktree,delete_worktree, andlist_worktreestools.src/isolation.test.ts).gemini-extension.jsonto register theconductorMCP server.Integration into Conductor Commands:
implement: Checks for existing worktrees or creates a new one using thecreate_worktreetool. Instructs the agent to perform all execution and file reads within this isolated context.review: Detects if an isolated worktree exists for the track being reviewed. Ensures pre-checks (linting, building, testing) and diff analysis run within the context of the worktree. Provides options to discard the isolated work or merge it into the base branch.revert: Integrates awareness of active worktrees, offering pre-merge options like aborting the track (destroying the worktree), rolling back the last commit within the worktree, or rolling back to a checkpoint.