Skip to content

Development environment setup#430

Merged
abhimehro merged 1 commit intomainfrom
cursor-agent/development-environment-setup-adbe
Feb 26, 2026
Merged

Development environment setup#430
abhimehro merged 1 commit intomainfrom
cursor-agent/development-environment-setup-adbe

Conversation

@abhimehro
Copy link
Owner

Create AGENTS.md to provide Cloud-specific instructions for future agents.


Open in Web Open in Cursor 

Co-authored-by: Abhi Mehrotra <abhimehro@pm.me>
@cursor
Copy link

cursor bot commented Feb 26, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@trunk-io
Copy link

trunk-io bot commented Feb 26, 2026

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Feb 26, 2026
@github-actions
Copy link

👋 Development Partner is reviewing this PR. Will provide feedback shortly.

@gemini-code-assist
Copy link

Summary of Changes

Hello @abhimehro, 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 essential documentation for setting up and operating the project's development environment, specifically tailored for Cursor Cloud agents. It provides a clear guide covering the project's architecture, required runtime dependencies, and standard development workflows, while also highlighting a critical existing bug that impacts the main application module. This ensures that new developers can quickly onboard and understand the system's operational nuances.

Highlights

  • New Documentation File: Added AGENTS.md to provide comprehensive Cloud-specific instructions for future agents.
  • Development Environment Setup: Documented the project overview, runtime requirements (Python >= 3.13, uv package manager), and common commands for installing dependencies, linting, testing, and running the application.
  • Known Issue Highlighted: Detailed a pre-existing syntax error in main.py (at line 1141) that prevents module import and application execution, clarifying its impact on testing.
  • Secrets Management: Outlined the necessity of TOKEN and PROFILE environment variables or a .env file for live application runs.
Changelog
  • AGENTS.md
    • Created a new documentation file for Cloud-specific agent instructions.
    • Added a project overview and specified Python 3.13 and uv as runtime requirements.
    • Included a table of common commands for development tasks like dependency management, linting, and testing.
    • Documented a significant pre-existing syntax error in main.py and its implications.
    • Provided guidance on setting up necessary environment variables (TOKEN, PROFILE) for live application execution.
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.

@abhimehro abhimehro merged commit 31a2fe3 into main Feb 26, 2026
19 checks passed
@abhimehro abhimehro deleted the cursor-agent/development-environment-setup-adbe branch February 26, 2026 19:58
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

The pull request adds a new AGENTS.md file with instructions for setting up the development environment in Cursor Cloud. The instructions cover project overview, runtime requirements, common commands, known issues, and secrets for live runs. The file provides helpful information for future agents working on the project.


### Runtime

- Requires **Python >= 3.13** (uses modern language features). The VM's system Python is 3.12; `uv python install 3.13` provides the right version and `uv sync` picks it up automatically via `requires-python` in `pyproject.toml`.

Choose a reason for hiding this comment

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

medium

The minimum Python version is specified as 3.13, but the system Python version is 3.12. It might be helpful to provide a command or instructions on how to verify the Python version after installation to ensure the correct version is being used.


### Secrets for live runs

A live sync run requires `TOKEN` (Control D API token) and `PROFILE` (profile ID) as environment variables or in a `.env` file. All tests use mocks and do not need these secrets.

Choose a reason for hiding this comment

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

medium

Consider adding a note that these secrets should be treated with care and not committed to version control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants