docs: add AGENTS.md with Cursor Cloud dev environment notes - #96
Draft
barredterra wants to merge 1 commit into
Draft
docs: add AGENTS.md with Cursor Cloud dev environment notes#96barredterra wants to merge 1 commit into
barredterra wants to merge 1 commit into
Conversation
Co-authored-by: Raffael Meyer <barredterra@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
Set up and verified a full development environment for the
ask_alyfFrappe app in Cursor Cloud, and captured the durable, non-obvious startup/run caveats in a newAGENTS.md.This run booted as a just-in-time override (no linked environment / no build), so the committed
.cursor/Dockerfilewas not applied. I bootstrapped a functionally-equivalent bench in the VM (Python 3.14, Node 24, MariaDB, Redis, Frappeversion-16) to prove the setup works end to end. The environment itself remains defined by the committed repo files (.cursor/environment.json→Dockerfile+install.sh+start.sh); no environment/snapshot changes are made here.What was verified
pre-commit run --all-files: ruff, ruff-format, prettier, eslint all pass.bench --site ask-alyf.localhost run-tests --app ask_alyf:Ran 109 tests ... OK.bench start(web:8000, socketio:9000);/api/method/ping→pong; login page renders.send_message→ RQ worker → LangChain coordinator → OpenAI Responses API) runs; the worker issuesPOST https://api.openai.com/v1/responses.Known blocker (environment, not code)
The AI chat requires network egress to
api.openai.com, which is not in the default Cursor Cloud egress allowlist. The external LLM call fails withopenai.APIConnectionError: Connection error, and the chat shows the graceful fallback "I hit an error while processing that request." Addingapi.openai.comto the egress allowlist unblocks real chat responses.Changes
AGENTS.mddocumenting the app, the repo-defined environment, and Cloud-specific run caveats (Python 3.14 / Node 24 requirement, bench location + site name, run/lint/test commands, and theapi.openai.comegress requirement).Artifacts
Ask ALYF assistant open on Frappe Desk
Chat message processed end-to-end (LLM call blocked by egress)
To show artifacts inline, enable in settings.