Skip to content

Conversation

@shahrear33
Copy link
Contributor

…ctions

  • Introduced CLAUDE.md to provide comprehensive guidance for the VLM Run Python SDK, including project overview, development commands, architecture details, configuration, optional dependencies, testing, and code style.
  • Updated version to 0.5.2 in version.py.
  • Modified CLI credential check to skip for config commands in cli.py.

…ctions

- Introduced CLAUDE.md to provide comprehensive guidance for the VLM Run Python SDK, including project overview, development commands, architecture details, configuration, optional dependencies, testing, and code style.
- Updated version to 0.5.2 in version.py.
- Modified CLI credential check to skip for config commands in cli.py.
@gemini-code-assist
Copy link

Summary of Changes

Hello @shahrear33, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the developer experience by introducing a detailed CLAUDE.md documentation file, which serves as a comprehensive guide for understanding and contributing to the VLM Run Python SDK. Additionally, it includes a minor version bump and improves the command-line interface usability by allowing configuration commands to run without prior API credential validation.

Highlights

  • New Documentation File: A new CLAUDE.md file has been added, providing comprehensive guidance for the VLM Run Python SDK. This includes details on project overview, development commands, architecture, configuration, optional dependencies, testing, and code style, specifically tailored for AI code assistants like Claude.
  • Version Update: The SDK version has been incremented from "0.5.1" to "0.5.2" in vlmrun/version.py.
  • CLI Credential Check Logic: The vlmrun/cli/cli.py file has been updated to skip the API credential check when a "config" subcommand is invoked. This allows users to configure their API key without being blocked by a missing credential error.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a CLAUDE.md file to guide AI-assisted development, updates the CLI to allow configuration without prior credential checks, and bumps the project version. The changes are well-implemented and logical. The new CLAUDE.md is comprehensive and provides a great overview of the project. The CLI modification is a necessary fix for setting up credentials. I have one suggestion for the CLAUDE.md file to improve consistency with the codebase's naming conventions, which will enhance clarity for both human developers and AI assistants.

- **Resource Classes** - Each API domain has its own resource class:
- `ImagePredictions`, `DocumentPredictions`, `VideoPredictions`, `AudioPredictions` (`predictions.py`)
- `Agent` (`agent.py`) - Also provides OpenAI-compatible completions interface via `client.agent.completions`
- `Files`, `Hub`, `Models`, `Datasets`, `Finetuning`, `Feedback`, `Executions`, `Artifacts`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better clarity and consistency with the client's properties, it would be helpful to list the resource properties using their actual snake_case names as they are accessed on the VLMRun client instance (e.g., client.fine_tuning). The current list uses PascalCase, which are the class names, and Finetuning is inconsistent with the property name fine_tuning.

Using property names will make it clearer for anyone (including an AI assistant) how to access these resources.

Suggested change
- `Files`, `Hub`, `Models`, `Datasets`, `Finetuning`, `Feedback`, `Executions`, `Artifacts`
- `files`, `hub`, `models`, `datasets`, `fine_tuning`, `feedback`, `executions`, `artifacts`

@shahrear33 shahrear33 merged commit 5813c4b into main Jan 26, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant