Fix Lightning RLM child tool routing - #3
Draft
pst2154 wants to merge 2 commits into
Draft
Conversation
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
ipythontool.ipythonuntil a parent reply is delivered.Why
Nemotron 3.5 Lightning can emit unadvertised calls such as
agent_messageinstead of executingagent_message.send()inside IPython. Those calls fail before the child can return its findings. The extension provides a model-specific request guard without hardcoding the workaround into Prime Agent core.Validation
npx tsx ../../node_modules/vitest/dist/cli.js --run test/system-prompt.test.ts— 26 tests passed.npm run check— passed.ipythonon its first response, delivered exactly one parent message, and stopped normally.Scope
This fixes Lightning's RLM tool-routing failure. It does not claim to improve the model's underlying SWE reasoning accuracy.