Skip to content

docs: add AGENTS.md with Cursor Cloud development instructions - #9596

Closed
dagil-nvidia wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-690a
Closed

docs: add AGENTS.md with Cursor Cloud development instructions#9596
dagil-nvidia wants to merge 1 commit into
mainfrom
cursor/setup-dev-environment-690a

Conversation

@dagil-nvidia

Copy link
Copy Markdown
Collaborator

Overview:

Adds a root-level AGENTS.md file with Cursor Cloud-specific development instructions for future cloud agents working on this codebase.

Details:

  • Documents the network restriction in Cloud Agent VMs where static.rust-lang.org, index.crates.io, and static.crates.io (Fastly CDN) are blocked, preventing cargo build/cargo test.
  • Provides the recommended Python-only workflow: install ai-dynamo-runtime from PyPI instead of building Rust bindings locally.
  • Documents how to run the frontend without GPU/etcd/NATS (--discovery-backend file).
  • Lists key paths, linting commands, and testing guidance.

Where should the reviewer start?

  • AGENTS.md — the only file changed.

Related Issues:

  • N/A — documentation-only change for Cursor Cloud agent development.
Open in Web Open in Cursor 

Signed-off-by: Cursor Agent <cursoragent@cursor.com>

Co-authored-by: Dan Gil <dagil-nvidia@users.noreply.github.com>
@copy-pr-bot

copy-pr-bot Bot commented May 15, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions github-actions Bot added docs documentation Improvements or additions to documentation labels May 15, 2026
@grahamking

Copy link
Copy Markdown
Contributor

I suspect a lot of devs have a local AGENTS.md (I do) that this would overwrite. Here is mine in full; I realized I was adding this to almost all prompts.

This is an AI inference system. It is composed of two Python processes:
- A frontend in `components/src/dynamo/frontend/` which is the HTTP server and does the pre and post processing for the request.
- A backend in `components/src/dynamo/[vllm|sglang|mocker]` which does the actual inference.

That Python code uses some Rust bindings from `lib/bindings/python` which in turn uses Rust code in `lib/llm/`.

Is there a way to put these cursor cloud instructions in a cursor cloud specific file? We don't really want them in every single Claude and Codex session we run.

@github-actions

Copy link
Copy Markdown
Contributor

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@dagil-nvidia

Copy link
Copy Markdown
Collaborator Author

Closing as superseded.

The repo now has a tracked root AGENTS.md (added in #10855, maintained since), plus CLAUDE.md, docs/fern/AGENTS.md, and the .ai/*.md topic guides covering build, test, lint, and PR conventions. This PR adds that file from scratch, so it conflicts with the file it set out to create - which is also the concern @grahamking raised at the time about overwriting developers' local copies.

The content has drifted as well: it pins ai-dynamo-runtime==1.2.0 (now 1.4.0), Rust 1.93.1 (now 1.96.1), points at deploy/docker-compose.yml (now dev/docker-compose.yml), and says lib/ has 30 crates (now 22).

The one piece not covered elsewhere - the Cursor Cloud sandbox blocking static.rust-lang.org and crates.io - is agent-environment configuration rather than a repo fact. #11378 is also covering this ground.

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

Labels

docs documentation Improvements or additions to documentation size/M Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants