Option to add extra args to providers#60
Conversation
|
master has changed a lot and i want to think about this still. I love the idea of passing additional params, but part of me thinks this should be on the opts passed into the function as opposed to on the state object. i could go either way, but for now, let me think on it for a while. also everything has been severely refactored. i am ~75% way through a great refactor and i will continue to refactor until my own morale improves :) The big thing for me was making a more consistent and sensible interface to manage lifecycles of data. now things are mostly good |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is kicking off a free cloud agent to fix this issue. This run is complimentary, but you can enable autofix for all future PRs in the Cursor dashboard.
Avoids breaking named options like GeminiCLI's --prompt flag.
|
coming back to this almost a month later i still feel the same way, but i also get why this could be nice. ill merge this in, though i dont know if this is a great / best solution |
|
the failing test is my fault |

option to add extra args to prompt.
In my case i don't want a session per code change in clause so i add "--no-session-persistence"
vim.iteris only available For Neovim 0.10+. don't know what version comp you looking forNote
Medium Risk
Moderate risk because it changes how provider subprocess commands are constructed and allows arbitrary flags to be appended, which could break some provider CLIs depending on argument ordering.
Overview
Adds a new
setup()option,provider_extra_args, which is stored on_99state and validated as a list.Updates
BaseProvider:make_requestto append these extra args to the generated provider command before spawning the subprocess, and adds tests covering state storage/defaulting for this option.Written by Cursor Bugbot for commit f2b4281. This will update automatically on new commits. Configure here.