Release v0.3.5 - #91
Merged
Merged
Conversation
Bump the marketplace-stream hosts -- Claude Code, Codex, Kimi Code, and Copilot -- to 0.3.5, along with the shared MCP client's default clientInfo version and the ref the Claude marketplace installs from. pi versions independently and is untouched. This release lets a clear match connect itself. On Copilot, get_context now connects a uniquely clear routing match when the session is grounded in nothing and the mode is auto, instead of printing a menu of one. Every safeguard still holds: an existing connection, a near tie, a weak match, ask or manual mode, an unavailable selection, or a context declined in this session all fall back to the menu. The confidence rule underneath it ships to every host. Connecting unasked now needs two agreeing terms the user actually typed, paired independently on both sides, so no single compound word can clear the floor on its own; an exact name or a whole-request alias stands in for it. Contexts are ranked and boosted before the shortlist is cut, the bridge's own automatic connections stay out of familiarity, and a refusal bars connecting unasked for one named half-life rather than for as long as the discount lingers. Co-Authored-By: Claude Opus 5 <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
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.
Bump the marketplace-stream hosts — Claude Code, Codex, Kimi Code, and Copilot — to 0.3.5, along with the shared MCP client's default
clientInfoversion and therefthe Claude marketplace installs from. pi versions independently and is untouched.This release lets a clear match connect itself (#90).
On Copilot,
get_contextconnects a uniquely clear routing match when the session is grounded in nothing and the mode isauto, instead of printing a menu of one. Every safeguard still holds: an existing connection, a near tie, a weak match,askormanualmode, an unavailable selection, or a context declined in this session all fall back to the menu. The bridge wiring is Copilot-only; the routing core below it ships to every host.Connecting unasked now needs real agreement.
assessonly ever judged the leader against the field, so a single-context store always read as "clear" — one common term or a filename hit was enough. A match now needs two agreeing terms the user actually typed, counted as words rather than index tokens, with terms landing only infilesexcluded and derived tokens collapsed souser_idcannot pay foruserandidas well. Pairing is an exact maximum matching between the parts of the request and what they agreed on, so rewording a sentence cannot change where it routes. An exact name, or an alias the user wrote out, still stands in for the floor.Known limitation, tested rather than papered over: a run of no-space script is one part of the request however long it is, so Chinese and kanji-dense Japanese need an exact name match or a whole-request alias to connect unasked. Korean is written with spaces and is unaffected.
Also in the routing core: rank and boost before slicing, so decline and familiarity multipliers can promote a context into the visible set; automatic connections stay out of familiarity, so routing cannot teach itself a preference the user never expressed; automatic decisions cap separately at 20 so the machine's routes cannot evict the user's own; and a refusal bars connecting unasked for one named half-life rather than for as long as
declineFactorstays under 1.Checks
npm run check— pass (includes thesync:evidenceandsync:contextdrift checks)npm test— 546 pass, 0 failnpm run validate:plugin— pass, strict, both manifestsAfter merge:
git tag v0.3.5 && git push origin v0.3.5, then publish the GitHub release. Marketplaces install from the tag.🤖 Generated with Claude Code