Allow vlmrun gw commands without an API key - #220
Merged
Conversation
Gateway CLI subcommands (gw/gateway) no longer require VLMRUN_API_KEY or a configured key. Other subcommands still enforce credentials as before. - Add require_api_key=False path on VLMRun for gateway-only initialization - Skip CLI credential check for gw/gateway subcommands - Omit Authorization header and use empty OpenAI api_key when unset Co-authored-by: sudeep <sudeep@vlm.run>
Co-authored-by: sudeep <sudeep@vlm.run>
Co-authored-by: sudeep <sudeep@vlm.run>
Contributor
There was a problem hiding this comment.
🔍 Devin Review: 1 flag
Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
Co-authored-by: sudeep <sudeep@vlm.run>
Co-authored-by: sudeep <sudeep@vlm.run>
nwaughachukwuma
approved these changes
Sep 4, 2026
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
Gateway CLI subcommands (
vlmrun gw/vlmrun gateway) no longer requireVLMRUN_API_KEYor a configured API key. Other subcommands (chat,files,generate, etc.) continue to enforce credentials as before.This enables usage like:
without ever setting an API key.
Bumps version to 0.9.0.
Changes
gw/gatewaysubcommandsrequire_api_key: bool = TruetoVLMRun; gateway-only initialization sets it toFalseapi_keyand omits theAuthorizationheader on health checksvlmrun.version.__version__from0.8.2to0.9.0Test plan
pytest tests/test_client.py::test_client_without_api_key_when_not_requiredpytest tests/test_gateway.py::TestGatewayCLI::test_gw_skips_api_key_checkpytest tests/test_gateway.py::TestGatewayCLI::test_non_gw_still_requires_api_keypytest tests/test_gateway.py::TestGatewayResource::test_health_omits_auth_header_without_api_keyunset VLMRUN_API_KEY && vlmrun gw modelssucceedsunset VLMRUN_API_KEY && vlmrun files liststill fails with API key required