Conversation
Co-authored-by: xre217 <xre217@users.noreply.github.com>
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
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
Sets up the Cursor Cloud Agent development environment for Grok Forge (Next.js 16 local AI studio, Ollama-powered) and documents non-obvious startup caveats for future agents.
The only code change is an added
## Cursor Cloud specific instructionssection inAGENTS.md. Dependency installation is handled by the environment update script (npm install); Ollama and thellama3.2:3bmodel are baked into the VM snapshot (system dependencies, not part of the update script).What was set up
npm install— project dependencies (Next.js 16, React 19, AI SDK, etc.)zstd, required by the installer) andllama3.2:3bpulled (~2 GB).env.localcreated from.env.example(local-only mode, no xAI key)Verification
npm run lintreact-hookserrors in committed source (not env issues)npm run buildnpm run dev:localnpm run verifyPOST /api/chat+ browser chatollama · llama3.2:3bend-to-endThe current Ollama build runs the AMX ggml CPU backend fine on this VM — no backend workaround was needed.
Demo
Sent a chat message in the studio; the assistant replied locally via Ollama with an
OLLAMA · LLAMA3.2:3Bengine badge.grok_forge_chat_hello_world.mp4
Grok Forge chat reply with Ollama badge
To show artifacts inline, enable in settings.