Repository navigation
plan: optional Eggsearch/MCP tools, embeddings, and retrieval interoperability - #9
Merged
Merged
Conversation
added 29 commits
November 3, 2026 16:41
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.
Purpose
Planning-only follow-up to the Eggpool versus PrivateGPT/Zylon gap review. Keeps Eggpool an on-prem Rust inference gateway by default; tools/hosted execution are explicit opt-in; vectors/ingestion remain outside the router.
Documents
tool-integration,embedding-routing,retrieval-interoperability.plans/registry.mdamended with all workstreams, one ready milestone, five blocked milestones and exact blockers.Handoff order
Invariants
No mandatory Eggsearch/embedding service; no arbitrary external MCP URLs; no default changes to Chat/Responses/Messages/compact or native/client-owned tool handling; no vector store/new SQLite writer, no prompt/tool-body retention; no bypass of user budgets, policy, generation leases or coordinator finalization.
Verification
Planning-file structural and registry checks performed; comparison against
mainconfirms 12 documentation-only files, no runtime or test changes. Cargo suites / live MCP qualification are not run for this planning-only PR. All future implementation plans require serial default and no-default Rust suites and targeted negative/live tests before closure.Maintainer decisions
Review and accept/supersede ADR-0007 and ADR-0008 before promoting blocked API/security milestones; preserve their proposed status until explicitly accepted.