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

[OnlineChef]

What

Sets up the development environment for cloud agents and records the non-obvious startup/run caveats in AGENTS.md under a new ## Cursor Cloud specific instructions section. No runtime/source code changes.

Environment setup performed

• Installed Bun 1.3.14 (pinned) and put it on PATH via /usr/local/bin/bun.
• Installed root deps (bun install) and GUI deps (bun install --cwd gui).
• Configured the startup update script to bun install + bun install --cwd gui.

Verification (agreed scope: the single Bun proxy daemon + dashboard)

Check	Command	Result
Typecheck	bun run typecheck	pass
Privacy scan	bun run privacy:scan	pass
GUI lint	bun --bun run lint:gui	pass
Tests	bun run test	5108 pass / 5 pre-existing env failures
Run proxy	bun run dev:proxy	serves API + dashboard on :10100
Run dashboard	bun run dev:gui	Vite dev server on :5173, proxies to daemon

The 5 test failures are not regressions: 3 are Docker-container detection (ocx status/service report "unsupported in Docker") and 2 are base-branch content drift (release.yml text, source-Bun docs paragraph). Documented in AGENTS.md.

Hello-world (core functionality)

Added an OpenRouter provider through the dashboard UI; the proxy auto-discovered its models and persisted it to config (GET /api/config shows openrouter with hasApiKey: true).

Notes

• bun run lint:gui must run under the Bun runtime (bun --bun ...) here — the VM's Node can't strip TS types imported by gui/eslint.config.js. CI uses Node 24 so it's unaffected.
• gui/bun.lock drifts from gui/package.json (missing posthog-js/fontsource entries), so --frozen-lockfile installs and bun run build:gui fail; plain bun install reconciles it. Left the lockfile untouched to keep this PR scoped to setup docs.

Branch note

Repo policy prefers dev for feature PRs, but this branch is based on main (this run's base), which has diverged from dev by 100+ commits. Targeting main keeps the diff to the single AGENTS.md commit; retarget/rebase onto dev if preferred.

  

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 63e13a5e-86fe-4f92-8a11-9e52ad954f00

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Target branch corrected

This pull request now targets dev.

The [WRONG BRANCH] title prefix has been removed. Its existing draft status has been preserved.

[OnlineChef]

Retargeted from main → dev (fork contribution path). Please rebase onto current dev before review; [WRONG BRANCH] prefix removed from the title.

[OnlineChef]

Closing as stale vendor-specific setup documentation. Top-level agent guidance should contain stable repository contracts, not temporary Cursor Cloud VM assumptions or known-failure counts. Reuse only durable install/test/start commands later in a focused development-documentation PR.