Fix repository paths for server-side CLI providers - #2242
Open
Selene29 wants to merge 1 commit into
Open
Conversation
Server provider resolution loaded per-repo configuration but rebuilt constructor arguments without repo_path. Codex CLI and OpenCode therefore defaulted to the workspace server's current directory, which may not be a Git repository. Reuse the shared provider argument mapping and cover both repository-aware providers.
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
1 participant
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
Problem
Server jobs correctly resolved the repository being indexed, but
get_chat_provider_instance()dropped that path while constructing the provider.Codex CLI then used the server process directory. In workspace mode this was the workspace root rather than a Git repository, so decision extraction failed with
Not inside a trusted directory. OpenCode had the same missing path even though both providers are registered as repository-aware.Testing