Skip to content

[Bug] Commands like codegate version fail to be processed #1362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
blkt opened this issue Apr 22, 2025 · 0 comments
Open

[Bug] Commands like codegate version fail to be processed #1362

blkt opened this issue Apr 22, 2025 · 0 comments
Labels

Comments

@blkt
Copy link
Contributor

blkt commented Apr 22, 2025

Describe the issue

Commands like codegate version are forwarded to the LLM rather than bypassing it.

The root cause is that the code implementing the short-circuit logic was removed during refactoring and never added back again. Note that the linked code would not work as-is and must be rewritten to behave in the same way.

Steps to Reproduce

Using any assistant, open a chat window and enter codegate version.

Operating System

Other

IDE and Version

Any

Extension and Version

Any

Provider

Other

Model

Any

Codegate version

9c51b4d0134a

Logs

No response

Additional Context

No response

blkt added a commit that referenced this issue Apr 29, 2025
While refactoring I removed three lines of coding managing
short-circuited requests. We short-circuit requests to implement
`codegate version`, `codegate workspace`, and similar commands.

Given we now have a provider-native representation of the messages, it
is necessary to produce the right message for the given request and
provider, so some code must be added in provider-specific modules to
handle that.

Fixes #1362
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants