docs: add Cursor Cloud environment setup notes - #7050
Draft
rrama wants to merge 3 commits into
Draft
Conversation
Co-authored-by: Ben Durrans <Benjamin.Durrans@snyk.io>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Contributor
|
Co-authored-by: Ben Durrans <Benjamin.Durrans@snyk.io>
Consolidates the two duplicate cloud-setup notes into this branch, keeping the more complete account of the license-prep workaround: because go-licenses runs with --force and wipes the tree, the Go LICENSE has to be placed after a build rather than before it, then the make target stamped. Verifies the claims against the checked-in Makefile: TOOLS_BIN is never assigned in cliv2/Makefile, so the golangci-lint prerequisite re-triggers the installer, and cliv2 pins v2.9.0 while the other Go repos use v2.10.1. Replaces the fixed reachable/blocked host list with guidance to probe egress directly, since the allowlist changes between runs. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
AGENTS.mdis repo-local agent guidance, not user docs)What does this PR do?
Adds a
## Cursor Cloud specific instructionssection toAGENTS.md, capturing thenon-obvious setup gotchas an agent hits when building this repo in a Cursor Cloud
Linux VM. Documentation only — no product code, build or CI changes.
Two duplicate cloud-setup PRs had been opened against this repo by successive cloud
runs. This one now carries the consolidated content and #7044 has been closed as
superseded, leaving a single PR per repo.
The notes cover:
v22.22.3, not/exec-daemon/node(which ships nonpm) — the root
.npmrcsetsengine-strict=trueagainst"npm": "^11.12.1".GOTOOLCHAIN=go1.26.5must stay pinned, so the toolchain resolves viaproxy.golang.orgrather thango.dev.make build BUILD_MODE=publicplus theconvcoprerequisite.go-licenses save --forcewipescliv2/internal/embedded/_data/licenses/first, so the Go LICENSE has to be placedafter a build and the make target stamped. The other PR claimed pre-placing the
file was enough, which does not survive the
--force.make lintkeeps re-running the golangci-lint installer:cliv2/Makefilenever assigns
TOOLS_BIN, so the prerequisite resolves to a missing/golangci-lint. Also notes thatcliv2pins v2.9.0 while the other Snyk Go reposuse v2.10.1.
What changed since the first revision
cliv2/Makefilerather thanrelying on the original run's notes (
OVERRIDE_GOCI_LINT_V := v2.9.0,GO_BIN := $(shell pwd)/.bin,TOOLS_BINunset, and the$(CACHE_DIR)/prepare-3rd-party-licensestarget having no prerequisites).
between runs, so a fixed map goes stale and gets trusted anyway. Readers are now told
to probe directly, with the matching semantics that actually matter: bare entries are
apex-exact while
*.example.comcovers subdomains only, and a block shows up as a TLSreset mid-handshake rather than a DNS failure.
Where should the reviewer start?
AGENTS.mdis the only changed file — read the new section at the bottom. The mainthing worth a second opinion is whether the license-prep workaround is described
accurately enough to follow.
How should this be manually tested?
Nothing to run. To confirm the guidance, follow the section in a fresh cloud VM:
PATH="$HOME/.nvm/versions/node/v22.22.3/bin:$PATH" make build BUILD_MODE=publicshould produce
./binary-releases/snyk-linux.What's the product update that needs to be communicated to CLI users?
None — internal contributor/agent documentation.
Risk assessment
Low. Markdown only; no product, build or CI behaviour is affected.