Skip to content

docs(agents): add Cursor Cloud environment setup notes - #21

Closed
andersalm wants to merge 1 commit into
mainfrom
cursor/cloud-env-setup-af9e
Closed

andersalm wants to merge 1 commit into
mainfrom
cursor/cloud-env-setup-af9e

Conversation

@andersalm

Copy link
Copy Markdown
Contributor

Summary

Sets up the Cloud Agent development environment for this repo and records durable, non-obvious guidance for future agents in AGENTS.md. No product code is changed — the only file touched is AGENTS.md.

Environment setup

  • Startup update script (dependency refresh only): rustup target add wasm32-unknown-unknown and cargo install just.
  • Rust 1.89.0 is pinned by rust-toolchain.toml and auto-synced by rustup.
  • The core just verify gate (Node .mjs checks + Python smokes) uses only stdlib / node --test; no npm install is required.

Verification performed

Step Command Result
Build just build Runtime + core capsules built (elastos 0.6.0-dev)
Lint just lint clippy -D warnings + cargo fmt --check clean
Test just test 2014 passed, 0 failed (35 suites)
Run elastos serve (source binary) /api/health → {"status":"ok","version":"0.6.0-dev"}, Carrier P2P online, authenticated POST /api/auth/attach session issued
Core actions elastos identity show / nickname set / init DID created, nickname set, capsule project scaffolded

Known release-gated gap (documented, not a bug)

just home-frontdoor-smoke and the public-install-* smokes call scripts/install.sh, which downloads the published release binary (currently v0.1.2) from elastos.elacitylabs.com. That public binary lacks newer subcommands this dev tree's installer expects (e.g. principal-root-upgrade), so the installed-path proofs fail until a 0.6-compatible release is published (see state.md → "Public Install Truth"). The source elastos serve path is used to run the runtime locally instead.

Open in Web Open in Cursor 

Document toolchain, dependency-free core gate, source-run path for elastos serve, and the release-gated installer smoke gap for Cloud Agents.

Co-authored-by: Anders <andersalm@users.noreply.github.com>
@irzhywau

irzhywau commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Closing: the Cursor Cloud environment section from this PR (cb80aab) has been adopted onto the upstream/0.7.1-dev integration line (commit 19cf7c19, landing with the next push of that branch), refreshed for the 0.7 tree along the way:

  • toolchain claim updated to the current 1.91.0 pin,
  • the build note now describes the shared target-capsules dir the capsule test lane uses since 8ac18bec,
  • the public-install gap paragraph is version-agnostic — the published-version truth stays in state.md ("Public Install Truth") instead of a hardcoded number that rots.

Everything else carries over verbatim. The original branch cursor/cloud-env-setup-af9e has nothing further unique once that lands.

@irzhywau irzhywau closed this Sep 1, 2026
irzhywau added a commit that referenced this pull request Sep 1, 2026
…shed for the 0.7 tree

Carries the Cursor Cloud specific instructions section from PR #21
(cb80aab, Anders Alm) with its stale 0.6-era claims corrected:
toolchain pin now 1.91.0, the capsule test lane's shared
target-capsules dir described, and the public-install gap paragraph
made version-agnostic with state.md as the published-version truth.
irzhywau added a commit that referenced this pull request Sep 1, 2026
…shed for the 0.7 tree

Carries the Cursor Cloud specific instructions section from PR #21
(cb80aab, Anders Alm) with its stale 0.6-era claims corrected:
toolchain pin now 1.91.0, the capsule test lane's shared
target-capsules dir described, and the public-install gap paragraph
made version-agnostic with state.md as the published-version truth.
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.

3 participants