Repository navigation
Relevance filter (decision model per file) + playground - #2
Merged
Merged
Conversation
filterRelevant asks a cheap model, per file, whether that file matters to the task. Only yes files are included when buildEnvironment is given those decisions. The patchling.app playground exposes the pass with a toggle, a decision-model picker, and bundled sample projects. Co-authored-by: ntc-ai <ntc-ai@users.noreply.github.com>
Use gemini-2.0-flash, the same size and binary policies, and camelCase decision fields. A truncated yes still forwards the original file, and a path can persist the cache as versioned JSON in Node. Co-authored-by: ntc-ai <ntc-ai@users.noreply.github.com>
Raise the filter completion cap, send reasoning_effort low, and treat an empty answer as an error that is not cached. Retry timeouts and HTTP 5xx, count files that failed open, and skip lockfiles and generated paths. Default model is xiaomi/mimo-v2.6-flash. Co-authored-by: ntc-ai <ntc-ai@users.noreply.github.com>
Node 18's test runner does not expose crypto, so SHA-256 via the bare global threw and every filter test failed open. Use globalThis.crypto when it is present, and node:crypto's webcrypto export otherwise. Co-authored-by: ntc-ai <ntc-ai@users.noreply.github.com>
Deploying patchling with
|
| Latest commit: |
2c121ba
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b9f86e5e.patchling.pages.dev |
| Branch Preview URL: | https://cursor-relevance-filter-915b.patchling.pages.dev |
Prompt version 3. The cache key hashes the path, the body that was sent, and the reasoning effort, and a malformed answer fails open without being stored. Truncation stays on a code point, and a short UTF-8 tail is not binary. Flask recall 1.0 and 0.8x token figures are unverified. Co-authored-by: ntc-ai <ntc-ai@users.noreply.github.com>
Hash length-prefixed fields with a colon, including mode, note, and the effort that was actually sent. Count Unicode code points, decode valid UTF-8 bytes, and fail open on a bad response envelope. The playground keeps going when no file is relevant, ignores a stale run, and shows classifier tokens. Co-authored-by: ntc-ai <ntc-ai@users.noreply.github.com>
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
2 participants
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.
From Patchling: opt-in per-file yes/no relevance filter via NanoGPT (default xiaomi/mimo-v2.6-flash), fail-open, retries, lockfile skip; playground on site. 131 tests.