Repository navigation
fix(mcp): honor advertised catalog subscription capabilities - #41
Merged
Merged
Conversation
![kit-code-agent[bot]](https://avatars.githubusercontent.com/in/4797102?s=60&v=4){kind=small}
danielkov
added a commit
that referenced
this pull request
Oct 19, 2026
## Summary Prepare releases for all unpublished package changes and the libraries that must move together with the new loop API. Update 17 package versions, their internal dependency requirements, and the workspace lockfile without changing external dependencies. ## Impact | Packages | Release | | --- | --- | | `agentkit-loop`, `agentkit-adapter-completions`, `agentkit-acp`, `agentkit-compaction`, `agentkit-reporting` | `0.11.0` | | All nine `agentkit-provider-*` crates | `0.11.0` | | `agentkit` facade | `0.12.0` | | `agentkit-mcp` | `0.11.3` | | `how-cli` | `0.10.7` | ## Technical details ### Changes included since published releases Four packages have unpublished source changes relative to their latest non-yanked crates.io archives: loop, OpenAI, and Anthropic include context-rejection recovery and classification from #42; MCP includes advertised catalog subscription capability handling from #41. Anthropic's cached-token usage fix from #38 is already included in published `0.10.11`. The other 12 publishable packages have no unpublished package changes and retain their versions. The existing publish script covers all 29 publishable workspace members in dependency order; no publish-script change is needed. ### Coordinated minor versions The new `ContextRecoveryDeadlineExceeded` variant extends the public, exhaustive `LoopError` enum, requiring a minor release before 1.0. Providers, the completions adapter, compaction, ACP, and reporting expose loop traits or types and therefore move to `0.11.0` together. The facade moves to `0.12.0`; binary-only `how-cli` takes a patch bump. All affected version-bearing internal dependency edges are aligned, including optional facade dependencies and integration-test requirements, so registry builds do not mix incompatible loop type identities. Compaction and reporting receive explicit versions rather than raising the inherited workspace version for unchanged crates. The lockfile changes only the 17 workspace package versions.
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.
Summary
Honor explicit
listChanged: trueadvertisements when requesting MCP catalog notifications. Do not opensubscriptions/listenduring connection, discovery, or authentication reconnect when neither catalog notifications nor resource subscriptions are requested.Motivation
Servers can advertise tools, resources, and prompts without implementing notification subscriptions. Treating capability presence as notification support sends unsupported requests to these servers.
Technical details
Explicit resource subscriptions still open a modern stream lazily when there is no catalog stream, and reconnect replays the committed resource filter. A modern resource unsubscribe with no controller is a no-op rather than falling back to a legacy RPC. HTTP protocol regressions cover missing, empty, false, mixed, and true catalog advertisements, plus resource-only streams.