Skip to content

Set up Cursor Cloud dev environment for Ember #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
besmpl wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Set up Cursor Cloud dev environment for Ember #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,23 @@ protecting the root package from speculative architecture.
- Summarize long command output and preserve the exact command.
- Keep final output compact: changed files, checks, risks, and next pressure.

## Cursor Cloud specific instructions

- This module pins `go 1.26` in `go.mod`. Go 1.26 is installed at
`/usr/local/go` and is first on `PATH`, so `go` resolves to 1.26 already.
The automatic `GOTOOLCHAIN` download of go1.26 does NOT work in this
environment, so rely on the pinned `/usr/local/go` toolchain rather than
letting an older `go` try to fetch it.
- There are no external module dependencies (`go.mod` has only the module and
`go` directives), so dependency refresh is effectively a no-op.
- Ember is a library, not an app or CLI; there is no server or binary to run.
Exercise it through the public `Compile` / `Run` / `RunWithGlobals` API
(see `docs/public-surface.md`). A minimal end-to-end smoke is:
`go build ./...`, then compile+run a script such as `return 1 + 2`.
- Standard verification commands are already documented: `go build ./...`,
`scripts/check-fast`, and `scripts/check` (see `docs/checks.md`). The full
`scripts/check` suite takes ~25-30s.

## Tooling Rules

- Use `rg` or `rg --files` for search.
Expand Down
Loading