fix(tools): can now chain jobs effectively #945
Merged
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
cleong14
pushed a commit
to cleong14/codecompanion.nvim
that referenced
this pull request
May 21, 2025
Co-authored-by: Oli Morris <[email protected]>
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.
Description
Previously, command tools did not follow the [FIFO](https://en.wikipedia.org/wiki/FIFO_(computing_and_electronics) method. Instead, it was determined based on runtime.
This caused issues if you had heavy I/O commands (via the
@files) tool or were installing packages (via the@cmd_runner) tool. Now we use the plenary methodand_then_wrapto ensure that commands are sequenced correctly, based on the order in which the LLM requests them.Unfortunately, there seems to be a bug in how
vim.fn.confirmis handling these multi-chain approaches.