Skip to content

Comments

chore: weekly Cloud API workflow to audit architecture docs; Python client + settings CLI#88

Draft
enyst wants to merge 10 commits intomainfrom
chore/weekly-arch-docs-cloud
Draft

chore: weekly Cloud API workflow to audit architecture docs; Python client + settings CLI#88
enyst wants to merge 10 commits intomainfrom
chore/weekly-arch-docs-cloud

Conversation

@enyst
Copy link
Owner

@enyst enyst commented Aug 16, 2025

This PR adds a weekly GitHub Action that triggers an OpenHands Cloud conversation to audit and update the repository’s architecture docs. It is designed to keep API calls in python, separated and minimal.

What’s included

  • Python Cloud API client (scripts/cloud_api.py)
    • Separated methods: store_llm_settings, create_conversation, get_conversation, get_trajectory, poll_until_complete
    • Intentionally does NOT accept or send provider LLM API keys; only authenticates with OPENHANDS_API_KEY
  • Weekly workflow (.github/workflows/weekly-arch-docs-cloud.yml)
    • Runs every Saturday at 06:00 UTC
    • Starts a Cloud conversation using only OPENHANDS_API_KEY
    • Does not poll by default; keeps runtime minimal. The Python entrypoint supports polling if needed.
  • Weekly entrypoint script (scripts/weekly_arch_docs_task.py)
    • Sends the task prompt/instructions to review docs/usage/architecture/backend.mdx and docs/usage/architecture/runtime.mdx
    • If material changes are found, the agent updates docs and opens a PR following the template with a technical report
    • If nothing meaningful changed, it summarizes findings and does not open a PR
  • Settings CLI (scripts/configure_cloud_llm_settings.py)
    • Optional one-off CLI to call POST /api/settings to configure an LLM model/base URL for the Cloud account
    • Not invoked by the weekly job

Why

  • Keep provider keys out of CI: OPENHANDS_API_KEY is the only secret used by the weekly workflow
  • Separation of concerns: API methods are separated and reusable; LLM configuration is a separate script
  • Simplicity: The weekly job starts a Cloud conversation and exits quickly; additional polling/reporting can be layered on later if desired

How to enable

  1. Add repository secret OPENHANDS_API_KEY in GitHub (Settings → Secrets and variables → Actions → New repository secret)

  2. (Optional) If you want to set Cloud LLM model/base URL on your account, run:
    python scripts/configure_cloud_llm_settings.py
    --api-key $OPENHANDS_API_KEY
    --llm-model "$LLM_MODEL"
    --llm-base-url "$LLM_BASE_URL"

    Optionally add provider tokens only if you explicitly want to:
    --provider-token openai=$OPENAI_API_KEY
    --provider-token groq=$GROQ_API_KEY

Notes

  • Model used for this work: GPT-5 (documented in the workflow header comment and commit metadata)
  • The workflow prints a conversation link. If you want polling/trajectory logging directly in the job, we can add a follow-up step.

Co-authored-by: openhands openhands@all-hands.dev

enyst and others added 4 commits August 16, 2025 10:06
…re docs audit

Includes:
- Python Cloud API client (no provider LLM keys sent)
- Weekly scheduled GH Action to start conversation
- Entrypoint script for manual triggering
- Plan README

Co-authored-by: OpenHands-UNKNOWN openhands@all-hands.dev
…arate per method

Co-authored-by: OpenHands-UNKNOWN openhands@all-hands.dev
Co-authored-by: openhands <openhands@all-hands.dev>
Model: GPT-5
…t separate from weekly job)

Co-authored-by: openhands <openhands@all-hands.dev>
Model: GPT-5
@coderabbitai
Copy link

coderabbitai bot commented Aug 16, 2025

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/weekly-arch-docs-cloud

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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.

Summary of Changes

Hello @enyst, 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 introduces an automated weekly workflow to audit and update architecture documentation using the OpenHands Cloud API. It includes a new Python client for the API, a dedicated script to initiate the audit conversation, and a separate CLI for managing LLM settings. The entire setup is designed with a strong focus on security, ensuring sensitive LLM keys are kept out of the continuous integration environment.

Highlights

  • New Cloud API Client: A new Python client (scripts/cloud_api.py) is introduced to interact with the OpenHands Cloud API, providing methods for managing settings and conversations. It is designed to explicitly avoid handling LLM API keys directly, enhancing security.
  • Automated Architecture Documentation Audit: A new weekly GitHub Action, driven by scripts/weekly_arch_docs_task.py, is added to automatically trigger an AI agent to review and update backend.mdx and runtime.mdx architecture documentation.
  • Separate LLM Settings CLI: A dedicated command-line interface (scripts/configure_cloud_llm_settings.py) is provided for one-off configuration of LLM models and base URLs on the OpenHands Cloud account, ensuring separation from the automated workflow.
  • Enhanced Security and Modularity: The overall design prioritizes keeping LLM provider keys out of CI by using only an OPENHANDS_API_KEY for the workflow and separating API methods and LLM configuration into distinct, reusable components.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 weekly workflow to audit architecture documentation using a new Python client for the OpenHands Cloud API. The changes include the API client itself, a CLI for configuration, and the weekly task script. My review focuses on improving code maintainability and consistency. I've suggested refactoring repetitive code in the API client for building request bodies, ensuring consistent argument parsing in the CLI scripts, and adhering to Python style guidelines. These changes will make the new scripts easier to read and maintain.

enyst and others added 5 commits August 16, 2025 11:06
…llm_api_key in /api/settings CLI + client

Co-authored-by: openhands <openhands@all-hands.dev>
Model: GPT-5
…; respond to review feedback

- cloud_api.store_llm_settings: build params dict and filter None
- cloud_api.create_conversation: unify optional params handling
- settings CLI: strip whitespace in provider token values

Co-authored-by: openhands <openhands@all-hands.dev>
Model: GPT-5
…-url (address review)

Co-authored-by: openhands <openhands@all-hands.dev>
Model: GPT-5
…ON/text body); add requests import

Co-authored-by: openhands <openhands@all-hands.dev>
Model: GPT-5
…logs

Co-authored-by: openhands <openhands@all-hands.dev>
Model: GPT-5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant