chore(env): add Cursor Cloud Agent environment config - #576
Merged
Conversation
Adds .cursor/environment.json and an idempotent install script for Cursor Cloud Agents. The install script: - selects an nvm-managed Node whose bundled node:sqlite has FTS5 enabled (the daemon's default node has FTS5 disabled, which breaks @dripnex/mcp-server) and makes it the default node for all shells; - runs pnpm install --frozen-lockfile (postinstall rebuilds better-sqlite3 for Electron and materializes the Electron binary); - builds workspace packages so typecheck and the Playwright+Electron e2e suite are ready to run. Validated: pnpm test (19/19 tasks), typecheck, lint, build, and the Electron e2e suite (7 passed under xvfb).
|
Warning Review limit reachedNext included review available in 56 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…me PATH The install-time PATH can differ from the agent runtime PATH: during an environment build the nvm bin already precedes /exec-daemon, so the previous 'no shim needed' shortcut skipped creating the shims — leaving a fresh agent's default node pointing at the daemon's FTS5-less node. Always place the shims in every writable PATH dir preceding /exec-daemon (plus /usr/local/cargo/bin).
tomymaritano
marked this pull request as ready for review
August 22, 2026 21:05
Contributor
|
🎉 This PR is included in version 0.18.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
2 participants
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.
Summary
Adds a Cursor Cloud Agent development environment for Dripnex so agents can install dependencies, run the full workspace, and launch the Electron app end-to-end. Config lives in the repo (
.cursor/environment.json), so it is versioned with code and takes effect for future Cloud Agents once merged.New files:
.cursor/environment.json—install: bash .cursor/install.sh(default base image, repo-file managed)..cursor/install.sh— idempotent bootstrap.What the install script does and why:
@dripnex/mcp-serveruses Node's built-innode:sqliteand asserts FTS5 is compiled in. The node binary the Cursor exec daemon ships (/exec-daemon/node) has FTS5 disabled, which makespnpm test(and the MCP server) fail. The script selects an nvm-managed Node whose bundled SQLite has FTS5 enabled (v22.22.2, matching CI's Node 22) and makes it the defaultnodefor every shell by symlinking the toolchain into a PATH dir that precedes the daemon's node. Shims are placed unconditionally so they hold regardless of the runtime PATH order.pnpm install --frozen-lockfile— the desktoppostinstallrunselectron-builder install-app-deps(rebuildsbetter-sqlite3for Electron) and materializes the Electron binary, which is what letspnpm devand the Playwright + Electron e2e suite launch.pnpm build— pre-builds workspace packages sotypecheckand the e2e suite are ready.No application code is changed. No secrets or network allowlist entries are required (the app is offline-first).
Type of Change
Checklist
pnpm test) — 19/19 turbo tasks (incl.@dripnex/mcp-server16/16)pnpm build)developbranch (notmain)Validation
pnpm test(default daemon node)pnpm typecheckpnpm lintpnpm buildxvfb-run pnpm e2e)install.shcompletes and verifies FTS5Screenshots
Dripnex running end-to-end in the Cloud Agent VM (launched under xvfb):
Dripnex welcome screen
Dripnex editing a markdown note
To show artifacts inline, enable in settings.