chore: skip pre-context injection on first iteration #325
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.
Refactors pre-context handling to skip injection during the first workflow iteration. This prevents unnecessary pre-context information from being added when the agent is just starting its work, improving the initial prompt clarity.
The pre-context injection logic has been extracted into a dedicated function that checks the iteration number before injecting pre-context file paths into workflow step prompts.
Changes
handlePreContextInjection()function to centralize pre-context file loading, validation, and injection logiciteration.jsonto determine if this is the first iterationiteration === 1to avoid polluting initial promptsNotes
This change maintains backward compatibility - pre-context files are still validated and tracked on the first iteration, but the file path information is only injected into workflow prompts starting from the second iteration onwards.