Repository navigation
fix(search): cli-core 0.665.0 and a skill that starts a question with meaning search - #893
Merged
Merged
Conversation
…ch and --discover In Experiment B round 3 an agent with the default skill ran 71 word searches, one meaning search and no --discover, filtered the source chat out with grep -v, and missed from:me. The skill now gives the order for a question in the owner's own words and the traps seen in that run. Refs #884 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour
force-pushed
the
fix/search-skill
branch
from
November 15, 2026 08:15
5219a6d to
b1844e8
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.
Task
Experiment B (an agent answers the owner's questions from one real Telegram account): the agent with tg used it as keyword search, and the strong search kinds failed on the 2-second limit. #884, #887.
Why
search conversationsfailed on 12 of 29 sentence questions withquery.time-limit;--timeoutdid not reach it.search messagesfirst; the agent ran 71 word searches, one meaning search and no--discover, filtered the source chat out withgrep -v, and missedfrom:me.What
@wirecat/cli-core0.665.0 (was 0.662.0),@wirecat/cli-base0.102.1: a slow word half no longer failssearch conversations, stop words left out,--timeoutreaches it (cli-core#2959, #2972);--discoverjoins a hyphenated name.search conversations, then--discover, then key words; the question as written; no filtering by hand;from:mefor "I advised";--timeoutafterquery.time-limit.docs/commands.md,contracts/wirecat.json, the test matrix (three shared options from cli-core 0.663–0.665 listed with the cli-core test that drives them). Fragmentschanges/chore-cli-core-0.665.0.md,changes/fix-search-skill.md.Testing
docs:check,parity:check,test:matrix:check.search conversationsfound the source in the top 10 in 8 of 29 one-query lookups (was 4), with 0 time-limit failures (was 12); some tg search kind found it in 14 of 29 (was 11). Numbers in search conversations stops at its 2 s time limit on a full-history store #887.Closes #884
🤖 Generated with Claude Code