From 77f91249126ce21d8d30d0d78e5eda056386f35c Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Wed, 30 Sep 2026 23:50:04 +0000 Subject: [PATCH] docs: note Cloud Agent install and test commands Record the uv workspace sync CI uses, the checks that prove the SDK, and that example runs need provider secrets the test suite does not. Co-authored-by: andrewklatzke --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 305613a9..2100f7aa 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -714,6 +714,13 @@ response = await graph( ).invoke(user_input, context) ``` +## Cursor Cloud specific instructions + +- Python 3.12 and `uv` (`~/.local/bin` if it is not already on `PATH`). After checkout, run `uv lock` and then `uv sync --all-packages`, the same package set CI installs. Plain `uv sync` does not install every workspace member. +- Verify with `make lint`, `make format-check`, `make typecheck`, and `make test`. +- `main.py` examples call LaunchDarkly and a model provider. They need `LD_SDK_KEY` and the provider key from `.env.example`. The test suite mocks those services. +- `uv lock` rewrites workspace member versions in `uv.lock` when they have drifted from each package's `pyproject.toml`. That dirty lockfile is not an install failure; do not commit it unless the lockfile change is intentional. + ## Maintaining this file Keep this file for knowledge useful to almost every future agent session in this project.