Skip to content

docs: add Cursor Cloud environment setup notes - #7050

Draft
rrama wants to merge 3 commits into
mainfrom
cursor/cloud-env-setup-notes-2e57
Draft

docs: add Cursor Cloud environment setup notes#7050
rrama wants to merge 3 commits into
mainfrom
cursor/cloud-env-setup-notes-2e57

Conversation

@rrama

@rrama rrama commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High)
  • Highlights breaking API changes (if applicable) — none, documentation only
  • Links to automated tests covering new functionality — n/a, no product code changes
  • Includes manual testing instructions (if necessary) — n/a
  • Updates relevant GitBook documentation (PR link: n/a — AGENTS.md is repo-local agent guidance, not user docs)
  • Includes product update to be announced in the next stable release notes — n/a, internal documentation

What does this PR do?

Adds a ## Cursor Cloud specific instructions section to AGENTS.md, capturing the
non-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:

  • Node/npm must come from nvm v22.22.3, not /exec-daemon/node (which ships no
    npm) — the root .npmrc sets engine-strict=true against "npm": "^11.12.1".
  • GOTOOLCHAIN=go1.26.5 must stay pinned, so the toolchain resolves via
    proxy.golang.org rather than go.dev.
  • make build BUILD_MODE=public plus the convco prerequisite.
  • The license-prep workaround, corrected: go-licenses save --force wipes
    cliv2/internal/embedded/_data/licenses/ first, so the Go LICENSE has to be placed
    after a build and the make target stamped. The other PR claimed pre-placing the
    file was enough, which does not survive the --force.
  • Why make lint keeps re-running the golangci-lint installer: cliv2/Makefile
    never assigns TOOLS_BIN, so the prerequisite resolves to a missing
    /golangci-lint. Also notes that cliv2 pins v2.9.0 while the other Snyk Go repos
    use v2.10.1.

What changed since the first revision

  • Verified every Makefile claim against the checked-in cliv2/Makefile rather than
    relying on the original run's notes (OVERRIDE_GOCI_LINT_V := v2.9.0, GO_BIN := $(shell pwd)/.bin, TOOLS_BIN unset, and the $(CACHE_DIR)/prepare-3rd-party-licenses
    target having no prerequisites).
  • Removed the hard-coded reachable/blocked host list. The egress allowlist changes
    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.com covers subdomains only, and a block shows up as a TLS
    reset mid-handshake rather than a DNS failure.

Where should the reviewer start?

AGENTS.md is the only changed file — read the new section at the bottom. The main
thing 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=public
should 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.

Co-authored-by: Ben Durrans <Benjamin.Durrans@snyk.io>
@snyk-io

snyk-io Bot commented Jul 28, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor
Warnings
⚠️

Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones.
A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax.
Files found:

  • AGENTS.md
⚠️ There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against a0a4504

cursoragent and others added 2 commits July 28, 2026 14:56
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants