Repository navigation
test(search): image search levels on the owner's images, totals only - #43
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.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
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.
Why: the owner wants images findable (image search plan, 2026-10-13, all three levels). This measures caption, surrounding conversation (e5) and two picture models on 150 of the owner's Telegram photos with 30 queries. Totals only; queries and per-query rows stay in the private report.
CLIP: 57 ms per image median, 44 ms per query, 226 MB. SigLIP2: 154 ms, 113 ms, 378 MB. Drive not measured: the CLI returns no image bytes, and the account's 126 Drive images carry no date or place.
Profiles and the account id are inputs (
TG_PROFILE,TG_ACCOUNT_ID,DRIVE_PROFILE), never defaults.🤖 Generated with Claude Code