Chore/pin engine agent framework migration - #36
Merged
Conversation
The MandoCode submodule moves from cd4d003 (v0.14.3 line) to 3b5f667, which carries the Semantic Kernel to Agent Framework migration, the engine's own 0.15.0 bump, and the fix excluding OllamaSharp's source generator from the build. Desktop tracks the engine generation, so its version follows.
Desktop feature work lands on top of this before the 0.15.0 release, so the section stays open rather than taking a date. The entry leads with the engine swap because no Desktop behavior changed — the machinery under every chat turn did.
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.
What changed in the engine
The engine's orchestration layer — the part that sends a message to a model, runs
tools, and streams the reply back — was rebuilt on Microsoft's Agent Framework,
replacing Semantic Kernel. Same models, same tools, same approval prompts. It is a
foundation swap underneath behavior that does not change, so there is no new
functionality for a user to see.
The engine work was built and verified on its own branch before merging: the new path
was stood up alongside the old one, checked against real models, and the old one
removed only once nothing depended on it.
Also picked up
A build fix (engine PR #78) for a Visual Studio failure the migration introduced.
Without it the app could not be compiled locally. Confirmed resolved.
Impact and risk
glance. Worth exercising: sending a message and watching it stream, a tool call that
requires approval, switching models mid-conversation, and a context snapshot carried
across a model switch.
engine.