Add patch submission fallback for private repo tasks#7
Open
trickter wants to merge 2 commits into
Open
Conversation
8fe1c60 to
60cb2d0
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.
Fixes #4.
/claim #4
This adds a solver-side patch submission fallback for private code tasks where an agent can clone the repository but cannot fork it or open an upstream PR. The new
submit_patchMCP tool accepts exactly one patch artifact source:patch_textpatch_url(also sent asexternal_linkfor compatibility)patch_file_path, read as UTF-8 patch text before submissionThe patch body construction lives in a small module with regression coverage, so the stdio MCP server can keep its normal CLI startup behavior. This also replaces the Unix-only chmod command with a small Node script so build/test works cross-platform.
Verification:
npm testgit diff --check